This repository has been archived by the owner on Dec 19, 2018. It is now read-only.
Create NoVSIX solution configurations #985
Merged
Conversation
This file contains 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
rynowak
approved these changes
Feb 9, 2017
natemcmaster
force-pushed
the
namc/no-vsix
branch
from
dad04ae to
eaadfb7
Compare
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.
In anticipation of aspnet/KoreBuild#159 which will build solution files instead of .csproj files. dotnet-CLI can't build the VSIX project (yet), so we want to disable this on the regular run of dotnet-msbuild.
This creates two solution configs, ReleaseNoVSIX and DebugNoVSIX which have disabled building the tooling/Microsoft.VisualStudio.RazorExtension.csproj project.
Also, removes the x86 and x64 configurations (pretty sure we don't need them, but can put back if I'm wrong).