![]() ![]() So one thing MM does is add the Markdown Monster install path to User's path so that you can type mm Readme.md or mm data.json or mm web.config (MM supports editing a few common text formats besides Markdown) to view the document in the editor. The application checks whether certain values have been set and if not attempts to set them.Īs you probably know, system folders and registry paths can vary depending on whether you are running 32 bit or 64 bit. MM requires a few file and system registry settings in order to work properly - specifically IE 10/11 browser emulation and an optional path check - in order to work properly. I ran into the 32 bit issue while debugging some start up configuration check logic in Markdown Monster. NET is actually big deal.ģ2 bit/64 bit issues usually come up in relation to OS features and locations that are different. If you don't think that's cool, you probably haven't done low level C/C++ style programming before and don't know how much of a pain dealing with bitness can be! That it's so easy in. The framework masks most of those differences for us. NET is that it for the most part doesn't have to care what CPU platform you're running under. One of the beauties of a runtime environment like. 32 Bit Debugger for 64 Bit Process?īefore we get into this I want to clarify that in most cases it's probably OK to be debugging in 32 bit mode when running what otherwise is a 64 bit application. In the process I discovered quite a few things of the debugger I wasn't aware of along with a few suggestions from Kirill Osenkov that were illuminating and that I'll share here. I found out the hard way today that when you fire up the debugger in Visual Studio it will launch in 32 bit mode by default even if the application would run 64 bit when run directly. I've been working on Markdown Monster which is a 64 bit application. ![]()
0 Comments
Leave a Reply. |