Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Predefined Path variables

Created: 21 May 2013 | 6 comments

Hello,

Is there a way to adjust the values of the path variables in Installer Editor? One of them is "VisualStudioProjects", which defaults to my documents/visual studio projects - but I have it different, so would be nice to modify it.

According to the Help article "About Path Variables", "You cannot modify predefined path variables", but I was still wondering where it takes them from.

Thanks

Operating Systems:

Comments 6 CommentsJump to latest comment

VBScab's picture

I don't know for sure but I wouldn't mind betting it takes them from the registry's "Shell Folders" or "User Shell Folders". Search for the path text in the registry. Some Googling suggests that HKCU\Software\Microsoft\VisualStudio\[x]\MyDocumentsLocation, where '[x]' is the VS version number, might be a good place to start.

Don't know why 'x' happened? Want to know why 'y' happened? Use ProcMon and it will tell you.
Think about using http://www.google.com before posting.

EdT's picture

The order of installation may be relevant here as well.

Generally, the Wise product should be installed last if you are planning to integrate with something like Visual Studio - certainly this always used to be the case with .NET frameworks to ensure that the .NET functionality was fully implemented in Wise.  Reputedly, running a repair on Wise would sort this out if one of the other components was installed after Wise.

If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.

Vadim Rapp's picture

Yes, that's what I did - first Visual Studio, where I have configured the path for the projects; then Wise.

Anyways, I figured it out. Running regmon trace showed that upon startup, WfWI is looking for this:

2.57789660    WfWI.exe:5620    QueryValue    HKCU\Software\Microsoft\VisualStudio\8.0\VisualStudioProjectsLocation    NOT FOUND        
 

Once I created that value, the predefined variable has changed. The problem probably was in the fact that my Visual Studio is 2008, i.e. it's 9.0 (and the directories are configured differently, with different value names), while Wise is looking for 8.0, i.e. VS 2005.

 

VBScab's picture

Great job, Vadim. Your doggedness is in sharp contrast to the spoon-feeding which we commonly have to engage in here.

@Ed, The Force is strong in this one...

Don't know why 'x' happened? Want to know why 'y' happened? Use ProcMon and it will tell you.
Think about using http://www.google.com before posting.

EdT's picture

@VBscab - clearly another of your Procmon disciples....

If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.

Vadim Rapp's picture

My biggest procmon odyssey was investigating where pdfcreator is storing the information about the security of the printer, when I was repackaging it into MSI. Took 2 days.