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
Setup MSBuild requires a private package for Microsoft.Net.Compilers.Targets.NetCore #4952
Comments
I believe @joperezr is going to make sure the package is available, or otherwise modify the buildtools package so it doesn't need this package. |
@joperezr: Do you have an ETA of when we will have buildtools that don't depend on the private NuGet package? Thanks. |
The problem is not the dependency in the private packages, since they can be uploaded to the build tools easily. The problem is that the MSBuild that we have right now doesn't run in Mac OS X since it crashes just after we invoke it. @rainersigwald is helping us fix this and hopefully he can get this working today so that we can depend on new packages that work across all platforms. |
@joperezr Tracking that as dotnet/msbuild#441. Currently working to resolve flakiness with build and test after updating our .NET Core dependencies. |
dotnet/msbuild#441 is fixed as of MSBuild packages version |
The packages have been published and the code change was made with dotnet/buildtools#396 |
Done, package version 00157 contains .Net Core MSBuild. @JohnChen0 if you want to see an example of how to use it, please take a look at dotnet/corefx#5711. The most important files you want to keep an eye on, are init-tools.sh and init-tools.cmd in the corefx repo, and how we call them from the build.cmd and build.sh. If you have any questions please let me know. I'm closing this issue since the package is ready. |
Resolving issue #4633 requires setting up an MSBuild that runs under CoreCLR. Currently, this setup requires a private NuGet package for Microsoft.Net.Compilers.Targets.NetCore. This package needs to be made available on a public feed.
The text was updated successfully, but these errors were encountered: