Skip to content
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

Add support for Microsoft.Build.CentralPackageVersions #1311

Merged
merged 1 commit into from
Sep 7, 2019

Conversation

david-driscoll
Copy link
Contributor

This pull request is intended to add support for two things.

  1. Projects that use Update semantics for PackageReference (and friends) instead of Include. (ex https://github.com/OmniSharp/omnisharp-roslyn/blob/master/build/Packages.props)
  2. Projects consuming Microsoft.Build.CentralPackageVersions.
    • Microsoft.Build.CentralPackageVersions adds a new file convention Packages.props in addition to Directory.Build.props/targets. It also adds a new element GlobalPackageReference used for private Package References.

Some problems I'm aware of...

  1. I'm a {}ist (ie I'm not super familiar with ruby, but I'm learning!) 🤣
  2. I did not add any specs (see 1 and below)
    • I'm currently battling to get a Ruby environment setup on windows... because that's always fun!

I was hoping I could get some guidance or assistance from someone like @greysteil, obviously you're busy working on everything else, but any help there would be appreciated.

see #1182

Copy link
Contributor

@greysteil greysteil left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks good! It needs tests, but let's figure out the logic first.

nuget/lib/dependabot/nuget/file_fetcher.rb Outdated Show resolved Hide resolved
@david-driscoll
Copy link
Contributor Author

I was not able to get things working on windows, but I was able to get them working with WSL2! Currently working on adding some tests.

@david-driscoll david-driscoll force-pushed the feature/csproj-update branch 3 times, most recently from 19688a2 to 6f23701 Compare August 16, 2019 03:52
@david-driscoll
Copy link
Contributor Author

@greysteil when you are able to, any help with additional testing that I should do would be greatly appreciated!

@david-driscoll
Copy link
Contributor Author

@greysteil let me know what else I can do for this.

Thanks!

@greysteil
Copy link
Contributor

Sorry for the delay reviewing this @david-driscoll.

If you rebase it and squash it down to a single commit I'll get it merged and deployed. :octocat:

@greysteil greysteil force-pushed the feature/csproj-update branch from be12457 to f7c62cd Compare September 7, 2019 13:32
@greysteil
Copy link
Contributor

Thanks for your work on this!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants