Problem installing for Visual Studio 2003

Hello,

I’ve just dowloaded the SDE for Visual Studio 2003. At least that was my intention. I used the following link: http://www.visual-paradigm.com/download.jsp?product=sdevs&edition=ce

The installation wizard only gives me the following options:

  • Visual Paradigm for UML 4.1
  • Smart Development Environment 2.1

    SDE for Exlips/IBM…
    SDE for Jbuilder
    SDE for Netbeans
    SDE for IntelliJ
    SDE for JDeveloper
    SDE for WebLogic

Now, where is Visual Studio? After installation I can use the Visual Paradigm tool, but not as a VS-plugin. It seems like I have downloaded a wrong version. But at the download screen it said “for visual studio”.

Help!!

Thanks in advance.
J

Dear Johnny,

Sorry for my late response. During installation, the installer will check for the system registry to determine weather the VS .NET 2003 was being installed or not. Could you please check the following registry value exist in your system or not?

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Path\sdevenv.exe

If the entry is not exist, please make it point to your “devenv.exe”.

I’m looking forward to hear the reply from you. Thanks in advance.

Best regards,
Rain

Hello Rain,

Indeed, I hadn’t such a key in “HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths”.
I’ve just added the key “sdevenv.exe” with inside the strings:
“default” (path + exe) en “path”.
Should I reinstall Visual Paradigm?

Thanks for your assistance.

J

Dear Johnny,

Sorry for my late response. The SDE-VS option should be enabled in the installer after adding the registry key & values. Please make sure the key and values are:

Key: “HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths”

Values:
Location of your “devenv.exe”

If you have any further questions, please feel free to contact us again.

Best regards,
Rain

Indeed, adding the key in the registry worked for me, although I think is a bug.

Dear John,

Actually the registry value should be comes with the VS. We don’t know why it will be missed for some users (Maybe different build of the VS). Our engineers will keep on investigate on this problem.

Best regards,
Rain