I am not sure if this is the correct forum for this questions. If not, please advise which forum I should ask the question.
We have started creating our own Win 10 UWP libraries that we want to share among our internal development team. We have create each library projects as a separate NuGet package and have them stored on a network share. This has been working for our needs.
However, now we are wanting to start creating boiler plate/template applications to minimize the initial project setup and coding. I saw there was a way to use NuGet and .pp extension. However, I have not been able to successfully get any of the content files to be added to the target projects. I have read that VSIX is the way to go for creating project templates. However, my concern is that as we start to adopt new versions of Visual Studio, we would have to go back and rework, and maintain different versions of our VSIX to target the different versions of Visual Studio. As some older projects will still developed under Visual Studio 2015, while the newer would be using newer versions of Visual Studio.
Can somebody please let me know if using NuGet and VSIX is an appropriate fit and model for sharing libraries and templates? Is there a better way to share boilerplate code that refactors namespaces and other variables at creation of new projects that use the shared libraries and isn't dependent on a specific version of Visual Studio.
Any guidance and direction would be greatly appreciated! Thank you in advance.
Alan
Edit:
Development environment
- Visual Studio 2015 Update 3
- Visual Studio Team Foundation Services for source control
- Latest version of nuget.exe (3.4.4.1321)
- Windows 10 Anniversary Update