The current NuGet packages are somewhat non-standard and onerous to use. I suggest a symbol package be created for RxUI. This will ensure anyone consuming RxUI via NuGet can very easily step into RxUI code.
@kentcb Ah, I didn't realize that symbol packages could be created via the .nuspec, I thought you had to create them from a csproj file, which doesn't work with ReactiveUI
@kentcb Do you want to contribute this? Here's how I would do it:
robocopy .\NuGet\ReactiveUI-Core\src\ReactiveUI .\ReactiveUI *.cs /S
@xpaulbettsx Sure thing - I'll get to it after Easter.
I would suggest adding /min:1 to the robocopy command to exclude the 0 byte temporary .cs files visual studio creates in the obj directory.
@jlaanstra: Actually, the obj directory will be excluded in its entirety.
You have to be careful with excluding the obj directory as there can be .cs files in there that must be part of the symbols package. This is for example happening with .xaml files. For now ReactiveUI doesn't include any .xaml files, but it is still something to watch out for.
Since you need to adapt the MakeRelease.ps1 file this could be combined with adapting MakeRelease.ps1 to build a portable library and put it in the supported folders, which is tracked as a task in #217.
Let me know if you need help with this!