The NCrunch.Framework wiki page suggests copying NCrunch.Framework.dll from the GAC into the project's folder to prevent the build from breaking on machines that don't have NCrunch installed. While the solution works, it just doesn't feel right since NuGet was released; why not add the assembly to NuGet? It'll allow existing users to take advantage of NuGet features like automatic package restoration and update detection, and might catch the attention of potential new users browsing through the NuGet repo.

P.S. Thanks for an awesome plug-in ;)

The same problem would arise when more than one person are sharing a solution as well, so I'm not sure how that affects the decision to use NuGet.

Respectfully, I don't see how putting the assemblies on NuGet "will only make this worse".

People "create version inconsistencies" by upgrading NCrunch to the next version, NOT by referencing a new Framework version. The framework version is only going to be updated when the NEW version of NCrunch stops working with the OLD Framework DLL. If you are trying to prevent inconsistencies altogether, the *only way* to do so is to stop releasing new versions.

If it were me, I would trust people to be able to keep NuGet packages in sync much more than I would trust them to manually manage DLLs by extracting them from the GAC.