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

We have several private "corporate services" DLLS that are used on all of our websites for authentication, registration, etc. Since they are private, we also control the version and source of these DLLs. Our historical (erroneous) steps after creation File | New Projectinclude

  • Add the project "Enterprise Services"
  • Add link to above
  • Edit web.config sections like Authentication, HttpHandlers, etc.

NuGet automates the above process

I just stumbled upon NuGet (bundled with MVC3), which allows me to download and install VS2010 packages from a privately hosted server and automate configuration settings that were previously made manually.

Question:

  • Does it make sense to publish my dll on a private NuGet server?
  • Will I lose the ability to debug and enter this DLL if I need to?
  • What other things should be considered if the rest of my project is based on TFS?
+3
source share
3 answers

I agree with marcind: having personal feed makes sense.

2 , : VS , TFS: NuGet .

, NuGet, , ( , gui) , , : .

+1

, NuGet

, DLL, PDB NuGet, ( VS, , ), , , .NET.

NuGet , , , , , .

+1

@Ghidello NuGet , ( "" )

0

Source: https://habr.com/ru/post/1772358/


All Articles