Visual Studio crash when renaming explicit interface method implementation - by Dave Fancher

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


2
0
Sign in
to vote
ID 2092048 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 12/4/2015 9:40:21 AM
Access Restriction Public

Description

Using the refactor/rename option to rename an explicitly implemented interface method at the implementation causes Visual Studio to crash. This appears to happen only when the interface and implementation are defined in a separate project than where they're used.
Sign in to post a comment.
Posted by David [MSFT] on 1/24/2016 at 10:44 AM
Hello Dave,

Thanks for taking the time to report this issue. The failure continues to reproduce on Visual Studio 2015 Update 1, so I've ported this issue to GitHub at https://github.com/dotnet/roslyn/issues/8139. You're welcome to post follow-up comments here or there, or to subscribe to updates as we make progress on or discuss the issue. I've also added some context to the GitHub bug (callstack and explanation of the bad assumption made in the rename engine) if you're interested.

Regards,
David Poeschl
Posted by Microsoft on 12/4/2015 at 10:03 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If you require immediate assistance with this issue, please contact product support at http://support.microsoft.com/oas/default.aspx?gprid=1117.