Search

Editors become unavailable for files left open during a debugging session by ITJoeB

Closed
as Not Reproducible Help for as Not Reproducible

1
0
Sign in
to vote
Type: Bug
ID: 777778
Opened: 1/29/2013 9:01:42 AM
Access Restriction: Public
0
Workaround(s)
0
User(s) can reproduce this bug
While working on code files, XAML files, EDMX files, and presumably any other type of file, leaving those files open and launching a debugging session causes the editors for those files to close. After debugging is stopped, Visual Studio is no longer able to open the editor for any file that was left open prior to starting the debugging session. Double-clicking any of these files shows a "No editor available" message in the status bar.

The only resolution is to close and re-open the solution, or restart Visual Studio.
Details (expand)

Visual Studio/Team Foundation Server/.NET Framework Tooling Version

Visual Studio 2012

Steps to reproduce

1. Open or create a WPF application
2. Open a XAML file for editing
3. Start a debugging session by hitting F5 or any other means.
4. The open file editor closes
5. Stop the debugging session
6. Double-click the file

Product Language

English

Operating System

Windows 7 SP1

Operating System Language

English

Actual results

Editors fail to launch for files that were left open at the start of the debug session. Editors for other files of the same file type are able to be opened, however.

Expected results

Editors would continue to launch normally regardless if the file was being edited prior to debugging.
File Attachments
0 attachments
Sign in to post a comment.
Posted by Microsoft on 2/4/2013 at 2:41 AM
Hi ITJoeB, we'll close this feedback because we can't repro it. Please recreate a new feedback and upload a demo project if you have not resolved this issue. Thanks.
Posted by Microsoft on 2/1/2013 at 2:08 AM
Hi ITJoeB, we want to remind you we have send a new message. Please reply to us in time. Thanks.
Posted by Microsoft on 1/29/2013 at 6:28 PM
Hi ITJoeB, thank you for submitting feedback on Visual Studio and .Net Framework. It's hard for us to repro this issue. Do all of the projects created on your machine have this problem? Could you upload a demo project to help us repro it? Thanks.
Posted by Microsoft on 1/29/2013 at 9:50 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.