I noticed a bug when I'm using Autodesk's .NET API for AutoCAD 2013 64-bit, on .NET Framework 4.0 .
I have a plug-in for AutoCAD 2013 64-bit which I wrote using Visual Studio 2012 and C#. What happens is that, since my plug-in is a DLL, I set AutoCAD on the "Start external program" project settings page, so that Visual Studio will start debugging my DLL by starting up AutoCAD, who will then load my DLL up automatically on startup.
Now, I'm testing this plug-in with VS 2013 Professional RC.
The thing is, I noticed a bug when setting text styles through the .NET API on AutoCAD 2013 64-bit with VS 2013 Professional RC. If I start AutoCAD 2013 64-bit by pressing the green "Play" button inside Visual Studio 2013 Professional RC, AutoCAD fails to display a few texts that I create programatically. If I open AutoCAD's "Text Style Manager" dialog window, AutoCAD will then crash (and this window executes nothing from my plug-in's code, it just tries to load up the text styles that my plug-in created). However, if I load up AutoCAD normally (without debugging), then the texts display as they should, even with the same DLL that VS 2013 RC was debugging.
If I open the same solution on Visual Studio 2012 Professional, and start debugging my plug-in by starting AutoCAD with the same green "Play" button, this problem does not occur. That is, the texts are displayed normally.
1 - With VS 2012 Professional, my plug-in creates Text Styles inside AutoCAD with no problems when debugging.
2 - With VS 2013 Professional RC, my plug-in crashes AutoCAD when it tries to display the text styles I created, but only when debugging. If I'm not debugging, AutoCAD bevahes normally.
I added a small solution that is able to reproduce this bug.