Activities of "yekalkan"

Hi @Spospisil

Untill we figure out the issue, following workaround may resolve it for you:

1. Open visual studio and create a new class library project
2. install Volo.Abp.Studio.Extensions.StandardSolutionTemplates to the project on manage nuget packages dialog.

This should bring the package to the cache.

I could not reproduce the problem.

Every time we modify a CRUD page and regenerate the list page (which uses the index.js file), this bug appears

Could you provide more details?

The new modules will continue being DDD layered.

Any update on this?

The issue is in the test process.

Can you ensure that anti-virus or something else is not blocking the file from read/write operations?

Hi @direccionti

Can you delete .abpstudio\state.json file in the solution, and then try again?

suite does not allow to load the whole microservice solution template as existing solution

You can add service by service. And then generate code on the services.

Hi @smansuri

It is a prioritized issue. We aim it to be resolved in the next release.

New microservice template is different then the old one. It is not about the ABP Framework version, the solution architecture is different. It is not possible to achive all features of ABP Studio with the old template.

Also, ABP Suite is used only for code generation. I guess it is not related with the case.

Hi @smansuri

It seems like your solution is created via old microservice template which is not compatible with ABP Studio.

We may suggest you to create a solution via new microservice template on ABP Studio, and continue your development with it if you can.