New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

COMException when navigating to step definition #9

Merged
merged 1 commit into from Dec 2, 2016

Conversation

Projects
None yet
2 participants
@ChristopherHaws
Contributor

ChristopherHaws commented Oct 29, 2016

Please see: techtalk/SpecFlow#726

This isn't the most ideal solution, but it does work as a workaround until the Roslyn team fixes the issue.

@SabotageAndi

This comment has been minimized.

Show comment
Hide comment
@SabotageAndi

SabotageAndi Nov 2, 2016

Collaborator

Thanks for the PR. Looks like a changed behavior from VS2013 to VS2015.
Do you have some information about this Roslyn issue?

I tried the fix and it is working with the provided test project.
But I had to add a using System.Runtime.InteropServices; because of the COMException.
Could you add this to the PR and then I will merge it.

Collaborator

SabotageAndi commented Nov 2, 2016

Thanks for the PR. Looks like a changed behavior from VS2013 to VS2015.
Do you have some information about this Roslyn issue?

I tried the fix and it is working with the provided test project.
But I had to add a using System.Runtime.InteropServices; because of the COMException.
Could you add this to the PR and then I will merge it.

@SabotageAndi SabotageAndi merged commit 9717a4d into techtalk:VS2015 Dec 2, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment