Activities of "alper"

bir de tüm destek ekibimizin sorulara cevap verebilmesi için bundan sonraki sorularınızı İngilizce sormanızı rica ederiz.

Merhaba,

indirdiğimiz projede klasör adını Angular yerine farklı bir şey yapmıştık bu olabilirmi mesela

Evet, bundan kaynaklı olarak angular klasörünü bulamıyordur.

Şu iki yoldan biri işinizi görecektir:

• Eğer sizin için önemli değilse, klasörün ismini angular olarak düzenleyip projeyi ABP Suite'e tekrar ekleyin.

• %USERPROFILE%\.abp\suite\appsettings.json dosyasında ilgili projeyi bulun. Daha sonra UiFramework değerini 3, UiFrameworkName değerini Angular olarak değiştirin ve AngularSolutionRootPath değerine de angular klasörünüzün path'ini yazın.

Ve bunu proje ekibinizdeki tüm arkadaşların yapması lazım. Tavsiyem "Angular" klasörünün adını değiştirmeyin.

thanks for the feedback

I'm closing this topic because there are too many messages on the page and it slows the page down. you can write your new posts to the following topic #5161

We want to collect some feedback from you to improve ABP support. In this context;

❓What are your problems with ABP Support? 💡Please suggest your ideas on how we can improve them.

This topic is the ongoing topic of #4479

bu özellik zaten mevcut. birşey yapmanıza gerek olmadan Angular sayfaları oluşur. Acaba Angular projesinin lokasyonunu mu değiştirdiniz?

Suite needs to find Volo.Abp.Commercial.SuiteTemplates.dll in your project output directories. As I understand you exclude this DLL. Suite will not work if it cannot find this file because all the templates to generate the code are in this file.

After upgrading from 7.0.1 to 7.2.2 getting the following build errors, after cleaning up known issues. All errors are coming from the Chart.js directory.

Did you run the command abp install-libs ? https://docs.abp.io/en/abp/latest/CLI#install-libs

Is the Microservice Template actually intended to be used and working or is it some kind of preview? When trying to create a simple project using ABP Suite, there are numerous build errors the first time you try to build it. Doing a "dotnet restore" in the solution directory will remove some of it, but instead produce new ones. The entire process seems kind of shaky...

Edit:

At first when trying to build in VS you get 40 of these

Severity Code Description Project File Line Suppression State Error NU1105 Unable to find project information for 'M:\Projects\ASP.NET\ABP\src\MicroserviceTest3\services\product\src\MicroserviceTest3.ProductService.EntityFrameworkCore\MicroserviceTest3.ProductService.EntityFrameworkCore.csproj'. If you are using Visual Studio, this may be because the project is unloaded or not part of the current solution so run a restore from the command-line. Otherwise, the project file may be invalid or missing targets required for restore. MicroserviceTest3.ProductService.HttpApi.Host M:\Projects\ASP.NET\ABP\src\MicroserviceTest3\services\product\src\MicroserviceTest3.ProductService.HttpApi.Host\MicroserviceTest3.ProductService.HttpApi.Host.csproj 1

After having done "dotnet restore", you instead get 96 of these

Severity Code Description Project File Line Suppression State Error CS0006 Metadata file 'M:\Projects\ASP.NET\ABP\src\MicroserviceTest3\services\administration\src\MicroserviceTest3.AdministrationService.Application.Contracts\bin\Debug\netstandard2.0\MicroserviceTest3.AdministrationService.Application.Contracts.dll' could not be found MicroserviceTest3.DbMigrator M:\Projects\ASP.NET\ABP\src\MicroserviceTest3\shared\MicroserviceTest3.DbMigrator\CSC 1 Active

Edit 3:

Seems like you have to do a "dotnet build /graphBuild" in the solution directory first, it seems to sort out the problems.

Developing a microservice solution is different from a single ASP.NET Core project development. You must install some mandatory tools, install certificates, and run specific commands. These are all explained at https://docs.abp.io/en/commercial/latest/startup-templates/microservice/get-started

please check out this document to understand how to start the microservice solution

did you also update your ABP Suite to v7.2.2 ABP Suite and your project version must be the same