If you are having trouble debugging your addons/plugins for Autodesk Civil 3D release 2012 you are certainly going to want to read this. The information presented also appears to be applicable to other products such as Autodesk Inventor 2012 and AutoCAD MEP. Probably even all AutoCAD 2012 based products. You probably found this post while searching for things relating to debugging your AutoCAD Civil 3D 2012 addons and running into a problem where the Visual Studio 2010 debugger fails to hit your breakpoints and does not show you the source of your application that you are debugging.
The result is that I am finding it very annoying and painful on the eyes. But not so much the color schemes using a dark background themselves, but rather the practical implications when using it while doing actual work. The dark background allows for better highlighting of code, no doubt about that, but in a practical situation I often have other applications running on the screens which include things like help files, CHM’s and PDF’s with developer documentation and API docs, Outlook, OneNote, Visio, and many other development tools, etc. and almost all of these applications will use a light or white background as a basis.
People have asked me to write something about some of the typical usage scenarios that I often find myself in at my home office. Since those are generally not easy to explain in a few words and since they could otherwise fill up the FAQ page a lot I’ve decided to just write them as posts in the blog and relink those back from the FAQ page for details. Note: This was written when I was using the old setup, not the new setup, so details now vary but the general idea of the content here is still the same and as applicable as it was before.