feat(vs): integrate with Visual Studio 2015 .NET Core Preview 2 tooling #163
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
BrainCrumbz
force-pushed
the
feat/integrate-vs2015
branch
from
16400a8 to
d753ee3
Compare
BrainCrumbz
force-pushed
the
feat/integrate-vs2015
branch
from
65d6223 to
4594788
Compare
BrainCrumbz
force-pushed
the
feat/integrate-vs2015
branch
2 times, most recently
from
b1fcddc to
a536cd6
Compare
... exception stacktrace changing from Debug build
Source code file/line number still missing.
…tive.amd64.dll That happens only on .NET 4.5.1
Also, mention working VS Test Explorer integration
When both a context and its sub-context should be run, examples in the sub-context are run twice: once for the sub-context, and once again when the parent context runs.
BrainCrumbz
force-pushed
the
feat/integrate-vs2015
branch
from
a536cd6 to
61f7e42
Compare
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.
This PR tracks progress on changes needed for integrating dotnet-test-nspec runner with Visual Studio 2015 and .NET Core Preview 2 tooling.