The solution file only changes when you add/remove projects or solution-level objects, so it rarely changes. csproj when you need to (like you do now).Īnd how stable is the solution file with source-controlled concurrent development? You don't get the benefits of having everything in one solution, but you can always re-open the sln when you need to and work in just the.
if it is a problem, it can be mitigated: open the. I've seen more without VS having problems. How fast is Visual Studio with a solution of 20+ projects? Much longer, and incremental builds sometimes have funky behaviour.
Separation studio single update#
you changed library code, so you have to update client code at the same time, with 1 checkin)
Separation studio single windows#
you're stepping through a windows service, when it jumps to shared library code, and it just works because all of the symbols are already loaded and accounted for) What are the pro's/con's to putting all your applications in a single solution rather than having separate solutions for each application? But you don't need to, and in my case, the code base is still stored on an ordinary hard drive. Personally, I didn't have such cases, but I imagine that other companies might have.įinally, investing in an SSD for every developer can make a huge difference. Managing the dependencies through NuGet can solve some of the problems when you don't want to merge a few projects into the common solution. I would also study a bit more NuGet and the ability to host a private NuGet server. I can also work on two weakly-related projects, and still have just one Visual Studio window opened. Having a centralized place for all the code is also a good idea this makes it possible, for example, to search for something within Visual Studio. This reduces enormously the pain of broken dependencies, and this benefit alone is totally worth it. I would still migrate everything into a single solution. Just beware of the cases where many developers add new projects at the same time: merging the. I haven't worked in a real concurrent environment, with, say, dozens of developers frequently committing code, but I would imagine that this wouldn't have too many issues. Version control works as expected as well (I'm using an SVN server, if it matters). If somebody works on something which requires only three projects to be loaded, there is no need to load all the 200 projects (unless, of course, dependencies may be affected). To go even further, systematically unloading projects is a good idea (and really easy when projects are organized in directories within the solution). Startup time (cold start, then loading the solution) is impressively fast maybe not as fast as with 10 projects, but still very acceptable (under 20 seconds on a machine bought more than five years ago). But nobody would expect to compile 200 projects as fast as 10, and by the way, you shouldn't: this is the role of the Continuous integration server. If you recompile every project, with Code contracts, Code analysis enabled by default, etc., expect it to take a while. Today, there are more than 200 projects Visual Studio appeared to be scalable enough to manage them as if there were only 20 of them. I thought that it will start crying with a solution with, say, 50 projects. Performance-wise, I was very surprised by Visual Studio. For me, it's a success.Ĭontinuous integration is now easier too.
Want to modify a method but also track the repercussions this change may have anywhere in the code base? Visual Studio can do that with ease. It works well for the moment, and the dependencies are now easy to follow. Merging all the code into one solution was an alternative. The worst part is that you can't even know what exactly would be affected by the change. The day you substantially change a project which is used nearly everywhere, expect hours and hours of lost work for the entire company for the next days or weeks. Some projects from a solution reused projects from another one, and nobody cared about using a package manager.
Recently, we migrated nearly all the source code in my company into a single solution.
0 kommentar(er)
