all reported bugs are fixed. for minor versions, there's no release notes
hi @Leaf,
UI Framework is not meaningful for modules because a module solution has both Angular and MVC. So you can ignore the UI Framework : Angular. Probably this text will be removed in the next versions for modules.
@Johannes thanks for your feedback. it's reproduced and fixed in v3.1.1
hi quan.truong.anh@gmail.com
I can verify that different namespace issue has been resolved in 3.1.1.
This minor version will be released soon.
If you see such an error while you are generating a page with ABP Suite, it means your current EF Core tools needs to be updated.
The EF Core tools version '3.1.5' is older than that of the runtime '3.1.6'. Update the tools for the latest features and bug fixes.
You can update it with the following
dotnet tool update --global dotnet-ef
that's normal and by design.. when there's only MVC project then there'll not be an aspnet-core folder.
we fixed the issue and you will get the fixed version with v3.1.1 .
while we release v3.1.1 you can do the following workaround to continue your development.
Go to your project root path where you see aspnet-core folder.
create a new folder "angular".
go to the new folder angular and create a new folder and name it "angular" inside the "angular" folder.
then create ".suite" folder inside angular.
and create "schematics" folder inside ".suite".
and create "commands" folder inside "schematics".
so you'll have this folder structure:
angular\angular\.suite\schematics\commands
super! closing this
why you don't want to seed the tenant database?
use string.IsNullOrEmpty
