I need to develop a multi project application using .net core 2.2
Apart from business logic, I need to implement client UI in a project and Admin UI in another.
How is it possible to do a think like this? I tried to find some example on this matter with no success.
Any suggestion?
Related
I have a VS Project/Solution (.NET 6.0) that contains a ton of core functionality. WinForms, Classes, etc.
My intention is to copy/duplicate this project and customize it for each individual application (if you are curious, this is a project interacting with collaborative robots. While the core of the project will be similar across multiple robots, each individual robot will need its own tweaking (GUI, functionality, etc). I would like to keep these as individual projects and not just add new robots to the base project. I want to keep it to one project per robot. I have my reasons, from licensing to support.
My question is: what is the best practice way to copy/duplicate a project and rename it? These are the goals:
Keep the Base/Ref project intact so it can be used as a basis for new projects.
Be able to push each 'new' project to a new location/repo in GitHub.
Any thoughts are greatly appreciated!
I am a bit confused about the differences of these two strategy.
Which is the guideline if I would like to share a java library among different java Apps ?
Regards,
S.
Not sure if a general guideline exists, but happy to share how we use the two in our company.
We use multi-project builds to organize the different parts of our product. For example, we have subprojects for the business logic, the rest api, the webapp, the mobile app, and the user manual.
In contrast, when working with software our product depends on, but isn't part of our product, using a composite build can be useful. For example, our product's webapp is based on a framework. For official releases of our product, we rely on the official releases of the framework only. However, in development we sometimes want to test a bugfix in the framework that has been applied to the framework's code base but that hasn't been relased yet. A composite build allows us to build the framework from source and run our product against that build.
What is the preferred solution for Exrin project layout when adding a database?
The sample Tesla app had a separate project for the Services and another separate app for the Repository. With the removal of both of those projects in the latest template, it makes the most sense for it to go within the Logic project, but I'm curious if the author had a different preferred implementation.
The Tesla Sample project is designed for a very large app, and Service and Repository don't need to be separated out into a separate project, they can all be referenced directly in the logic app, as per this diagram.
This is the project setup, I now recommend for most projects.
I have a solution with multiple projects and a website. On each project I have set up a pre build event to get the highest subversion revision number of the project (using SubWCRev) and then replace part of the AssemblyVersion with that revision number.
How do I achieve this on a website? As far as I can tell there is no pre build event and if I try to:
Add another project
Make the website dependant on the project
Use the pre build event for the project
The subversion revision number used to replace information in the website will be for the project not the website.
Any ideas?
One suggestion might be to use a Web Application project - rather than a Web Site project. Although this might not be entirely feasible in your case, depending on the amount of work required to essentially migrate the existing code-base.
See this question and its answers for more information: ASP.NET Web Site or ASP.NET Web Application?
How do you commonly lay out your solutions in Visual Studio? Recently, I've kept the BLL, DAL and presentation in different classes and planned to add a test solution as I learn TDD. However, after recently watching a video from Rob Conery and viewing a project from an external contractor, I noticed a theme of multiple projects in the solution.
The projects included in the solution were:
Infrastructure
Model
Web
Tests
SQL Repository
Is this something new or a design technique suggested for MVC? Can anybody tell me more about this design?
First, you need to understand Rob's coding habits. He uses an MVC-esque approach to development (if not pure MVC) and uses his ORM SubSonic.
The use of MVC is the reason for the "Model" class, since SubSonic 2.1 contains Migrations, he is using the SQL Repository for those migrations, so that he can version his DB.
Tests and Web are self-explanatory, which only leaves the Infrastructure, and your guess is as good as mine, though it could be the "Controller" of the MVC pattern.
It all depends on the pattern that you're using, your own preferences for separation of concerns, and your comfort level developing multiple projects at once.