search

LightBuzz / Vitruvius

A set of easy-to-use Kinect utilities that will speed-up the development of your projects.
http://vitruviuskinect.com
Apache License 2.0
229 stars 82 forks source link

Update Vitruvius NuGet package with latest Kinect v1 version #10

Open birbilis opened 8 years ago

birbilis commented 8 years ago

It seems the https://www.nuget.org/packages/Vitruvius/ package has older version of the Kinect v1 library, that is it doesn't contain the WPF control

I guess the https://www.nuget.org/packages/lightbuzz-vitruvius/ version is for Kinect v2 only

is it possible to update the Kinect v1 NuGet package and also add some note at the above two URLs that says for which Kinect sensors each NuGet package is?

birbilis commented 8 years ago

the Kinect v1 package version on NuGet is very old, from 2013 https://www.nuget.org/packages/Vitruvius/

birbilis commented 8 years ago

btw, would be nice to also have NuGet subfolder under Kinect v1 and Kinect v2 folders with the respective .nuspec files. I also keep .nupkg files in such folders and have a .gitignore rule for *.nupkg so that only the .nuspec files get published

birbilis commented 8 years ago

see my comment at the end of this Pull Request - https://github.com/LightBuzz/Vitruvius/pull/17

After merging it and pulling in locally you can open the Kinect V1 solution and Rebuild all (for RELEASE configuration)

Then install NPE (http://npe.codeplex.com - has a ClickOnce installer) and just open the .nuspec file under Kinect v1\NuGet folder and do File\Publish to update the old NuGet package for Kinect v1 (I've imported the old one from nuget.org using NPE, updated the semantic version to 1.1.0 from 1.0.1, added missing WinForms DLL and placing targeting files at lib\net40\ instead of lib)

NPE does check if there are any missing files referenced by the .nuspec metadata file, so you can't have any broken patch by accident.

birbilis commented 8 years ago

note, I've also updated the .gitignore file to ignore .nupkg files, since the pattern I use is to have a NuGet.nupkg subfolder under my NuGet folder, where I Save (using File/Save of NPE) all .nupkg files ever published for the .nuspec file (NPE can even download the current .nupkg file and save it there). NPE nicely adds the semantic version as a suffix the the .nupkg filename

So my steps after editing a .nuspec file are: 1) open the .nuspec from NuGet folder with NPE 2) do File\Publish (enter password) 3) do File\Save to NuGet\NuGet.nupkg subfolder

I've also added a NuGet subfolder to the Kinect V1 solution for easier editing and checking-in of its .nuspec file

didn't do similarly for the Kinect v2 solution, since its .nuspec has lots of files and it's better if you use your original version of it instead of me importing and adapting its filepaths