Knowing this decides for me that for our purposes we should probably use a shared folder for packages rather than implement a local NuGet repository service.
Actually, it was the content of the link you reference that prompted the question. As far as trying it first, I was looking for confirmation from users who had experience that otherwise takes an undetermined amount of time for me to acquire by trial and error. It never hurts to ask.
While we use NuGet packages from the public repository, it is only recently that I considered using it for in-house publication.
Thanks
Actually, it was the content of the link you reference that prompted the question. As far as trying it first, I was looking for confirmation from users who had experience that otherwise takes an undetermined amount of time for me to acquire by trial and error. It never hurts to ask.
While we use NuGet packages from the public repository, it is only recently that I considered using it for in-house publication.
Thanks