Hello Dmitry. Recently working with ExtCore 5 and having a trouble switching to Extensions.
The Startup.cs of my inner project is not recognized by the Project. So Dependency Injection not working
@DmitrySikorsky Aha, the ** !
Thank you, another lifesaver :smiley:
I am facing an issue integrating Angular into the extension. It would be great help if you will provide sample to me
Look, ExtCore is a server-side modular framework. So you can create an app that will combine entities, repositories, controllers, views... from the extensions. But also you can include the client-side content into the packages. Like html, css and js files. In case of Angular I don't think it will be very easy to do, because you will have to deal with paths, because by default the assembly name is included into the path when you need to access a static resource from the extension (but you can change this behaviour).
Hi, I have got an ASP.NET Core MVC application which contains main web app and 2 extensions - both of them are quite complex, frontends are included. I would like to apply localization with resources, however I am not able to register localization services for mentioned extensions. When I place resources in main web app, everything goes properly, but there is a requirement to separate resources via extensions. What is a correct way to achieve it? Thank you for advice :-) P.S. Localization setting is done in startup file of main app, in accordance with MS examples...
Hi! You can look at https://github.com/Platformus/Platformus/blob/master/src/Platformus.ECommerce.Backend/Areas/Backend/Views/Products/CreateOrEdit.cshtml#L15 for the sample
Hello, i upgraded my project from .NET core 3.1 to .NET 6 and i had an issue with EXT Core, it was including the plugins in debug but whenever i publish the project the extensions are no longer loaded.
If anyone had this issue just add the below in your csproject file:
This is due to a breaking change in the .NET core 6: https://docs.microsoft.com/en-us/dotnet/core/compatibility/aspnet-core/6.0/preservecompilationcontext-not-set-by-default#:~:text=PreserveCompilationContext%20is%20an%20MSBuild%20property%20that%20causes.NET%20Core,is%20primarily%20used%20to%20support%20run-time%20compilation%20scenarios.
Hi Dmitry, thank you a lot for your reply and example links. I am not sure, however it seems that you use an oposite approach than I would like to have. Your localization resources are centralized, but my aim is to place mentioned resources into every extensions (so, i get this structure: controllers, viewmodels, models, views, resources...). As I wrote in my request, there is a problem how to set up path to these resources from startup file (here you can find also a configuration of ExtCore :-)) contained in main web project.
I see. I'm not sure I can look at it now, I have to release the Platformus 3 asap. I only can suggest to debug the localization factory I've sent you, it is very simpe so you can just understand how it works and configure it as you need. I don't remember how the default one works, but I remember that I had to copy one from the .NET source code, replace the existing default implementation with it, and debug.