أنشطة "improwise"

Creating a new solution for MAUI Blazor in ABP Suite RC3 always seem to give the error below when trying to run it. Other MAUI related projects inside of ABP and outside seem to work though, like if you select to have a ABP Suite create a Mobile MAUI app. So it seems to be related to to particular template.

Severity Code Description Project File Line Suppression State Error DEP1000: Cannot copy file "C:\Users\***\.nuget\packages\volo.abp.aspnetcore.components.web.leptonxtheme\3.2.0-rc.3\staticwebassets\side-menu\libs\bootstrap-datepicker\css\bootstrap-datepicker.standalone.css.map" to layout "M:\Projects\ASP.NET\ABP\src\ABPTester6\src\ABPTester6.MauiBlazor\bin\Debug\net8.0-windows10.0.19041.0\win10-x64\AppX\wwwroot\_content\Volo.Abp.AspNetCore.Components.Web.LeptonXTheme\side-menu\libs\bootstrap-datepicker\css\bootstrap-datepicker.standalone.css.map". DirectoryNotFoundException - Could not find a part of the path 'M:\Projects\ASP.NET\ABP\src\ABPTester6\src\ABPTester6.MauiBlazor\bin\Debug\net8.0-windows10.0.19041.0\win10-x64\AppX\wwwroot\_content\Volo.Abp.AspNetCore.Components.Web.LeptonXTheme\side-menu\libs\bootstrap-datepicker\css\bootstrap-datepicker.standalone.css.map'. [0x80070003] ABPTester6.MauiBlazor

Edit:

Maybe this is casued by the long path problems in Windows and not ABP, will do further testing.

Edit 2:

Not ABPs fault, Microsoft apparently broke MAUI again https://github.com/dotnet/maui/issues/17828 (or Windows to be exact)

You may try the Solution 3 in the following documentation to overcome this issue. Visual Studo or any other IDe still can't work but you can build from terminal via dotnet CLI https://docs.abp.io/en/abp/8.1/KB/Windows-Path-Too-Long-Fix#solution-3

Thanks. I actually posted about another solution we came up with that works in Visual Studio as well. Perhaps not that pretty but we have been using it now for a while with the created ABP solution and it seems to work fine and also works from within Visual Studio.

https://github.com/dotnet/maui/issues/17828#issuecomment-2148408662

Creating a new solution for MAUI Blazor in ABP Suite RC3 always seem to give the error below when trying to run it. Other MAUI related projects inside of ABP and outside seem to work though, like if you select to have a ABP Suite create a Mobile MAUI app. So it seems to be related to to particular template.

Severity Code Description Project File Line Suppression State Error DEP1000: Cannot copy file "C:\Users\***\.nuget\packages\volo.abp.aspnetcore.components.web.leptonxtheme\3.2.0-rc.3\staticwebassets\side-menu\libs\bootstrap-datepicker\css\bootstrap-datepicker.standalone.css.map" to layout "M:\Projects\ASP.NET\ABP\src\ABPTester6\src\ABPTester6.MauiBlazor\bin\Debug\net8.0-windows10.0.19041.0\win10-x64\AppX\wwwroot\_content\Volo.Abp.AspNetCore.Components.Web.LeptonXTheme\side-menu\libs\bootstrap-datepicker\css\bootstrap-datepicker.standalone.css.map". DirectoryNotFoundException - Could not find a part of the path 'M:\Projects\ASP.NET\ABP\src\ABPTester6\src\ABPTester6.MauiBlazor\bin\Debug\net8.0-windows10.0.19041.0\win10-x64\AppX\wwwroot\_content\Volo.Abp.AspNetCore.Components.Web.LeptonXTheme\side-menu\libs\bootstrap-datepicker\css\bootstrap-datepicker.standalone.css.map'. [0x80070003] ABPTester6.MauiBlazor

Edit:

Maybe this is casued by the long path problems in Windows and not ABP, will do further testing.

Edit 2:

Not ABPs fault, Microsoft apparently broke MAUI again https://github.com/dotnet/maui/issues/17828 (or Windows to be exact)

Delete of Entities in ABP Suite does not seem to do anything in RC3. It claims to have deleted the Entity but tables are still in database and code is still in the solution. It seems it just was deleted from ABP Suite itself. I assume the idea is that it should actually be deleted from the solution and maybe database?

Assume you are aware of the concept of soft delete: https://docs.abp.io/en/abp/latest/Data-Filtering

Check in the database the IsDeleted column. If you want to remove from the database, then you need to do a Hard Delete.

