C# Development – Best Way to Handle References in a .NET Application

c

Recently at work we ran into a problem where we tagged/branched a project and had some compiling issues because of dll/project references that was pointing to the old folder structure.

We created an 'external bin' folder for each of the projects and copied the referenced dll's to these folders. Is this the best way or is there a specific industry standard to handle this?

Best Answer

I would say that nuget is the best way to handle dependencies.

nuget can manage versions AND automatically download the dependencies from your local nuget server.

It's quite easy to create/configure a local server. Simply create a new empty ASP.NET project and install the nuget-server nuget package (using nuget ;).

That also means that you wont have to check in all dependencies and/or manage their versions using TFS.

Related Topic