Namespace collisions with Visual Studio SDK #85
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
…this can build in a vsix solution
I am unsure how to unit test the interfaces and intended functionality without hooking it into Visual Studio and finishing the run factory. all existing unit tests pass.
…een implemented so far
…olete set to throw a compiler error.
…at understands netstandard 2.0 and 4.5
This reverts commit 5d5c176.
…app domain is the process.
…et core runtime, one need to account for the runtime
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
closes #84
closes #86
closes #87
closes #88 created a unit test to verify that the parameter property is static