Kinook Software Forum

Kinook Software Forum (https://www.kinook.com/Forum/index.php)
-   [VBP] Third Party Tools (https://www.kinook.com/Forum/forumdisplay.php?f=3)
-   -   Global macro DEVSTUDIO_NET_DIR is not detected correctly (https://www.kinook.com/Forum/showthread.php?t=970)

Wayne 03-24-2005 06:24 PM

Global macro DEVSTUDIO_NET_DIR is not detected correctly
 
On a fresh install of Visual Build Pro v.5.7, the global macro: "DEVSTUDIO_NET_DIR" is not set correctly.

It is:
"C:\Program Files\Microsoft Visual Studio.NET 2003"

instead of

"C:\Program Files\Microsoft Visual Studio .NET 2003"

(note the space between Studio and .NET).

kinook 03-24-2005 07:42 PM

Does 'Tools | Application Options | Macros | Reload Predefined Global Macros' help? To initialize the VSTUDIO_NET_DIR macro, VBP looks for the following registry values (which correspond to the values created by the VS.NET 7.1 [2003] and 7.0 [2002] installers, respectively):

HKLM\SOFTWARE\Microsoft\Microsoft Integration\03721D9F-6222-4200-BE0C-531F96AAF9B4\SuiteLocation

HKLM\SOFTWARE\Microsoft\Microsoft Integration\490D3C64-A846-4bcf-A22E-448B5157FA53\SuiteLocation

If neither is found, it defaults to "C:\Program Files\Microsoft Visual Studio.NET 2003" (it's does appear that this default doesn't match the actual default VS.NET 2003 install path, as you noted), but the first entry above should exist and be used to retrieve the actual path if you have VS.NET 2003 installed. Was there anything non-standard about how you installed VS.NET? Does that registry value exist?

Wayne 03-24-2005 07:57 PM

That's the problem, I don't have those 2 registry keys that you mentioned.

I do have this key: "04E753AE-B2B4-4936-8DA2-4BDE702139FF". I have Visual Studio .NET Enterprise Architect 2003, the MSDN version. Nothing special about how I set it up.

Why don't you guys detect the folder from "HKLM\SOFTWARE\Microsoft\VisualStudio\7.1" : InstallDir, and then parse the path?

kinook 03-25-2005 07:14 AM

I see. I don't know why we don't look for that registry entry, but it sounds like a good suggestion. Most users probably don't utilize these macros, instead using the Make VS.NET and VS.NET Get Version actions (which locate what they need differently), and I suspect that's why this issue wasn't noticed before. Thanks for the feedback.


All times are GMT -5. The time now is 02:17 AM.


Copyright © 1999-2023 Kinook Software, Inc.