We have upgraded to Visual Studio 2008 but are still stuck with Visio for Enterprise Architects 2003 for designing databases. Recently my system started causing some problems, and I decided to format my hard disk and reinstall Windows XP, since it had a lot of obsolete/unnecessary stuff too. So I backed up all data, formatted C drive and installed everything afresh. Finally I started installing my development environment. I installed Visual Studio 2008 and wanted to skip Visual Studio 2005 installation. But the Visio for Enterprise Architects setup won’t let me do that. The setup won’t work until you install Visual Studio 2005.
I really didn’t want to install Visual Studio 2005, since we no longer use it. We have already upgraded all our projects to .NET framework 3.5. (Visual Studio 2008)
I searched for workarounds on the internet and finally hit upon some hints.
This is what I did.
- Run Regedit
- Backup the entire registry, less something goes wrong.
- Create the following registry key:
- Inside the VSTD key, create a string value named ProductDir and set it to any value. (I had set it to “1”)
- Close Regedit and run the Visio setup. It should now run smoothly.
I created and saved a copy of reg file that inserts the required keys, so that the next time I run into such situations I find this handy. So if you don’t want to follow the above manual procedure, or won’t like to mess around with the registry editor, just download & run the reg file I created.
Download link: VisioEA Registry Hack
What if It doesn’t Work?
Hacks are hacks after all. They may work in one situation and not in others.
This hack worked for me. But from what I read from various resources on the internet, it doesn’t work for everyone. This depends on your version of Visio or Operating System etc.
If the hack didn’t work for you, try the following alternatives:
In the above procedure, step 3, try with these other registry key variations (other steps remain the same). One of these might work for you:
A Word of Caution here
- Playing with the registry can be harmful. Do whatever you want to do with your registry at your own risk. I take no responsibility for any damages or anything else whatsoever.
- As with any other hacks, you may or may not be violating any license terms etc.. I never bothered to looked at that. So, do that at your own risk.
- As with any other files, scan downloaded files for viruses. I may not be having the best antivirus in the world and I undertake no responsibility for any damages caused to your system by using the files. Specifically, *.reg files have the ability to cause damage to your system, since they are executable files.