Well, *they* could switch. My own platform specific libraries do detection. Anything else just ends up with lots of vaguely shareable, similar, but unshared code. In practice what it means is a developer is going to forget to package anything but the Windows version. That may be the idea. Making the library *just work*, without the developer having to worry about platforms, is best.

I have two libraries I maintain that support both .NET Framework and .NET Micro Framework (and Arduino -- libraries for embedded devices), and due to how Microsoft ended up putting things in different assemblies, even the same classes, it's a cluttered #ifdef mess. Some are missing this overload or that. I have to have separate solution files. In the future I'll probably just ditch Micro Framework support. It's terrible, a hassle to maintain, and even more of a hassle to support, debug and test.

It's probably better to pull Microsoft out of the mud as best as possible instead of sinking with them.

James


On 11/29/2016 10:56 PM, Miguel de Icaza wrote:
Hello Jerod,


    Question as a followup:

    "This means that some of the work that we will have to do will
    involve either adjusting the CoreFX code to work in the way that
    Mono works, or give up on our tradition of having the same
    assemblies work across all platforms"

    Is there a preference/leaning one way or another on that point
    yet, or is it still being investigated?


We will have to explore this when we get there.

My personal preference is to use the Mono model, but the maintainers of CoreFX likely have their own personal preference to keep their model and they own that code, so we might have to either get creative with the solution that glues CoreFX code in Mono, or adjust Mono. Neither is easy :-)

Miguel.


_______________________________________________
Mono-devel-list mailing list
[email protected]
http://lists.dot.net/mailman/listinfo/mono-devel-list

_______________________________________________
Mono-devel-list mailing list
[email protected]
http://lists.dot.net/mailman/listinfo/mono-devel-list

Reply via email to