reverting Syntax Vizualizer dependencies to use MSBuild so we can specify that nuget dependencies are build-time only #7261
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.
#7259 introduces a problem: project.json has no way to specify that dependencies should not be copied to the output folder (buildtime vs. runtime dependencies), therefore it will happily copy Microsoft.CodeAnalysis.dll Version 1.0 over the top of Microsoft.CodeAnalysis.dll 1.2 since all of our binaries are dropped into a single directory.
To solve this, we revert back to packages.config which gives us the ability to test that certain sets of dependencies should not be copied to the output folder.