Seems like abp bundle command is not working as it should in a MAUI Blazor project (created via the MAUI Blazor template in ABP Suite), at least not according to documentation.
"bundle This command generates script and style references for ABP Blazor WebAssembly and MAUI Blazor project and updates the index.html file. It helps developers to manage dependencies required by ABP modules easily. In order bundle command to work, its executing directory or passed --working-directory parameter's directory must contain a Blazor or MAUI Blazor project file(*.csproj)."
abp bundle --maui-blazor ABP CLI 8.2.0 Unsupported project type. Project type must be Microsoft.NET.Sdk.BlazorWebAssembly. Unsupported project type. Project type must be Microsoft.NET.Sdk.BlazorWebAssembly. Volo.Abp.Cli.Bundling.BundlingException: Unsupported project type. Project type must be Microsoft.NET.Sdk.BlazorWebAssembly. at Volo.Abp.Cli.Bundling.BundlingService.CheckProjectIsSupportedType(String projectFilePath, String projectType) in D:\ci\Jenkins\workspace\abp-volo-release\abp\framework\src\Volo.Abp.Cli.Core\Volo\Abp\Cli\Bundling\BundlingService.cs:line 333 at Volo.Abp.Cli.Bundling.BundlingService.BundleAsync(String directory, Boolean forceBuild, String projectType) in D:\ci\Jenkins\workspace\abp-volo-release\abp\framework\src\Volo.Abp.Cli.Core\Volo\Abp\Cli\Bundling\BundlingService.cs:line 50 at Volo.Abp.Cli.Commands.BundleCommand.ExecuteAsync(CommandLineArgs commandLineArgs) in D:\ci\Jenkins\workspace\abp-volo-release\abp\framework\src\Volo.Abp.Cli.Core\Volo\Abp\Cli\Commands\BundleCommand.cs:line 47 at Volo.Abp.Cli.CliService.RunInternalAsync(CommandLineArgs commandLineArgs) in D:\ci\Jenkins\workspace\abp-volo-release\abp\framework\src\Volo.Abp.Cli.Core\Volo\Abp\Cli\CliService.cs:line 173 at Volo.Abp.Cli.CliService.RunAsync(String[] args) in D:\ci\Jenkins\workspace\abp-volo-release\abp\framework\src\Volo.Abp.Cli.Core\Volo\Abp\Cli\CliService.cs:line 80 Unhandled exception. Volo.Abp.Cli.Bundling.BundlingException: Unsupported project type. Project type must be Microsoft.NET.Sdk.BlazorWebAssembly. at Volo.Abp.Cli.Bundling.BundlingService.CheckProjectIsSupportedType(String projectFilePath, String projectType) in D:\ci\Jenkins\workspace\abp-volo-release\abp\framework\src\Volo.Abp.Cli.Core\Volo\Abp\Cli\Bundling\BundlingService.cs:line 333 at Volo.Abp.Cli.Bundling.BundlingService.BundleAsync(String directory, Boolean forceBuild, String projectType) in D:\ci\Jenkins\workspace\abp-volo-release\abp\framework\src\Volo.Abp.Cli.Core\Volo\Abp\Cli\Bundling\BundlingService.cs:line 50 at Volo.Abp.Cli.Commands.BundleCommand.ExecuteAsync(CommandLineArgs commandLineArgs) in D:\ci\Jenkins\workspace\abp-volo-release\abp\framework\src\Volo.Abp.Cli.Core\Volo\Abp\Cli\Commands\BundleCommand.cs:line 47 at Volo.Abp.Cli.CliService.RunInternalAsync(CommandLineArgs commandLineArgs) in D:\ci\Jenkins\workspace\abp-volo-release\abp\framework\src\Volo.Abp.Cli.Core\Volo\Abp\Cli\CliService.cs:line 173 at Volo.Abp.Cli.CliService.RunAsync(String[] args) in D:\ci\Jenkins\workspace\abp-volo-release\abp\framework\src\Volo.Abp.Cli.Core\Volo\Abp\Cli\CliService.cs:line 80 at Volo.Abp.Cli.Program.Main(String[] args) in D:\ci\Jenkins\workspace\abp-volo-release\abp\framework\src\Volo.Abp.Cli\Volo\Abp\Cli\Program.cs:line 43 at Volo.Abp.Cli.Program.<Main>(String[] args)
Will you please refund ticket with this being a confirmed bug/problem? Thanks.
THe issue has been fixed
https://github.com/volosoft/volo/pull/17940
Is that a public repo as the link isn't working?
You can report all your ABP-related issues on this platform.
Other platforms are for open-source users.
We read all these posts and take necessary actions.
PS: You can still use the following platforms to find a community-supported solution.
- https://github.com/abpframework/abp
- https://stackoverflow.com/questions/tagged/abp-framework
- https://discord.gg/abp
Hi @alper, When you say, “We read all these posts and take necessary actions.” does this mean if my previous posts were read, and no action was taken, they were rejected or what?
Thanks
The fact that your question still remains unanswered is a bit worrying.
When creating/generating new Entities in ABP Suite, there are many many not founds appearing in the output log like this. Guessing that might be part of the reason why ABP Suite feels so much slower in 8.2 than previous versions.
info : GET https://nuget.abp.io/***/v3/package/volo.abp.commercial.suitetemplates/8.2.0/volo.abp.commercial.suitetemplates.8.2.0.nupkg info : NotFound https://nuget.abp.io/***/v3/package/volo.abp.backgroundjobs.domain/index.json 89ms info : NotFound https://nuget.abp.io/***/v3/package/volo.abp.blobstoring.database.domain/index.json 91ms info : NotFound https://nuget.abp.io/***/v3/package/volo.abp.permissionmanagement.domain.openiddict/index.json 89ms
(Replaced GUID with ***)
I think it should stay. We can find bugs in the release version
My bad, I though it was only for RC versions. Which OP kind of suggest as well.
8.2 has apparently been released now so this thread should probably be closed.