It also happened on existing language, default language as English, even you switch to others, it always display English language resources on sidebar.
asp.net core with netframework 461
In version 4.0.0, in the admin area, if select the language dropdown list, then it always stay on "English" option, if you selected other language, the side bar always display English language resources, but the page could display according selected language resources.
<cite>ismcagdas: </cite> Yes,
Exactly, if you want to execute a domain service in a UoW, it needs to be decorated explicitly with a UnitOfWork attribute and it must be marked as virtual in order to be intercepted.
It seems in the document [https://aspnetboilerplate.com/Pages/Documents/Domain-Services]), it doesn't show a walkthrough that methods in the application services needs to be marked as virtual.
Yes，using same name application service in a module or assembly is not a good pattern, but sometimes it is required, such as a "Category" entity, it is a so common definition in different namespace, accordingly, "CategoryAppService" also will existing in different namespaces.
Especially, in my project requirements, lots of similar entities are needed(because they need mapping to individual table in database), if each application service add the prefix will cause the application service and according DTO with long name, it is not convenient when coding.
So I want to customize the API namespace like ABP.WebApi done.
Another story, Swagger also not support same name application service(even they are polymorphism) and not support DTO with same name.
ABP could Building Dynamic Web API Controllers and the namespace of the API could be customized in module initialize, but it seems this cannot be implemented in asp.net core integration, in asp.net core only below configuration available
Configuration.Modules.AbpAspNetCore().CreateControllersForAppServices(typeof(MyApplicationModule).Assembly, moduleName: 'app', useConventionalHttpVerbs: true)
This really not convenient, as I have lots of same name application service in different namespace in the application module.
Could you also make the Dynamic Web API controllers feature available for asp.net core?
@ismcagdas , yes, the MVC project as the startup project.
@joe704la , I found the reason about "The EntityFramework package is not installed on project", it is because EntityFramework and EntityFrameworkCore both are installed on the solution, but I checked didn't find EntityFramework installed. Current, I am add a prefix before the command in PM console, such as "EntityFrameworkCore\Update-Database", it works with the command in EntityFrameworkCore.
I also customized some entity mapping configuration to mapping entity to database.
<cite>joe704la: </cite> Another thing I just tried and failed was doing a brand new fresh download and trying to Update-Database in the Package manager console and I am getting "Could not load file or assembly 'Microsoft.EntityFrameworkCore.Design' or one of its dependencies. The system cannot find the file specified."
I shut down visual studio, I cleaned the solution rebuilt it, and triple checked that I have the EntityFrameworkCore as the selected default project in Package Manager Console.
@joe704la, How to resolve this issue finally?
Copy to a clean solution, when run the update-database encountered "The EntityFramework package is not installed on project", did you see this error too?
Is that existing migration record which generated by EF.migrator still could use in EF core pack manager console?
As EF Core replaced EF 6.x, migration records also restart, does Zero 4.0 still support upgrade from previous versions? such as Zero 3.4