This issue has not been resolved https://commercial.abp.io/releases/pr/16413
It's still happening the issue with the test and the one-to-many relationship. You need to validate the one-to-many when it's related with a Detail in the Master/Detail functionality.
Steps to reproduce.
Create a Master Entity named "RelatedDemo" Create a Master Entity named "MasterDemo" Create a Detail for "Demo" and name it "DemoDetail"
In the "DemoDetail" configuration, add a one-to-many with "RelatedDemo"
It will throw a similar error but instead of looking for the full namespace for the RelatedDemoDataSeedContributor. It will start to look for the file in the Master entity folder instead of the folder "RelatedDemo"
Could not find file 'C:\Users\User\Documents\GitHub\demo802\modules\DemoModule\test\DemoModule.Domain.Tests\MasterDemo\RelatedDemoDataSeedContributor.cs'.
UPDATES
It also happens when you have TWO one-to-many relationships of the same entity. It tries to look the DataSeedContributor of the related entities from the destination entity folder
in the CLI, abp update it's not updating the project to the latest version 8.0.2. Either it's applying any changes to the code related to the new version.
I can't see any Lepton or LeptonX Bug & Issues but here I go
In
LeptonX\src\Volo.Abp.AspNetCore.Mvc.UI.Theme.LeptonX\Themes\LeptonX\Components\SideMenu\MobileNavbar\Default.cshtml
There is no localization for "Settings" button (Line 49) <li class="lpx-mobile-nav-tab"> <a class="lpx-mobile-nav-item" data-lpx-mobile-menu-toggle="settings"> <i class="menu-item-icon bi bi-gear-wide-connected" aria-hidden="true"></i> <span class="mobile-item-text">Settings</span> </a> </li>
It also happens here LeptonX\src\Volo.Abp.AspNetCore.Components.Web.LeptonXTheme\Components\ApplicationLayout\TopMenu\Navigation\MobileNavbar.razor
I found an issue while creating Master / Detail.
The generated MasterDto includes a wrong collection of DetailDto. It includes DetailWithNavigationPropertiesDto instead of DetailDto.
Any news about the fix? It's not possible to use ABP Suite with the last version to create a new module
There is an important error in ABP Suite for 8.0.1.
Can't create a module even in a clean installation.
You get the following error while creating a new module
Please, this requires special attention to be fixed soon and this shouldn't happen in future versions since it's a basic functionality of ABP Suite
Thanks.
Hi, can you check if your application is running or not? If it's running please stop it and then re-try to add the module.
Hi, the application was not running, turned off the antivirus and created a new abp application from ABP Suite and still got that error.
There is an important error in ABP Suite for 8.0.1.
Can't create a module even in a clean installation.
You get the following error while creating a new module
Please, this requires special attention to be fixed soon and this shouldn't happen in future versions since it's a basic functionality of ABP Suite
Thanks.
There is still a critical issue in ABP Suite that won't let you generate Entities with one-on-one relationships.
If I create a RelatedEntities in ABP Suite with any property and generate it and then create a MasterEntity with a relationship of 1-1 with RelatedEntities and try to generate it using ABP Suite. I will get the following error.
Related to this. If you create a Master-Detail Entity, the detail entity doesn't generate any test project or it's added to the master entity test project.
There is still a critical issue in ABP Suite that won't let you generate Entities with one-on-one relationships.
If I create a RelatedEntities in ABP Suite with any property and generate it and then create a MasterEntity with a relationship of 1-1 with RelatedEntities and try to generate it using ABP Suite. I will get the following error.
Found another bug in ABP.Suite 8.0.0.rc-3
When you try to generate an Entity with a one-to-many relationship. It tries to locate a test class in the wrong place.
It tries to locate in Demo.TestBase folder instead of Demo.Domain.Tests folder
Could not find a part of the path 'C:\Users\User\Documents\GitHub\demo\demo-web-mvc\modules\Demo\test\Demo.TestBase\Demo\DemoDataSeedContributor.cs'.
System.IO.DirectoryNotFoundException: Could not find a part of the path 'C:\Users\User\Documents\GitHub\demo\demo-web-mvc\modules\Demo\test\Demo.TestBase\Demo\DemoDataSeedContributor.cs'.
at Microsoft.Win32.SafeHandles.SafeFileHandle.CreateFile(String fullPath, FileMode mode, FileAccess access, FileShare share, FileOptions options)
at Microsoft.Win32.SafeHandles.SafeFileHandle.Open(String fullPath, FileMode mode, FileAccess access, FileShare share, FileOptions options, Int64 preallocationSize, Nullable`1 unixCreateMode)
at System.IO.Strategies.OSFileStreamStrategy..ctor(String path, FileMode mode, FileAccess access, FileShare share, FileOptions options, Int64 preallocationSize, Nullable`1 unixCreateMode)
at System.IO.Strategies.FileStreamHelpers.ChooseStrategyCore(String path, FileMode mode, FileAccess access, FileShare share, FileOptions options, Int64 preallocationSize, Nullable`1 unixCreateMode)
at System.IO.StreamReader.ValidateArgsAndOpenPath(String path, Encoding encoding, Int32 bufferSize)
at System.IO.File.OpenText(String path)
at Volo.Abp.IO.FileHelper.ReadAllTextAsync(String path) in D:\ci\Jenkins\workspace\abp-volo-release\abp\framework\src\Volo.Abp.Core\Volo\Abp\IO\FileHelper.cs:line 59
at Volo.Abp.Suite.Areas.AbpSuite.CrudPageGenerator.Commands.UnitTestCommandCommand.kKU8AbY4LZ(String )
at Volo.Abp.Suite.Areas.AbpSuite.CrudPageGenerator.Commands.UnitTestCommandCommand.ThA8R0QUdt(TestDataObject , Int32 )
at Volo.Abp.Suite.Areas.AbpSuite.CrudPageGenerator.Commands.UnitTestCommandCommand.OYG8Wvo7Rq()
at Volo.Abp.Suite.Areas.AbpSuite.CrudPageGenerator.Commands.UnitTestCommandCommand.ExecuteAsync(CrudPageCommandOptions options)
at Volo.Abp.Suite.Areas.AbpSuite.CrudPageGenerator.CommandManager.ExecuteAllAsync(CrudPageCommandOptions options)
at Volo.Abp.Suite.Areas.AbpSuite.CrudPageGenerator.Commands.CrudPageGenerator.GenerateAsync(EntityModel entity, Solution solution, EntityModel masterEntity)
at Volo.Abp.Suite.Controllers.CrudPageGeneratorController.SaveAndGenerateEntityAsync(Guid solutionId, EntityModel entity)
at lambda_method1948(Closure, Object)
at Microsoft.AspNetCore.Mvc.Infrastructure.ActionMethodExecutor.TaskOfActionResultExecutor.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.<InvokeNextActionFilterAsync>g__Awaited|10_0(ControllerActionInvoker invoker, Task lastTask, State next, Scope scope, Object state, Boolean isCompleted)
at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Rethrow(ActionExecutedContextSealed context)
at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted)
at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.<InvokeInnerFilterAsync>g__Awaited|13_0(ControllerActionInvoker invoker, Task lastTask, State next, Scope scope, Object state, Boolean isCompleted)
at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeNextExceptionFilterAsync>g__Awaited|26_0(ResourceInvoker invoker, Task lastTask, State next, Scope scope, Object state, Boolean isCompleted)