Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
Add support for .NET Core/CoreCLR #672
This is for #668.
I've added a build-time package for my Dependency generator tool: https://github.com/onovotny/ReferenceGenerator. That puts the right dotnet stuff in the nuspec.
Then I've updated the nuspec to put the right files in the lib dirs.
I've removed the un-needed xproj stuff as there's no need for them to support CoreCLR. If you want to use the new .NET Core libraries, you can also do that with a "modern PCL" -- that is, create a new PCL project that targets aspnet 5, universal 10 and .net 4.6. You can use linked files/shared projects to share the code with the existing PCL.
The only thing you need xproj for is for websites. The other xproj can be moved into a "modern PCL" that only targets aspnet 5 too. I can help with that later if you need.
As-is, the package should work on everything....but should be tested of course :)
If we can avoid being broken by DNX updates all the time that would be
On Wed, 12 Aug 2015 09:00 Oren Novotny email@example.com wrote:
For what I've done so far, the Win10 tools aren't required. They would be if you want to use "modern PCL".
"all" I've done is put the existing Profile259 PCL in the \lib\dotnet dir and attach the reference generator tool to list out the correct set of dependencies for the dependency group. Because it's "just" a Profile 259 PCL, all of the package versions are 4.0.0 and work across all .NET 4.5+/System.Runtime systems.
If you use a newer PCL profile or a .NET Core based library that references newer BCL contract/package versions, then you'd need to do more work in the form of blank dependency groups and adding specific TFM lib dirs with compatible versions (the 259 dll). It's confusing for sure.
A few other thoughts: if you download nuget.exe, make sure it's the v3 beta. It's here for now: http://dist.nuget.org/win-x86-commandline/v3.1.0-beta/nuget.exe
Then call nuget restore on the sln for it to generate the proper .nuget.props/.nuget.targets/project.lock.json files
Add *.nuget.props, *.nuget.targets and project.lock.json to the .gitignore - nuget will generate those
As for building w/o VS installed, I'm not sure. Rember that MSBuild was split from the framework in 2013. The version in the system framework directory is old. You'll want to build with the v14 tools here: C:\Program Files (x86)\MSBuild\14.0\Bin\msbuild.exe. I don't know if that's available for install w/o VS.
I fear the build-agent-without-VS battle has been lost long ago :/
@onovotny If we wanted to keep
If we switched to target those, putting in the appropriate dependencies in
Reason being... I kinda like the new build structure. I'd hate to have to go back if I don't have to.
I couldn't get Android/Xamarin ("monoandroid5.0") or iOS/Xamarin ("xamarinios1") to work because we need
Since we have this working, I'll close this PR and we can update in the
Thanks again @onovotny for helping us through this one.
I'll update #668 accordingly.