Right, this kind of assembly support is something that we should adopt at
some point, but it will require some major changes to do this.
Alex is right, for now this should be considered equivalent to the full
.net stack, not the split version of it.
Btw, it seems from the live webcasts that (a) t
Well the issue with the NuGet-based BCL libraries like System.Console is that
the actual implementation still depends on Windows internals, e.g. a very quick
peak with a decompiler on the new System.Console NuGet library reveals dozens
of DllImport("api-ms-win-core-file-l1-1-0.dll") and correspo
As I follow the github discussions in some of the asp.net vnext
subprojects, I see them testing on Mono (in MacOS X) as part of the
development process, but yet some things are lagging a bit... :)
On Wed Nov 05 2014 at 9:43:28 AM Martin Thwaites
wrote:
> So, after thinking about this further. T
So, after thinking about this further. The question I have is not really
about CoreCLR.
What I want to know is, the libraries that Microsoft are making available
via their nuget (myget at the moment), are these going to be tested again
.net, mono and CoreCLR? I.e will the libraries be cross platf
