NuGet all the things!

[jlaanstra]

This PR fixes #582 by getting all the packages from NuGet. Locally I have build the RxUI packages except for the mac files to verify that everything works.

What else?

This PR does a number of other things.

Updates to the .nuspec files

The .nuspec files are updated to include the new PCL profiles and the new WPA81 folder.

• NuGet.exe has been updated to 2.8.2.
• RxUI.Blend now contains the Blend projects. Putting this in platforms does not make sense since it is only for some Xaml platforms.
• RxUI.Platforms now references RxUI.Core and RxUI.Blend.
• Remove the files for RxUI.Mobile.
• Make sure the .pdb files are tracked.
• Fix a bug in MakeRelease where a single empty file would not result in an error during the creation of the packages.
• Kill the WinRT45 identifier and replace it with Win8 for consistency.
• Fix the Winforms and AndroidSupport packages.

Kill all nuget.targets.

Automatic package restore is way better, so let's use that.

Add missing Testing project

The RxUI.Testing project for Windows 8 was missing and has been added.

Bug fixes to RxUI.Events.

• The EventBuilder project now also uses packages from NuGet.
• Events for iOS failed to build with Xamarin 3.0 and possibly earlier.
• Events for Android failed to build and now references the assemblies in the v1.0 folder.
• Events for WIndows 8 failed to build because it referenced thee wrong .winmd files.
• Really reference Android 4.0.3 files.

Small fixes.

• Make sure all projects output a pdb and xml file in release mode.
• Fix some configuration mistakes and output folders.
• Missing link to CommonAssemblyInfo.
• Fix a reference to a .Net 4 assembly leading to app.config everywhere.

TODO:

• Only reference RxUI.Blend for the Xaml platforms that support it.
• Decide if we would update RxUI.Mobile and reference RxUI.Core similar to RxUI-Xaml. It should.
• Decide if RxUI.Core should have a dependency on Newtonsoft.Json. It shouldn't.
• In ext is still XamMac.dll and Xamarin.Android.Support.v13.dll. The support lib is also in the reference assemblies folder. Should we use that one? What about XamMac.dll?

[jlaanstra]

@paulcbetts I think this helps you with #598 :)

[anaisbetts]

[anaisbetts]

[anaisbetts]

Decide if we would update RxUI.Mobile and reference RxUI.Core similar to RxUI-Xaml.

Yep, RxUI.Mobile just becomes a metapackage

Decide if RxUI.Core should have a dependency on Newtonsoft.Json.

Yep. I'm sure people will get so maaaaaaaaadddddd about it, doin' it anyways

In ext is still XamMac.dll and Xamarin.Android.Support.v13.dll. The support lib is also in the reference assemblies folder. Should we use that one? What about XamMac.dll?

I'll fix this stuff up, probably want to just delete XamMac.dll

[jlaanstra]

Yep, RxUI.Mobile just becomes a metapackage

So in the case of RxUI-Platforms I agree, but in this case the functionality of the original RxUI-Mobile just does not exist anymore. Keeping it as a meta-package implies that it still exists but elsewhere.

[anaisbetts]

So in the case of RxUI-Platforms I agree, but in this case the functionality of the original RxUI-Mobile just does not exist anymore. Keeping it as a meta-package implies that it still exists but elsewhere.

So, if you were using RxUI-Mobile and only had a reference to that, you now should have a reference to RxUI proper on upgrade (Unless you were the one guy who used the location API stuff)

[jlaanstra]

So, if you were using RxUI-Mobile and only had a reference to that, you now should have a reference to RxUI proper on upgrade (Unless you were the one guy who used the location API stuff)

True, but in that case you should rethink large parts of your applications, that simply are not there anymore. I'm not sure what the best option is, but adding the meta package is easy so I will add it.

[jlaanstra]

I've changed the description of the meta packages to indicate that they are no longer needed. Thoughts?

[shiftkey]

Yep. I'm sure people will get so maaaaaaaaadddddd about it, doin' it anyways

Always Be NuGetting

[jlaanstra]

Always Be NuGetting

Definitely agree, but it would be great if there is choice between serializers. Especially since it is suggested to write your own ISuspensionDriver which is the only code that depends on Json.Net as far as I know.

[shiftkey]

@jlaanstra where are we suggesting that?

If users care about the serialization library used, that's one thing.
If users want to control behaviour, that's a different thing (and I think more important).

[jlaanstra]

@shiftkey https://github.com/reactiveui/ReactiveUI/blob/rxui6-master/ReactiveUI/RegisterableInterfaces.cs#L394

[shiftkey]

@jlaanstra I'd suggest either 🔥 that comment down if that's not the case, or elaborate on why you should do it, and make it a proper extensibility point...

[anaisbetts]

Ugh, ok nevermind, let's burn down JSON.NET

[anaisbetts]

😍😍😍😍😍😍😍😍😍😍😍😍😍😍😍😍😍😍😍😍😍😍😍😍