Update dev build to include old and new system.valuetuple #4589
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.

In a recent overhaul of the build. We updated to 4.4.0 of the System.ValueTuple nuget package.
We also updated the templates to support this newer nuget package.
However, the templates with the VS2017.6 and VS2017.7 previews require the 4.3.1 nuget package. This PR amends developer builds so that they will deploy both the 4.3.1 and 4.4.0 System.ValueTuple, when the template is created.
Note: When VSIX installs a nuget package, it doesn't really go to nuget and install it. It sort of fake drops files.
This change is only intended to impact developer builds, internal product builds will only deploy the correct version.
@brettfo can you confirm that microbuild is set for internal builds.