Merged
Conversation
Member
Author
|
@jaredpar @dotnet/roslyn-infrastructure PTAL |
Member
Author
Contributor
I assume this is because we need .NET Core compatible versions of those targets? |
Member
Author
jaredpar
approved these changes
Jul 6, 2020
Member
|
Really excited about this. Would much prefer to just
What is the mechanism that makes this happen? I can see from the change why we don't produce the uber VSIX anymore but can't see why the individual VSIX are no longer building. |
Member
Author
|
Arcade skips VSIX targets when building on .NET Core. |
2 tasks
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Roslyn.sln can now be built using
dotnet build/pack. VSIXes are not produced from such build.Allows us to run test projects targeting .NET Core that are not in Compilers.sln.