How (and when) do I use TFS with private DLLs that can also be served by NuGet/NuPack?

Question

We have a couple of private "Enterprise Services" DLLS that are used in all our Websites for authentication, logging, etc. Since they are private, we also control the versioning and source of these DLLs. Our historic (error prone) steps after creating File | New Project include

1. Add the "Enterprise Services" project
2. Add a reference to above
3. Edit web.config sections such as Authentication, HttpHandlers, etc...

NuGet will automate the above process

I just came across NuGet (bundled in MVC3) which allows me to download and install VS2010 packages from a privately hosted server, and automate the config settings that previously would have made manually.

Question:

• Does it make sense to publish my dll into a private NuGet server?
• Will I lose the ability to debug and step into this dll if I need to?
• What other things should I consider if the rest of my project is based in TFS?

Answer 1

Yes, it makes sense for you to have a private NuGet feed

I'm not sure about stepping into the dll, but if you provide PDBs in your NuGet package as well as the library sources on a share (and then configure VS to know where those sources are) then you should be able to step into the code just like you can today for the .NET framework itself.

NuGet was designed to work well with projects that are mapped to source control so hopefully there's nothing else you need.