Hello, After we updated to Abp 8.2 (and migrated to Blazor WebApp) any solution is getting the error Cannot find the directory. This error seems to be related only with Blazor WebApp. Any new solution shows the same error.
- ABP Framework version: v8.2.1
- UI Type: Blazor WebApp
- Database System: EF Core (PostgreSQL)
- Tiered (for MVC) or Auth Server Separated (for Angular): no
- Exception message and full stack trace: Relevante log in .abp\suite\logs.txt 2024-08-12 15:23:03.145 -03:00 [INF] Executed endpoint 'Volo.Abp.Suite.Controllers.AbpSuiteController.IsSuiteOutDatedAsync (Volo.Abp.Suite)' 2024-08-12 15:23:03.145 -03:00 [INF] Request finished HTTP/1.1 GET http://localhost:3000/api/abpSuite/is-suite-outdated - 200 null application/json; charset=utf-8 24.8838ms 2024-08-12 15:23:03.236 -03:00 [WRN] ---------- RemoteServiceErrorInfo ---------- { "code": null, "message": "Cannot find the directory ", "details": null, "data": {}, "validationErrors": null }
2024-08-12 15:23:03.236 -03:00 [WRN] Cannot find the directory Volo.Abp.UserFriendlyException: Cannot find the directory at Volo.Abp.Suite.Areas.AbpSuite.CrudPageGenerator.Services.SuiteAssemblyService.hJD6zcs8Vu(String ) at Volo.Abp.Suite.Areas.AbpSuite.CrudPageGenerator.Services.SuiteAssemblyService.rdx6U06fb7(Solution , String& ) at Volo.Abp.Suite.Areas.AbpSuite.CrudPageGenerator.Services.SuiteAssemblyService.Sxd6kPKM08(Solution , String& ) at Volo.Abp.Suite.Areas.AbpSuite.CrudPageGenerator.Services.SuiteAssemblyService.AssemblyExists(Solution solution) at Volo.Abp.Suite.Areas.AbpSuite.CrudPageGenerator.Services.SolutionService.IsSolutionBuiltAsync(Guid solutionId) at Volo.Abp.Suite.Controllers.AbpSuiteController.IsSolutionBuiltAsync(Guid solutionId) at lambda_method1995(Closure, Object) at Microsoft.AspNetCore.Mvc.Infrastructure.ActionMethodExecutor.AwaitableObjectResultExecutor.Execute(ActionContext actionContext, 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.
- Steps to reproduce the issue:
- Create a new Solution: Layered, Blazor WebApp, EF Postgre (Abp Suite or Abp Studio)
- Open Suite and try add a Entity
The error cloud be by missing Templates, because in solutions with previews versions the templates tab open correctly.
We have last version of all tools (cli, sutie and studio). We also reinstall all of them.
7 Answer(s)
-
0
Hi, did you move your solution to another directory? Can you check the solution directory path in the appsettings.json file under the .abp/suite folder?
-
0
Hi, we didn't move. This happen with all projects with 8.2, even new ones. I have attached a simple demo create with suite with the problem. Also the current appsettings.json. All the paths in json seems ok.
https://www.dropbox.com/t/VcOff3kr1dCVp41X
-
0
Hi, we didn't move. This happen with all projects with 8.2, even new ones. I have attached a simple demo create with suite with the problem. Also the current appsettings.json. All the paths in json seems ok.
https://www.dropbox.com/t/VcOff3kr1dCVp41X
Hi, sorry for the late response, I reproduced the problem and created an issue for it. For a quick workaround, you can manually set the BlazorProjectDirectory in the appsettings.json file. It's under the
C:\Users\<username>\.abp\suitefolder. Find your solution by name and please set the BlazorProjectDirectory manually, then you should be able to generate CRUD pages. -
1
Hi, thanks for the responde, but we still are getting the same error. The BlazorProjectDirectory was already set in appsettings.json in our attachment and I double check in local env. Can you confirm that this is the right name? There is also the BlazorWebAppProjectDirectory. We are using the Blazor WebApp (that contains .Blazor and .Blazor.Client project). We have tried different combinations in both paths (with .Client and without .Client) , always restarting suite after, but without success. Maybe you can post the appsettings.json and we cloud do a diff compare. Thanks.
-
1
Hi, thanks for the responde, but we still are getting the same error. The BlazorProjectDirectory was already set in appsettings.json in our attachment and I double check in local env. Can you confirm that this is the right name? There is also the BlazorWebAppProjectDirectory. We are using the Blazor WebApp (that contains .Blazor and .Blazor.Client project). We have tried different combinations in both paths (with .Client and without .Client) , always restarting suite after, but without success. Maybe you can post the appsettings.json and we cloud do a diff compare. Thanks.
You should also manually set the HttpApiHostProjectDirectory and change the UiFramework as 7, sorry I forgot to mention that:
"UiFramework": 7, . . . "HttpApiHostProjectDirectory": "C:\\Dev\\Demo.Test\\src\\Demo.Test.HttpApi.Host",If you still can not generate CRUD pages, please let me know, so I can share all the solution info.
-
1
Hi, that solves, thanks!
-
-1
Since your problem is resolved and I refunded your ticket, I'm closing the question. Thanks again for reporting this problem. We fixed it and it will be included with the next release.
Regards.
