updating to the latest version may fix it.
go to this URL and write us the response api/abp/api-definition/
This is in the roadmap but there's no blocking case that implementing a N:N relationship. See
1- https://docs.microsoft.com/en-us/ef/core/modeling/relationships?tabs=fluent-api,fluent-api-simple-key,simple-key#many-to-many 2- https://www.learnentityframeworkcore.com/configuration/many-to-many-relationship-configuration
I'm not sure if this helps https://docs.abp.io/en/commercial/latest/modules/file-management But I'd do it without File Management. It'd be a forced solution.
hi @murat.yuceer,
can you give more details about adding a module issue. you created a Blazor solution. Then you add a module. Which module? How did you add (as NuGet reference, project reference)? what's generated? did you generate a CRUD page using Suite?
for the Angular code generation issue; the problem is related to this commit https://github.com/angular/angular-cli/commit/5ce621e371166af4994cae5cc9a456ee683cbaf0 we'll fix this but there's a workaround of this problem.
Open this file:
C:\YourProject\angular\.suite\schematics\commands\entity\index.js
Go to line 56 and replace it with the following:
const abpSchematics = './node_modules/@abp/ng.schematics/collection.json';
@lwilbourn @rcalv002 I reproduced the issue. There's a problem generating the Angular code. Created an internal issue. Will be fixed in v4.0.1
@christianharo I couldn't reproduce "No gulpfile found" problem. Tried on 2 different projects
@christianharo can you add the below line to your NuGet.config in your root directory of the solution.
<add key="BlazoriseMyGet" value="https://www.myget.org/F/blazorise/api/v3/index.json" />
I created a new v4.0 project and my Suite is also 4.0
There was no error creating entities.
I guess your project is v4.0.0-RC ...
this character is in these templates: createjs_DropdownFunctions.txt , editjs_DropdownFunctions.txt and Indexjs_NavigationPropertyDropdownOpenEditModalArgs.txt.
When I check it in v3.3.2 (Suite) I don't see the dash char.
can you double check that you are running on 3.3.2. this was an old issue and must be fixed in 3.3.2
