Debug problems with AutoCAD 2017 and Visual Studio Express 2017

Debug problems with AutoCAD 2017 and Visual Studio Express 2017

mconley
Enthusiast Enthusiast
517 Views
1 Reply
Message 1 of 2

Debug problems with AutoCAD 2017 and Visual Studio Express 2017

mconley
Enthusiast
Enthusiast

We have a VB.Net program that we have been using for years at our company that creates drawings in AutoCAD and also creates documents in Excel.    An update came out for Office 365 on Monday and now when the program starts filling in values in Excel,  a HRESULT 0X800A03EC error occurs with the computers that have Office 365.    For the computers that have Excel Pro 2013, the program still runs fine.  

 

The computer on which the program is compiled has Excel Pro 2013.    So, we installed Visual Express 2017 on a computer that has Office 365 so that we could debug the program to find out where the error is happening.

 

The problem we are having is that after netloading the application in AutoCAD while in debug mode on the computer with Office 365, we get an unknown command message when trying to start the program.   We have set the references in Visual Studio to FALSE for copy to local and that does not fix the problem.    We set the debug settings in Visual Studio Express on the computer with Office 365 to match the computer where we can debug but still no success.

 

When not in debug mode, we can netload the program and it will run.

 

Anyone have any more ideas on how to get AutoCAD to recognize the command in debug mode.  

0 Likes
518 Views
1 Reply
Reply (1)
Message 2 of 2

mconley
Enthusiast
Enthusiast

We were able to get debugging to work by turning on  "Use Managed Compatibility Mode" in Visual Studio.

 

0 Likes