This article makes the suggestion to break up your .net project into nuget packages. This is horrible and DOES NOT WORK - DO NOT DO THIS. As someone who, as of

This article makes the suggestion to break up your .net project into nuget packages. This is horrible and DOES NOT WORK - DO NOT DO THIS. As someone who, as of this very minute, is working on a project that someone has broken up into different nuget packages - this is a fine idea but it can go very bad and kill productivity completely. Unless each individual part has independent test harnesses, as soon as you need to make a change, you need to go through the build server to test any change. Combine this with sub-par tooling and you can use your imagination as to how badly that messes up your development flow. As well as this, it also messes up your potential branching strategies - you cant make a branch to do speculative changes unless you setup a build definition to create the nuget packages. And even if you do this, you need to maintain two streams of versions for the same package. This has a whole range of problems when it comes to updating packages - a package update ends up having to actually be a downgrade in terms of version numbers. This is not supported by your tooling in visual studio. Before taking this approach, please give it some serious second thoughts.