HI @ismcagdas
Please confirm if I understood your recent reply correctly and your advice is to create clean @Angular frontend project?
If that’s the case, can we then use some of the components from existing asp.net zero template (e.g. chat, registration/authentication related components) in new project or we should expect be some license related complications (is any licensing logic embedded into Frontend template)?
We are building application based on asp.net zero + angular 8. Unfortunately our UI design is too custom to fit with any of the existing Medtronic themes (even with slight modifications)
Is there any clean & non too time consuming way to replace Medtronic with fully custom styling approach based on Material Design?
In our application we don't need any of the existing apsnet zero admin functionality or dashboard, only some components to handle common API related concerns from like Tenants, User authentication, features etc...
Otherwise, is is possible to create new separate Angular project and adopt there functionalities from your template as needed without being blocked by some licesing limitations (we have a dedicated license for it)?
Additional argument for the second option is live reload setup based on gulp which compared to recently recommended webpack based approach is quite inefficient and slow.
Thanks
Great, you will have it in 15 min.
@ismcagdas
Which email do we send it to?
We have two Asp.Net Zero applications. After some analysis we found out that the first application which is already under development will share a lot of classes and business logic with the second much bigger application. In order to avoid copying code between applications we would like to make some parts of those two applications a common codebase. The parts are: Domain and DataAccess (Or in Asp.Net Zero terms Core and EntityFrameworkCore projects). We thought that we will split those projects as a git submodule and then reference it in both of the projects. After the split however the first app stopped working and we can see 'Abp.AspNetZeroCore.Licensing.AspNetZeroLicenseException' in Abp.AspNetZeroCore.dll. It happens when we try to run the Web.Host project or when we try to debug the unit tests (if we just run the unit tests they work fine which is unusual). Can you please advise how we should handle this split process or what should we do in order to get rid of this exception. Both products are on separate licenses.