To answer my own question...
When you run the build it creates these two keys:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\8.0Exp\VSTemplate\Ite
m
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\8.0Exp\VSTemplate\Pro
ject
Or in my case:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\VisualStudio\8.0Exp\VS
Template\Item
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\VisualStudio\8.0Exp\VS
Template\Project
The default value of these is the hard code path to your build folder,
if you move the build these keys not updated and the build copies the
Visual Studio template files to the folder.
This seems wrong to me - I will raise a bug.
Neil
From: Neil Sleightholm [mailto:[email protected]]
Sent: 10 June 2010 20:57
To: Windows Installer XML toolset developer mailing list
Subject: [WiX-devs] Votive2005 Build folder
Before I report this as a bug could some confirm what I am seeing. Every
time I build the WiX source the following folder is created:
"D:\WiX\WiX Source\build\obj\debug\x86\Votive2005\WiX"
It doesn't matter where the source of the build is located, currently it
is "C:\Source" but I have also tried "D:\WiX\WiX3.5\Source" and
"D:\WiX\Source". I have done a fresh get from Codeplex so I don't think
there is anything in the code path. The very first time I did the build
on this machine the source was in "D:\WiX\WiX Source" so I am suspicious
that something in the build has create a reference outside the source
folder.
Is anyone else seeing this?
Neil
Neil Sleightholm
X2 Systems Limited
[email protected]
------------------------------------------------------------------------------
ThinkGeek and WIRED's GeekDad team up for the Ultimate
GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
lucky parental unit. See the prize list and enter to win:
http://p.sf.net/sfu/thinkgeek-promo
_______________________________________________
WiX-devs mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-devs
