Hi @ismcagdas
Thank you very much that's great news for me :)
So can you just explain now how to deal/comply with naming conventions in regards to the new project names (hence namespaces)?
Thanks, Loizos
Hi @ismcagdas,
Thank you for your answers. I am still little confused though because in order create a new app with all layers, it means that I have to purchase a new license right? In such a case I don't believe I will get an approval from MDs for the moment so I am looking for alternatives.
So for example my initial idea is to create a new front-end client portal (outside asp.net zero) but connect it with the existing back-end (asp.net zero). Is that possible or not? Can I utilize the existing distrubution layer in order to call application APIs from my own front-end?
The second thing is that I would like to isolate somehow all available services to the client portal. How can I achieve that and what are the options I have? Can I use permissions for example instead of separate them physically? Please explain me a little bit on this matter.
Thank you in advance.
I have the following case and I would like your advises on how to proceed.
I would like to deploy a new small web application (client portal) in order to access specific part/services of the main application, but with limited permissions and functionality of course. The main application (angular + asp.net core) is a multitenant application and each tenant/customer have it's own clients, hence the need of the client portal. To do so I am planning to create a new web application/front-end but I would like to benefit and use the existing asp.net zero functionality as my base/core back-end.
Can I create a new class project inside existing core solution as a new module in order to implement all portal related application services? i.e mycompany.myapplication.application.portal Do I need to create a new module in all layers or a new module in application layer only?
How can I expose these services separated and isolated and not mixing them with the application (full) services and functionality? If I just add the depentency in webcoremodule it's going to add/expose the new services along with the application services right? Do I have to create a new web host project instead? Please advise.
Also how can I isolate database related functionality on EF/migration layer as well as on DB layer? For the DB layer can I implement a new repository that will point to a new connection string? This way I am thinking to have a second schema on the database (SQL) with limited permissions. Please advise your recommendation on this.
Thank you.
Thank you @ismcagdas
Hi,
Thanks for your answer.
I think the power tools doesn't work though. Perchaps angular & aspnet-core folders have to coexist on the same level?
Loizos
Hi @ismcagdas
Thanks for your answer, that's for sure, no intention to change the internal structure.
However, to do so I have to move the 3 projects for the mobile app from the existing path and place them in a root folder before add them in a new repository. Also I have to fix their dependencies (references) to the other (aspnet core) projects. Are these changes acceptable?
Also a quick clarification regarding the ui-tests folder in the root structure. This one refers to the angular app isn't it? Can this be packed under the angular app repository only?
Thanks, Loizos
What is your product version: 11.0.0 What is your product type (Angular or MVC): Angular What is product framework type (.net framework or .net core) .NET 6.0
Hi,
I would like to ask if I will be facing any kind of issues in future (..during updates/upgrates of ASP.NET Zero ?) if I change the structure of the root folders. For example I would like to have the angular folder in a different github repository (e.g. myapplication-angular/angular) while the aspnet-core folder in another respository (e.g. myapplication-core/aspnet-core).
Also, the same question goes for the mobile app source code, is it possible to take it out in its own root folder without having any troubles in future updates?
Thank you in advance,
Loizos
Hi,
Yes, that solved the problem! Thank you very much @ismcagdas
Loizos
Hi,
Yes, that solved the problem! Thank you very much @ismcagdas
Loizos
Hi @AuroraBMS
I am encountering the same issue and after installing "dotnet-runtime-2.2.0-win-x64.exe" the code is generated however I get an error while running add-migrator....
You mentioned EF to be installed/upgraded ... how to do that? I just tried to unistall/intall from nuget packages but problem still persists.
