-
-
Notifications
You must be signed in to change notification settings - Fork 38
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
Update Proj-Info to use FCS and FSharp.Core from 9.0.100 #219
Conversation
5942ee9
to
c792485
Compare
c792485
to
c3d18f3
Compare
3b245ad
to
31a2922
Compare
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.
Alright - the asset handling for the MSBuild packages is all set now. I also saw that one package wasn't getting a version - that was due to missing packagerefs on the build-time packages. I pushed those into Dir.build.props so that everything got them at the same time and in the same way. I also added small READMEs to the packages so that the NuGet warnings were satisfied and users might have a slightly-better getting started experience. After this I diff'd the local packages to the latest packages on NuGet.org and the content is structurally the same - with the exception that the Microsoft.Build packages no longer pollute callers. Now they will need to add their own MS.Build compile-time references, but the README for the Ionide.ProjInfo package includes those instructions. |
Fixes #218 #214
Supplants #211