Aktivity „okains“

• ABP Framework version: v5.3.4
• UI type: Blazor Server
• DB provider: EF Core
• Tiered (MVC) or Identity Server Separated (Angular): no
• Exception message and stack trace:
• Steps to reproduce the issue:"

I have been following the instructions provided to fully customize the Login / Register page UI. All is working well apart from the fact that the Default.cshtml that I have in the Account folder is not being picked up at all. The standard Default.cshtml UI from the Lepton theme is still being used / displayed.

Is there a config setting I am missing, or something else I need to look for here?

<br> Here is a screenshot of my project / folder structure:

• ABP Framework version: v4.4.3
• UI type: Blazor
• DB provider: EF Core
• Tiered (MVC) or Identity Server Separated (Angular): no
• Exception message and stack trace:
• Steps to reproduce the issue:"

I would like to know what is the best practice using ABP for creating a Many to Many relationship with IdentityUser? With Core EF5 we can add nav properties to our entities to make this easy, as documented here : https://www.davidhayden.me/blog/ef-core-5-many-to-many-relationships.

I created 2 test case entities, M2MUser & M2MGroup, added the navigation collections i.e. ' public ICollection<M2MUser> M2MUsers { get; set; } ' in the domain project and ran a DB Migration and everything worked as it should do, the M2MUserM2MGroup table was created in the DB.

However we can not add a collection property to the IdentityUser class, and there is no longer a derived ABPUser class. If we want to add an M2M relationship with a 'User' should we wrap IdentityUser? This seems like the wrong way forward, am I missing something? Can you please provide the best practice, using ABP, for this situation?

If this helps, here is the part of my model that I am trying to implement. 'User' is an IdentityUser. 'OnboardingGoal' is an entity I have created using ABPSuite. UserOnboardingGoal should be implicitly generated by EF, so it is not explicitly created using ABPSuite.

Thanks,

Karim

An update on this:

I was able to work around this by using a less complex password. I had initially used long random passwords that contained many special characters. These would work when connecting remotely to an Azure SQL DB using SSMS, but would not work using DBMigrator against an Azure SQL DB.

I reduced the length and complexity of the passwords that I use, kept them to UpperCase/LowerCase/Numbers/[*!"] and DBMigrator now runs.

Hope that helps someone else get past this.

ABP Framework version: v4.4.2 UI type: Blazor DB provider: EF Core Tiered (MVC) or Identity Server Separated (Angular): no

Exception message and stack trace: The project name is invalid! Please specify a different name. Volo.Abp.Cli.CliUsageException: The project name is invalid! Please specify a different name.

Steps to reproduce the issue:

It seems like it is impossible to create a new project/SLN in ABP Suite that contains/ends with "Blazor", like "TestProjectBlazor". Generating the project online with the same name and then open it in ABP Suite seem to work though. No problem creating something like "TestProjectAngular".

• at Volo.Abp.Cli.Commands.NewCommand.ExecuteAsync(CommandLineArgs commandLineArgs) in D:\ci\Jenkins\workspace\abp-commercial-release\abp\framework\src\Volo.Abp.Cli.Core\Volo\Abp\Cli\Commands\NewCommand.cs:line 66 at Volo.Abp.Suite.Areas.AbpSuite.CrudPageGenerator.Services.SolutionService.CreateSolutionAsync(CreateSolutionModel input) at lambda_method2438(Closure , Object ) at Microsoft.AspNetCore.Mvc.Infrastructure.ActionMethodExecutor.AwaitableObjectResultExecutor.Execute(IActionResultTypeMapper mapper, ObjectMethodExecutor executor, Object controller, Object[] arguments) at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.<InvokeActionMethodAsync>g__Awaited|12_0(ControllerActionInvoker invoker, ValueTask`1 actionResultValueTask) at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.

I ran into this also and created a ticket : https://support.abp.io/QA/Questions/1706/Error-Project-Name-is-Invalid-when-creating-a-Blazor-Server-project-using-Suite

there is an open issue for this, but for now you can not use 'Blazor' in the project name.

https://github.com/abpframework/abp/issues/9853

Any idea when this fix will be available?

ABP SUITE GENERATE ENTITY BUG

ABP Suite, Blazor Server Project, error on SaveAndGenerate entity AFTER having published once. Seems to be looking for a {ProjectName}WEBAutoMapperProfile.cs file that does not exist , see file attached. This file isn't even called {ProjectName}WebAutoMapperProfile.cs in a Blazor project, it is {ProjectName}AutoMapperProfile.cs . In either case, the file does not exist in the location and this fails every time.

Steps To Reproduce:

1. Using ABP Suite, create New Blazor Server Project
2. PUBLISH the project ( anywhere )
3. Create a new entity, SaveAndGenerate

Also I am still waiting on a patch for the other ABP Suite Blazor Server Code Gen bug I reported 1 week ago:

Blazor Server & ABP Suite Code Gen Issue #1721

#1721 is still unfixed, though there is a workaround. For this issue there is no workaround that I can see, I tried renaming the AutoMapperProfile.cs file and adding it to the location but that didn't work.

These are 2 SERIOUS BLOCKERS for me and any other Commercial customer using Blazor Server. I can not continue working on my current project as I have ~50 entities to generate. Can we please get a patch ASAP?

Thanks,

Karim

Hi,

Yes, I figured that out after experimenting a few times and just settled on using BZ instead. However 'Blazor' is and should be allowed in project names. If you look at a lot of the online tutorials / documentation they use Blazor in the project name extensively. Is there a reason why you decided to make it invalid in this case?

I am having problems generating an entity with ABP Suite. For me, the project name 'BZServerPlay' is appended to the namespace of the razor file for all ABP Suite generated entities. This causes the build to fail at the point of DB Migration. When I remove the extra .BZServerPlay namespace then everything builds with no problems. Please see the attached screenshots for more details.

The work around is to generate as is, with the exception thrown. Then modify the namespace by removing the last .BZServerPlay from the generated namespace of 'BZServerPlay.Blazor.Pages.BZServerPlay'. , then generate without UI. Then everything works as expected.

But this can only be temporary! Please let me know what the situation is here, if this is a bug please let me know when fixed.

Thanks,

Karim

Check the docs before asking a question: https://docs.abp.io/en/commercial/latest/ Check the samples, to see the basic tasks: https://docs.abp.io/en/commercial/latest/samples/index The exact solution to your question may have been answered before, please use the search on the homepage.

If you're creating a bug/problem report, please include followings:

• ABP Framework version: v4.4.0
• UI type: Blazor
• DB provider: EF Core
• Tiered (MVC) or Identity Server Separated (Angular): no
• Exception message and stack trace: image attached
• Steps to reproduce the issue:"

It seems that you added this validation in 4.4 :

https://github.com/abpframework/abp/issues/8959

and I am guessing you are validating out the keyword 'Blazor' for project names? When I changed from Blazor, to 'BZ' then the project was created.

I can create a project using VS with the keyword 'Blazor' in the project name. This took longer than it should have to work through, can you confirm that this is a bug in your code or if I have missed something?

Thanks,

Karim

I am trying to create a Blazor Server project using ABP Suite. I consistently get Project Name Invalid Errors, and have tried different project names but still the same error.

I have attached screenshots of my input, and also of the exception thrown by the CLI. Can you let me know if this is a bug or if I am doing something wrong? Need to get this project created as soon as possible.

Thanks,

Karim

Check the docs before asking a question: https://docs.abp.io/en/commercial/latest/ Check the samples, to see the basic tasks: https://docs.abp.io/en/commercial/latest/samples/index The exact solution to your question may have been answered before, please use the search on the homepage.

If you're creating a bug/problem report, please include followings:

• ABP Framework version: v4.4.0
• UI type: Blazor
• DB provider: EF Core
• Tiered (MVC) or Identity Server Separated (Angular): no
• Exception message and stack trace: attached
• Steps to reproduce the issue:"