the only way is removing the [Authorize] attribute from Application Services.
If you want to guard some specific Web API actions, you can also put the [Authorize] attribute to your service methods .
@talha in the new version (v3.2.X) there shouldn't be files under %UserProfile%\.abp\suite\solutions\{solution-id}\entities\.
So the new location for entity files are in your solution folder. This is done because we wanted to include entity json files to the source-code system.
Find your entities in your-solution-root-direcroty\.suite\entities
hi,
please add "AbpLicenseCode": "xxxxxxxx" to your appsettings.json file
We'll add this in the next release
check that you have your entitites in the following directory
%UserProfile%\.abp\suite\solutions\{solution-id}\entities\
you can copy your entities from that folder to the following folder
your-solution-root-direcroty\.suite\entities
hi Chris, I reproduced the issue
Volo.Abp.AspNetCore.Mvc.UI.Theme.Shared.Demo project is missing on NuGet. We'll add this in v3.3.0
See the commit for that https://github.com/abpframework/abp/commit/0242db8d076e889513f95a293d48857a9a120fd6
Not to block you now, I'm sending the related DLL https://drive.google.com/file/d/1i8MvNX2kVAeeOIgPwAsQ5vTLy1_Udszb/view?usp=sharing
ok I reproduced it using private window
yes this might be the issue
The lepton styles are in this folder.
You need to open Volo.Abp.LeptonTheme.sln
After modifying scss files, build project to generate minified versions
normally this problem will not happe in your production environment. we as developers often recreate database, delete tenants etc. that's why we face this problem.
yes, if you change the database provider, you need to remove all migrations and add again, because each DBMS has its own data limitations. please read https://docs.abp.io/en/abp/latest/Entity-Framework-Core-Other-DBMS
