Can an app have multiple APIs?
Yes of course and you should do so as much as possible! APIs are great for providing modularity and separation of concerns (which is an important concept in web architecture). Even within your own organization you should design your systems as services that sit behind APIs.
Should I create a new repo for each project?
A new repo should only be created for a new project. For instance, if you are working on a 2 different e-commerce sites, don’t put them in the same repo unless they have to work together.
How do I merge two projects in Visual Studio?
3 Answers
- In Solution Explorer, select files that you want to move from your source project to your target project.
- Choose ReSharper > Refactor > Move. Here’s how the refactoring dialog looks like.
- Choose a destination project (or a folder in it).
- Make sure to keep “Fix namespaces” selected and apply the refactoring.
Should I use Git submodules?
Its more accurate to say that git submodules are useful when you want to share code that you also need change along with the consumer of that code. There’s additional complexity that comes along with using git submodules, and this complexity isn’t worth it if there are simpler ways of sharing code.
How to run multiple ASP.NET Web API pipelines?
While Web API will still treat all AppDomain types as potential “controller” candidates, in TypedHttpControllerTypeResolver we use the same default constraint to discover controllers (must be class, must be public, must not be abstract) that Web API uses, but additionally we throw in the requirement to subclass our predefined base controller.
What are the benefits of multiple projects and one solution?
Another point is the build time that could be shorter as the whole solution won’t be recompiled each time. Might be a good argument for your manager (but this assumption might be wrong depending on the size of your solution). If you only ever have one application, than one project is fine.
Is it better to split a MVC project into multiple projects?
Maintainability is about clean code, small methods, small classes each having a single responsibility and limited coupling between these classes. Splitting a project with with fat classes and fat methods into BLL/DAL projects doesn’t improve the maintainability of your software.
Is it better to have multiple projects or folders?
If your only reason to have multiple projects is improved organization, then you are doing it wrong. It would be just as effective to use folders. I’m very surprised by the accepted answer.
https://www.youtube.com/watch?v=V3hNzKuLqtM