I am not part of the ABP team - but this is not the right channel for this question/feedback. ABP are trying to get 8.2 finished and, with respect, this is noise they don't need.

I suggest reading more carefully before commenting - this is about deleting entities in ABP Suite. Apparently this has never worked the way you can assume it to when you have a delete button right next to a save and generate one. If the current behavior remains unchanged, it should at least be made more clear that it only deletes entities from ABP Suite.

https://support.abp.io/QA/Questions/639/ABP-Suite-does-not-delete-GRUD-Entity-cleanly

Edit:

Correction, the confirm message for the delete button actually say that it will only delete from ABP Suite upon closer inspection. But main issue, at least according to me, remains that you would have to manually delete everything. What is the reasoning behind this behavior? That said, I can understand that scripting deletion could be a challenge, probably more so than updates and new entities.

Delete of Entities in ABP Suite does not seem to do anything in RC3. It claims to have deleted the Entity but tables are still in database and code is still in the solution. It seems it just was deleted from ABP Suite itself. I assume the idea is that it should actually be deleted from the solution and maybe database?

In a Blazor app (but guessing it might be in all kinds of projects), when a user only has read permission to an entity, the Actions button is still displayed even though the user has no permissions to do anything. When you click it, it appears as nothing happens but in fact there is a very small empty menu that shows up (as the user has no available actions). This is quite confusing to the user.

The permissions dialog is in itself a bit confusing but I assume that this is the configuration you should have for "read only with no actions". That in itself should probably also be clarified/improved as it isn't obvious that the checkbox on the same line as the entity means "read only".

I totally agree with that and noted this confusion. I'll try to update the documentation and clarify this situation.

Thanks. Please note that this is also, AFAIK, a bug as there should be no actions menu rendered when there are no actions available. For the UI, I believe that it would be much clearer if the Entity name was not selectable but instead a "View" permission was displayed in the submenu.

You can't create an entity with ABP Suite + ABP Cli 8.2.0-rc.3

You should ensure that your application's version is v8.2.0-rc.3. There is a Volo.Abp.Commercial.SuiteTemplates in the domain layer and you should check the related .dll under the bin directory. (Because, we already checked generating entities and could not found any problem, so it's probably related that)

At least for me both are updated to RC3 and apparently at least two of us received similar errors but only for the Blazor WebApp template (or at least not the Blazor Server one, have not tried any more yet).

In a Blazor app (but guessing it might be in all kinds of projects), when a user only has read permission to an entity, the Actions button is still displayed even though the user has no permissions to do anything. When you click it, it appears as nothing happens but in fact there is a very small empty menu that shows up (as the user has no available actions). This is quite confusing to the user.

The permissions dialog is in itself a bit confusing but I assume that this is the configuration you should have for "read only with no actions". That in itself should probably also be clarified/improved as it isn't obvious that the checkbox on the same line as the entity means "read only".

With Blazor being more "build once, run everywhere" it would be nice if ABP Suite generated components to a separate class library instead of putting them in each project. You can of course do this yourself but that would probably break any further updates by ABP Suite. This is especially useful if you intend to use MAUI with Blazor Web View. For this to happen, ABP Suite would probably have to begin with actually generating components instead of just pages. I see that the latest versions of Blazor templates actually has a "Components folder in them" where the predefined ABP pages are located, but when you create a new page (entity) in ABP Suite, it actually creates a new "Pages" folder at the same level as the Components folder, so that you end up with 2 Pages folders. Not sure if this is intended or an error.

Maybe the Module Startup Template can be used for this even though a module and a component isn't really the same thing.

With the raising popularity of using Blazor in MAUI applications (BlazorWebView) to reuse code on all platforms, I think there should be an option to have ABP Suite generate a solution with that setup from the start. I guess the stuff already in the template to handle login, users, profiles etc. could just stay in XAML and then just simply add something like this if the options is selected

<BlazorWebView HostPage="wwwroot/index.html">
    <BlazorWebView.RootComponents>
        <RootComponent Selector="#app" ComponentType="{x:Type local:Main}" />
    </BlazorWebView.RootComponents>
</BlazorWebView>

When creating a Blazor solution also containing a MAUI project, when you try to login in the running MAUI app, you will be redirected to a login page in the web browser. The login itself seem to work find but the login page in the browser never seem to update to the usual "Authentication completed, you can now close this window and return to the app" or something like that but instead will just continue to show the login screen. This is running locally as I windows app I might add, could be different on Android, iOS etc.

This is how the web page looks even though login has been completed successfully.