3 ms·
> There will be some shared code you don’t want to run out of process. For that, create Nugget packages and you won’t have to change your client code at all. a
by merb 8y ago
> There will be some shared code you don’t want to run out of process. For that, create Nugget packages and you won’t have to change your client code at all.
actually you can keep your solution and just have many projects in one solution (monorepo)
- scarface74 8y agohaving one large solution causes a ton of issues. Even if you have multiple solutions in one repo, that means everytime you deploy, you have to deploy the whole thing. Rolling back becomes more difficult and one team can break the build and it effects other teams.
- merb 8y ago> Even if you have multiple solutions in one repo, that means everytime you deploy, you have to deploy the whole thing. Why? Just because the code sit's in one repo, doesn't mean that everything needs to be deployed the same time.
- scarface74 8y agoHow do you do independently automatic partial builds and deployments to an integration environment with a monorepo? If I just changed one solution, pushed it, and the build process is automated, how does it know not rebuild and deploy all of the solutions?