-
Notifications
You must be signed in to change notification settings - Fork 123
Cleanup for .NET Core SDK preview2 #616
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
ref dotnet/msbuild#394 ``` C:\Program Files (x86)\MSBuild\Microsoft\NuGet\Microsoft.NuGet.targets(140,5): Your project is not referencing the ".NETFramework,Version=v4.5" framework. Add a reference to ".NETFramework,Version=v4.5" in the "frameworks" section of your project.json, and then re-run NuGet restore ```
|
ok better now 😄 So issue was references.
i think is enough to be future proof in the near term. |
|
Down to only 2 failures: I checked and the attributes exists in the .net core |
|
Ok skipped (with I removed the additional appveyor job, now .net core is ok and should remain always green |
|
Nice work, LGTM. I would really appreciate merging this soon and keeping the build green. Whenever I come back to update to latest FSharp.Compiler.Service I need some hours to figure out how to compile the thing for dnc ... |
| "Microsoft.Build.Tasks.Core": "0.1.0-preview-00028-160627", | ||
| "Microsoft.Build.Utilities.Core": "0.1.0-preview-00028-160627", | ||
| "System.Runtime.Serialization.Json": "4.0.2", | ||
| "Microsoft.FSharp.Core.netcore": "1.0.0-alpha-*", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why not "FSharp.Core": "4.0.1.7-alpha"?
masterproject.jsonare in the same directory of the projects (no more .netcore suffix)dotnet testinsidetests\servicedirectorybuild Release(or justNuget.AddNetCore) will build, run tests (failing atm) and merge packages