While we are waiting for our application server to be configured we have started some preliminary testing of our application outside of the VS IDE on our development PCs. Everything runs as expected when there are no errors, but if an error is encountered then a "Visual Studio Just-In-Time Debugger" window opens and must be manually dealt with. When we click the "No" button then the error messages familiar to us from our Net Express days are displayed.
We are using VS 2013 and VC 2.3 for VS 2013 on a Windows 7 PC. Our projects are Native COBOL, Release configuration (no "Compile for debugging"), x64 platform, and linked as Dynamic with binding. The Console Application projects include system programs, the Link Library projects do not.
Q1. So why is a .idy file created on Build?
Q2. Why is the VS JIT Debugger being triggered if everything is built with no "Compile for debugging"?
Q3. Is there a way to disable or get around the triggering of the VS JIT Debugger?
Q4. Is this going to happen under COBOL Server 2.3?