Hi @sgarad
Does the problem persist after you give the missing permissions to admin on Identity Management>Roles page? or are not they present in permissions window?
Hi @Navneet
Is PowerShell installed in your system as dotnet tool? (dotnet tool list -g)
if I run the project from the terminal, I am getting errors in the console:
You can try running abp install-libs from the terminal before running the solution.
We've detected that AuditLogging.Pro source code is not published correctly.
It will be resolved in next framework release (v8.2.3 i guess).
Hi @rwright-ruhealth
I've created an internal issue for this. It will be resolved in next versions.
Hi @sairam.thirupathuru
This command basically runs dotnet ef database update command in the target package's directory. You can run it yourself and see if the problem is related with studio.
You can also see the error details in logs section, next to Notifications.
Thank you for the feedback.
I'll create internal issues.
To monitor an application, you need to add the following package to the application:
-> Package Name: Volo.Abp.Studio.Client.AspNetCore (version 0.6.2 or 0.6.3, according to the ABP Studio version installed)
-> Module Name: AbpStudioClientAspNetCoreModule (namespace:Volo.Abp.Studio.Client.AspNetCore)
and:
app.UseAbpStudioLink();
Hi @mrbrl
Manually removed the new Web Project by editing the .abpmdl and .abpsln files
You can do this operation on solution explorer (removing/adding projects). I guess somehow you have corrupted the .abpsln file.
After the initialization , the Solution Runner tree remains consistently empty.
Initialize Existing Solution comand doesn't create run profiles, thus you need to create a new solution profle and add the projects.
Additionally, microservice startup template generated by ABP Suite is completely different that the template generated by ABP Studio. (fyi)
Hi
This is still not supported. You can manually change the base class after code generation. (then you may need to create new migrations)