Hello,
Recently, when working in a Visual COBOL 4.0 Visual Studio 2017 environment, if we leave Visual Studio 2017 up for a length of time, we get the following Visual Studio 2017 error. We then have to kill Visual Studio 2017 via Task Manager.
Has anyone else experienced this? Could this have been caused by a Microsoft update?
![]()





