Closed panesofglass closed 9 years ago
Rx nuget is only applicable to Windows builds, Rx is packaged with Mono 3.x
Personally, I'd really dislike if the NuGet package was shipped as a code file. The code in my Visual Studio projects is my own, and I find it much harder to navigate if NuGet packages start adding code files to my projects. If that happens, then which code is mine, and what shouldn't I touch? What would the update process be?
I think the main reason was it's really just a conversion wrapper around the numerous overloads. I can understand the concern though.
On 2 Oct 2013, at 07:48, Mark Seemann notifications@github.com wrote:
Personally, I'd really dislike if the NuGet package was shipped as a code file. The code in my Visual Studio projects is my own, and I find it much harder to navigate if NuGet packages start adding code files to my projects. If that happens, then which code is mine, and what shouldn't I touch? What would the update process be?
— Reply to this email directly or view it on GitHub.
Any further thoughts on this? @7sharp9, would this be preferable to fixing the packaging story? Also, how would we fix the fsproj files to accommodate the differences with Mono's Rx support?
If exists should do it shouldn't it?
On 29 May 2014, at 20:20, Ryan Riley notifications@github.com wrote:
Any further thoughts on this? @7sharp9, would this be preferable to fixing the packaging story? Also, how would we fix the fsproj files to accommodate the differences with Mono's Rx support?
— Reply to this email directly or view it on GitHub.
No longer necessary with paket.
The wrapper is currently only a single file and could just as easily be added via nuget as content rather than as an additional assembly. This should also depend upon the Rx nuget package.