HI @EngincanV did your try blazor ui? I capture my opreating screen in mp4,may I send to you?
Yes, I've tried Blazor UI and I could successfully generate CRUD pages.
You can send the video to engin.veske@volosoft.com.
Hi @mc86, I've tried just before. I could successfully generate CRUD pages and not encounter with any dependency resolution problem. But as @gterdem mentioned, i use the dotnet build /graphBuild
command in my root directory to ensure the solution is completely built.
Can you first execute the delete-bin-obj-folders.bat
file to delete all bin/obj folders that generated before and then run the dotnet build /graphBuild
on your root directory?
up to 5.0 rc1 also didn't work.as the same as4.4.4
ABP Commercial 5.0.0-rc.1 release has just been completed, so when you updated to 5.0.0-rc.1
it probably still used the v4.4.4 or it should have given some errors.
2.use "abp add-package Volo.Abp.Commercial.SuiteTemplates" in my blazor project. (if i don't use this i will get can't find Commercial.SuiteTemplates.dll error when generating
I've encountered this problem with MVC page generation, it really sometimes happen but after adding this .dll file into the relevant project directory, I could generate CRUD pages for MVC UI as well.
Hi @improwise, I've created an app-pro template with Blazor Server as UI and EF-Core as the database provider (in v4.4.4). Then, I could successfully generate CRUD pages for my Book entity.
For some strange reason, we notice that the error messages seem to be truncated.
Yes, I reproduced this problem using VS 2022. But there is not any problem, when using dotnet run
command or using other IDE such as Rider. There could be a problem in VS 2022, we will investigate this, thanks.
Hi @mc86, I will check and write you back asap.
Hi @mc86, after creating the new microservice did you follow the documentation?
After applyng the steps in the documentation you should be able to generate CRUD pages for your microservice.
Hi @LawrenceKwan, *.EntityFrameworkCore.DbMigrations
project is removed from the solution.
From v4.4.4 DbContexts are unified in the *.EntityFrameworkCore
project. (See the related issue)
*.EntityFrameworkCore.DbMigrations
project is removed and DbContexts are unified you can read this article.My Angular and API are are hosted in the same node in the IIS - so do i have to keep the angular url empty ? I tried removing the key it doesn't work.
No, they both need to be the same then.
Did you change your appsettings.json when migrating the database (in DbMigrator project)?
{
"ConnectionStrings": {
"Default": "Server=localhost;Database=MyApp;Trusted_Connection=True"
},
"IdentityServer": {
"Clients": {
//...
"MyProjectName_App": {
"ClientId": "MyProjectName_App",
"RootUrl": "http://116.90.234.198:8080" //change root url
},
//...
}
}
}
Hi @mc86, as @berkansasmaz mentioned product service
does not support code generation with Suite in versions 4.*.*
. But you can create a new microservice and then generate CRUD pages for it.
Hi @LawrenceKwan, do you use the Redis? It can be really helpful to downgrade the response time.