Activities of "chrisalves"

• ABP Framework version: v5.2.0
• ABP Suite: Yes, v5.2.0
• Template Type: Application Template
• UI type: Blazor WebAssembly
• DB provider: EF Core
• Database: SQL Server
• Tiered (MVC) or Identity Server Separated (Angular): There is no separated Identy Server.
• Exception message and stack trace: Blazor App error when run using Visual Studio (CTRL+F5)
• Steps to reproduce the issue:" I created a simple application to try the feature Many-to-Many, with a single field (name) considering 2 entitys (product and catalog). The application worked fine, I was able to run the HttpApi.Host and Blazor. After that, I decided to create additional fields on ABP Suite in the Entity Products. After that, I selected to "Save and Generate". This process took a long time and at the end I saw an error message related to the Migration. I repeated few times the execution of "Save and Generate" but now it runs without problem but something was not done in the solution because the Blazor is not running anymore.

If I select to run the Last Sucessful build, it runs but it does not present the new fields created. I do not know how to solve the issues related to this Bulld errors.

Hi,

I was working today with ABP Suite and also with Visual Studio for Windows, building a new solution. I realized that the ABP suite stopped work and I closed the command prompt and tried to run/load it again. I realized the Suite was not being launched in the browser, so I rebooted the pc few times, also removed the ABP suite, rebooting again. Reinstalled and the same problem persists. I cleaned browser cache and history, but it is still the same, not being loaded.

Any thoughts about it?

Bellow you will see the answers required, also two screen shots for the command prompt and the browser. Thanks for your support.

If you're creating a bug/problem report, please include followings:

• ABP Framework version: v5.1.3
• UI type: Blazor
• DB provider: EF Core
• Tiered (MVC) or Identity Server Separated (Angular): no
• Exception message and stack trace:
• Steps to reproduce the issue:"
•