So we’ve got a bunch of GIS people with 64-bit Windows, as you’d expect. Unfortunately, Autodesk thinks supporting 64-bit Windows is unnecessary. The installer won’t let you install it, and even when you bypass that, it throws an error when you launch the program. With Studio being a .NET application and WOW64 being pretty damn good at running things in 32-bit mode, I was pretty sure this was just some obscene laziness on their part. After some unsuccessful hacking with compatibility modes and editing the .manifest file, I landed on something that works. There’s a tool distributed with the .NET SDK (in Visual Studio) called CorFlags. This tool can be used, among other things, to set a .NET assembly to be forced to run in 32-bit mode. After getting MapGuide Studio to install by directly executing the MSI on the trial DVD, I used this command to make it run right:
C:\Program Files (x86)\Autodesk\MapGuideStudio2009> CorFlags Studio.exe /32BIT+
… and it works flawlessly. Yes, it’s that easy. What a bunch of douchebags.
Filed under: Random
[...] not sure I agree with rbranson’s assessment (my guess would be testing and support resources rather than laziness) but this is a pretty useful [...]
Does anynone did this step-by-step with sucess?
Please let us now.
I am still having issues installing the MapGuide Studio. You said that you installed it by directly executing the MSI on the trial DVD. I have downloaded my trial version from Autodesk web site – how do I install it in that case (no trial DVD).
Thanks,
I agree with you. Autodesk is way behind on supporting technologies. Many customers are using 64bit OS and Studio is a client application (not installed on server) and should be compatible. I understand the server not being ready with the lack of focus and/or investment in that department but at least make the client side applications 64bit ready. I wonder if they even warn customers that buy Map 3D 64bit and get MapGuide as their web platform. My best guess is no and the answer to why will never be known.