Changes are not allowed while code is running


  • Started VS ultimate 2013:

    1. Pointed to specific Application in Set As Start Project in Debug mode.

    2. Located to code base and tried to update something.

    3. Closed the running application

    4. Display popup message "Changes are not allowed while code is running", not able to close that popup message as It is not allowing to close VS 2013 and also OK button not working.

    So Visual Studio hanged and not able to close it manually (Not allowed to use Close button as popup windows enabled). 

    This is my second time to reproduce the same issue. Please help me to short out that problem. There is one way to start VS by forcefully need to close using Task Manager.

    Monday, January 2, 2017 6:16 AM

All replies

  • Hi Suresh Kumar Kaushik,

    After closing the running application, does the Visual Studio debugger also stopped? Please try stop the application by click the Stop debugging button to check whether this issue also occurs.

    If the Visual Studio debugger is not stopped, please check whether there has any breakpoint hit when you try change the code. Because only the breakpoint is hit when the debugger is running, we could change the code. And also please make sure you have enable edit and continue setting in Visual Studio.

    According to your description, the pop up window could not be closed by click the OK button and close button, is it right?

    Please try run your Visual Studio in safe mode to check whether there has any VS add-ins causes this issue. And please check the ActiveLog.xml under the path of %AppData%\Microsoft\VisualStudio\14.0. This file will log all operations when you operate Visual Studio. We need to check whether there has any error occurs when try to close the pop up window.

    Best Regards,

    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact

    Tuesday, January 3, 2017 6:13 AM