This repository was archived by the owner on Mar 17, 2025. It is now read-only.
Repository navigation
Fix installation of Project File Tools on Visual Studio 2019 updates - #62
Merged
Merged
Conversation
|
Please merge this PR for benefit of others |
mlorbetske
reviewed
Jul 7, 2019
mlorbetske
left a comment
Contributor
There was a problem hiding this comment.
Thanks for contributing this :)
Contributor
Collaborator
|
@mlorbetske I can't approve PRs on this repo. @jaredpar can you? I can do the build and release a new version to the Marketplace once it's merged |
|
Ping! Hope we can move this forward. |
|
@madskristensen Can you find someone else that can approve this if @jaredpar not have the possibility? |
Collaborator
|
@davkean ? |
|
Just a side note that my PR (#64) also addresses the VS 2019 update. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Unlike other VS releases in 2019 updates minor point releases are being used (src). So I changed the range like specified in this blog post. This fixes issue #61.