How should I handle packages with a VS2013 (TFS) nuget installation?
This one is baking my noodle a little and hopefully there's someone who's approached this and has a "best practice" solution.
I'm collaborating on an Umbraco project that's being developed in VS2012 / TFS. I've decided to use nuget to handle the injection of an umbraco base install. It seems to work really well and takes away a lot of the pain in handling umbraco build versions.
But what about third party packages? How do I go about managing them? A lot of folders that would otherwise be exposed are hidden and are handled by nuget. Should I force un-hide them so I can at least check-in the package?
I'm not really sure how to approach this so some advice for someone who's been there already would be absolutely marvelous!
How should I handle packages with a VS2013 (TFS) nuget installation?
This one is baking my noodle a little and hopefully there's someone who's approached this and has a "best practice" solution.
I'm collaborating on an Umbraco project that's being developed in VS2012 / TFS. I've decided to use nuget to handle the injection of an umbraco base install. It seems to work really well and takes away a lot of the pain in handling umbraco build versions.
But what about third party packages? How do I go about managing them? A lot of folders that would otherwise be exposed are hidden and are handled by nuget. Should I force un-hide them so I can at least check-in the package?
I'm not really sure how to approach this so some advice for someone who's been there already would be absolutely marvelous!
Thanks in advance.
Martin
is working on a reply...