simple switching between current repo and official-release-PCL

What would be the best practice to use current repo of CocosSharp in my project? I would like to be able to switch (realtively easily) between the last "official" release (CocosSharp.PCL.Shared package) and the current repo version. Is it best to remove PCL package every time when I want to switch to current repo version? Or is ti possible just to switch just CocosSharp.dll?

When I check /Users/jeff/Developer/SDKs/CocosSharp/ProjectTemplates/XamarinStudio/Packages/ the only file in this directory at the time of the build is: CocosSharp.PCL.Shared.MacOS.1.5.0.0.nupkg
and I notice all the NuGets that got built in NuGet/bin all use the 1.5.0.0 version number.

Is there something I needed to do to bump and fix the 1.5.0.0 and 1.5.0.1 discrepancy? I also notice I ended up with a MacOS version and not a generic version of CocosSharp.PCL.Shared.1.5.0.1.nupkg

Is it at least safe to assume that I now have complete and working local NuGets in NuGet/bin at this stage even if the buildXStemplates target failed if I don't really need the new project templates?

Yes you can use the the PCL's that are generated on the Mac with no problem. They will only contain the Android, iOS and Mac versions though. The only way to get the generic version which contains all platforms is to compile on windows and move the generated windows version that does contain all the generic versions. This is what the build is telling you is that this generic .nupkg does not exist. You can still use the templates that are delivered you will just need to change out the .nupkg to point to the locally built versions.

You can update the versions by modifying the .nuget packages with the new version if you would like.

Change the version in each package definition that you want to update locally.

<version>1.5.0.0</version>

To

<version>1.5.0.1</version>

I usually change this myself locally because it sometimes get's confusing which one you are using. The nuget.org version or locally built.

The mac specific versions are appended with .Mac. The reason for the differences is that each platform has it's own separators and build specs.

Since you are using a Mac let me warn you that sometimes when switching the NuGet packages in and out to test different scenarios you may think that they are getting updated but that may not be the case especially if you have multiple XS applications running. If this seems to be happening make sure you Clean, remove all NuGet packages, remove all bin directories, shut down ALL instances of XS and restart by adding the NuGet packages from the local package directory again. We have been bitten a couple of times with this especially with multiple XS apps open at the same time.

FYI, the whole nant thing is nice, but it doesn't quite work with Indie Xamarin licenses.

error: The Indie Edition of Xamarin.Mac does not support building outside of Xamarin Studio. Please go to https://store.xamarin.com to upgrade to the Business Edition.

After I got this error, I had to manually open the MacOS solution in XS to build it. That's not such a big deal, but then, of course I didn't get the benefit of the remainder of the nant script - namely, creating the nice nuget package. So there's another pain point to deal with for us (albeit few) MacOS CocosSharpers.