Why start template not published when a new version released? it is a long time can not get the template 8.3.1 after it released, abp cli and abp studio also upgraded to latest version.
What is the reasoning for the new directory structure of solutions created with ABP Suite / ABP Studio? It used to be that you got a folder for each "application" under the main directory like "MyApplication" = > "aspnet-core", "angular", "react-native" etc but now it seems to be that angular and react-native folders are moved within what used to be the aspnet-core folder. So now you have SLN file and "test" folder for aspnet-core stuff right next to your angular and react-native folders, even though they are stand alone applications (kind of).
Is this even an intended change or some kind of bug? There might be advantages of this as well, like using only one repo for everything etc (which could be both good or bad depending on personal preference).
You can of course change this after creation, but I would imagine that doing that would break code generation etc?
Is there a guide on if we want to tidy this up a bit and still make sure that ABP Suite etc works (and that won't break with updates etc)?
I also want to know why change the structure, difficult to maintain code changes history in git
After upgrading version from 8.2.1 to 8.30, even run the "install-libs" command, it still get below errors caused the datatable.net component cannot running:
Hi,
It works for me
My steps
- Update
run-tye.ps1<# Check development certificates #> if (! ( Test-Path ".\etc\dev-cert\localhost.pfx" -PathType Leaf ) ){ Write-Information "Creating dev certificates..." cd ".\etc\dev-cert" .\create-certificate.ps1 cd ../.. } cd "./shared/PlayPoint.DbMigrator" dotnet run cd ../.. <# Run all services #> tye run --watch
- Update connection strings
- run
create-certificate.ps1- run
run-tye.ps1Make sure the Redis, RabbitMQ are available
thanks！I think I found problem, there were some wrong queues in my rabbitmq, and when I removed them and rerun them, it worked. good luck for you！
If you need, I can provide the solution of the compressed package, because it is only generated using abp suite, there is no other content.
okay, please my email is shiwei.liang@volosoft.com
I have sent an email to your work email, thank you again for your help!
What can I do to get my admin role fully authorized? Hope to get your help.
The other one works without any exceptions, and my admin role can be authorized to complete
I am not sure why this is caused, whether it is caused by the network or suite tools?
I think this is caused by the docker environment. You can try to clean up the docker container again.
thanks for your reply！ but I am not using docker, I modified the run-tye.ps1 script to remove the containerization part, I think this should not have a bad effect, I have tried to recreate my database, but it does not work.
If you need, I can provide the solution of the compressed package, because it is only generated using abp suite, there is no other content.
As you can see, I just changed the connection string, but the permissions of the admin role are incomplete
Hi,
I didn't see any error message in the logs
Yes, but after I started the program using tye tool, the permission scope of the admin user after logging in did not include products, saas, and some others. I tried to generate a new solution using suite tool and found that this problem was not inevitable. Two of the three microservice solutions I generated had these exceptions. [WRN] Could not find IdentityClientConfiguration for AbpMvcClient. Either define a configuration for AbpMvcClient or set a default configuration. [WRN] Could not find the localization resource ProductService on the remote server! [WRN] Could not find the localization resource LeptonX on the remote server! As you can see, these issues do not affect the application up and running, but my admin user has incomplete permissions
The other one works without any exceptions, and my admin role can be authorized to complete
I am not sure why this is caused, whether it is caused by the network or suite tools?
