如何增加允许 Visual Studio 无响应的时间？

Question

I am trying to develop an application in C# communicating via OData with Microsoft's Dynamics 365 for Finance and Operations solution. This uses a large (900,000+ lines) file produced by Microsoft's OData V4 Client Generator extension (V2.4.0).

Whenever I accidentally step into code in this file while debugging, or try to look at a definition in it (whether the application is running or not), or otherwise just open the file, Visual Studio 2017 (currently version 15.5.6) will become unresponsive and be restarted a few seconds later.

Visual Studio 2015 used to start getting various panels no being refreshed and flickering as complete blank before it failed. Visual Studio 2017 just locks up.

I have wondered if the timeout before it gets restarted could be increased, so that it has to complete whatever it's doing, assuming it will recover.

If anyone has another way to work with huge autogenerated files, I'd be willing to try them. Obviously, spending hours manually breaking up the file is not an option and my attempts to split the file into multiple files using partial classes simply wouldn't compile (as I recall, the error was that it ran out of string space - presumably, VS couldn't maintain all the cross-file information for over two thousand partial classes in its internal structures).

Answer 1

You can try to close the large file window immediately on opening to prevent Visual Studio from processing it. For example in a IVsRunningDocTableEvents.OnBeforeDocumentWindowShow handler:

public int OnBeforeDocumentWindowShow(uint docCookie, int fFirstShow, Microsoft.VisualStudio.Shell.Interop.IVsWindowFrame pFrame)
{
    try
    {
        if (GetDocumentName(docCookie).EndsWith(fileToBlock, System.StringComparison.CurrentCultureIgnoreCase))
            pFrame.CloseFrame((int)Microsoft.VisualStudio.Shell.Interop.__FRAMECLOSE.FRAMECLOSE_NoSave);
    }
    catch (System.Exception e)
    {
    }
    return Microsoft.VisualStudio.VSConstants.S_OK;
}

See Block certain file from opening in a document tab sample extension for Visual Commander.

Answer 2

Searching the forums on MSDN I was able to find a high number of people with the same issue you're reporting. The VS Development team said they've fixed those issues back in August 2017.

You could try to update Visual Studio and get the release with the fix or try disabling diagnostics tools and elapsed time PerfTip:

If your project is compatible with VS 2015, I'd suggest going back to it if you still have a working license.

Source:

Slow IDE when Diagnostics Tools is turned on

Slow IDE when CodeLens is turned on

Slow IDE when fusion logging is turned on