Hi Edward, As I explained in a previous answer, the run the same DLL everywhere isn't as universal as it should, and not just because of OS differences, but also because there are differences in the way each platform implements the API. Yesterday's blog .NET Standard Library Support for Xamarin <https://blog.xamarin.com/net-standard-library-support-for-xamarin/> and Yesterday's update to Xamarin Studio to support it proves my point.
Xamarin mobile platforms are driving this change (that's were the market is now) and non mobile Mono was left behind. I won't repeat myself, but I don't feel the need to have the same DLL running on Windows, Android or iOS. Neither does Microsoft/Xamarin/NuGet. That's why they introduced all the NuGet targets referred on my previous post. I know how to solve my problem and have different NuGet packages for .NET and Mono. What I'm looking for, is to have only one NuGet package that maps to a different DLL according to the VS project target. ----- --- Tiago Freitas Leal -- View this message in context: http://mono.1490590.n4.nabble.com/A-NuGet-target-for-Mono-is-needed-tp4668302p4668313.html Sent from the Mono - General mailing list archive at Nabble.com. _______________________________________________ Mono-list maillist - [email protected] http://lists.dot.net/mailman/listinfo/mono-list
