I am trying to initialise an existing solution that loads fine in visual studio and is Blazor / Microservices based.
If I initialise each solution or microservice solution they work fine however if I try to initialise the main solution which has all projects into a single solution with 302 projects I get the following error.
I am running on Windows 11
Logs
2024-04-24 22:47:37.921 +10:00 [WRN] Exception of type 'Volo.Abp.Studio.AbpStudioException' was thrown. Volo.Abp.Studio.AbpStudioException: Exception of type 'Volo.Abp.Studio.AbpStudioException' was thrown. at Volo.Abp.Studio.Modules.ModuleManager.CreateFolderAsync(String modulePath, String folder) at Volo.Abp.Studio.Initializer.ModuleInitializer.Dj4RL1f3Wr(String , String ) at Volo.Abp.Studio.Initializer.ModuleInitializer.UtsR2fpR9p(String , Boolean ) at Volo.Abp.Studio.Initializer.ModuleInitializer.InitializeAsync(String modulePath, Boolean skipExisting) at Volo.Abp.Studio.Initializer.SolutionInitializer.InitializeAsync(String directoryPath, String solutionName) at Volo.Abp.Studio.UI.Commands.InitSolutionCommandFactory.jgiB46XYTk() 2024-04-24 22:47:37.921 +10:00 [WRN] Code:AbpStudio:InvalidFolderName 2024-04-24 22:47:37.921 +10:00 [WRN] Details: 2024-04-24 22:47:37.922 +10:00 [WRN] ---------- Exception Data ---------- Name = ../../services/identity/src
Ok. Will raise with ASP.NET Core team.
Thx
Hi
No you cannot do that as it need to resolve to a type within the swagger definition. This will cause the schema to be invalid
"text/json": { "schema": { "$ref": "#/components/schemas/Volo.Abp.Application.Dtos.ListResultDto1Volo.Abp.Identity.OrganizationUnitWithDetailsDtoVolo.Abp.Identity.Pro.Application.ContractsVersion7.2.3.0CultureneutralPublicKeyTokennull" } }
hi
I downloaded your project. How can I get
Parsing error(s)
?
If you use https://editor.swagger.io/ to validate it you will see the parsing issue
Hi
If you create a fresh application using suite, abp new BookStore -t app-pro, then add the CMS suite and start the application up.
Update the .Web as below which should fix the issue.
private void ConfigureSwaggerServices(IServiceCollection services) { services.AddAbpSwaggerGen( options => { options.SwaggerDoc("v1", new OpenApiInfo { Title = "BookStore API", Version = "v1" }); options.DocInclusionPredicate((docName, description) => true); options.UseInlineDefinitionsForEnums(); options.UseAllOfToExtendReferenceSchemas(); options.CustomSchemaIds(type => type.FullName); } ); }
If you then open the swagger definition https://localhost:44351/swagger/v1/swagger.json and look at line 7026 and many others you will see that they violate the open api specification.
"$ref": "#/components/schemas/Volo.Abp.Application.Dtos.PagedResultDto`1[[Volo.Abp.AuditLogging.EntityChangeDto, Volo.Abp.AuditLogging.Application.Contracts, Version=7.2.3.0, Culture=neutral, PublicKeyToken=null]]"
I would be happy to send you a runnable application if you drop me you email?
THanks
Hi
If you have a look at my snippet that configuration has already been applied and the issue is still occuring.
This is important as in the cloud we use API gateway instead of ocelot for on-premise so the swagger definitions need to be confirming to the openapi spec.
Thanks
I have sent you a private email with the connection string as requested
Hi
Can I ask how we get the patch version?
Thanks
Same