[WiX-users] Installing drivers with subdirectories
John, Thanks for the response. If I create two ordinary components for the subdirectories then they don't get copied to the DriverStore directory so that inf file can't find them. And if I add the difx tag to the subdirectories, the install fails. I just can't seem to get the subdirectories installed into the DriverStore directory. Very frustrating that this should be so hard - given that I see many installer file sets that have subdirectories. Richard, Just create normal components for the two subdirectories, and a third component just containing the INF file and the difx attributes, and then add all three to the same feature. I think that the difx stuff only has to be attached to the INF file. Regards, John - Sent from Yahoo! Mail. A Smarter Email.- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] converting .reg to .wxs in WiX 3.0
Hi,
I'm using v3.0.4116.0 currently (installing v3.0.4123.0 first thing
tomorrow morning).
I have a problem with the COM registration info heat.exe generates for
one of our executables (not written by me). It doesn't seem to get all
the required entries. The generated code is as follows:
?xml version=1.0 encoding=utf-8?
Wix xmlns=http://schemas.microsoft.com/wix/2006/wi;
Fragment
DirectoryRef Id=appsFolder
Component Id=iesoop
Guid=503CDCB9-669D-4c18-BF30-B1319A127326
File Id=iesoop.exe Name=iesoop.exe KeyPath=yes
Source=..\..\..\bin_release\iesoop.exe
TypeLib Id={7749E01A-8723-476D-905F-E8F97EDF8AF6}
Description=iesoop Type Library Language=0 MajorVersion=4
MinorVersion=0
Interface
Id={22624D71-96AA-4581-AF1B-E58539EB3EC3} Name=_IBridgeEvents
ProxyStubClassId={00020420---C000-0046}
ProxyStubClassId32={00020420---C000-0046} /
Interface
Id={93B8BD76-7C0A-4119-84C7-3FDCF9B7477C} Name=IBridge
ProxyStubClassId={00020424---C000-0046}
ProxyStubClassId32={00020424---C000-0046} /
/TypeLib
/File
RegistryValue Root=HKCR
Key=TypeLib\{7749E01A-8723-476D-905F-E8F97EDF8AF6}\4.0\HELPDIR
Value=[appsFolder] Type=string Action=write /
/Component
/DirectoryRef
/Fragment
/Wix
When I use RegSpy on this app it generates much more than those entries
above. When I install our application it fails to run. If I run the
above executable after installation with the /regserver parameter then
run our application it works fine. This is what leads me to believe
heat.exe is missing some of the self-registration info.
In WiX 2.0, tallow.exe happily took a .reg file output the required
XML, heat.exe in 3.0 refuses to play the game (outputs a fragment with a
directory, component file tag for the .reg file!).
Does anyone know how I can convert the .reg file I've extracted using
RegSpy to WiX 3.0 XML? heat.exe seems to have no documentation at all
other than what it outputs when run with /? I really don't want to have
to use a custom action for this.
Cheers,
http://www.iesve.com/
Palbinder Sandher
Software Deployment and
IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com http://www.iesve.com/
**Design, Simulate + Innovate with the Virtual Environment**
Integrated Environmental Solutions Limited. Registered in Scotland No.
SC151456
Registered Office - Helix Building, West Of Scotland Science Park,
Glasgow G20 0SP
Email Disclaimer http://www.iesve.com/disclaimer.html
att6a1b8.jpg-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Build Wix v3.4123 Issues
The WiX.chm Building WiX has the list of external SDKs that you must have installed to build fully. The other issues (besides the paths not being set correctly) are bugs, please do feel free to open them on SourceForge so we are sure to fix them. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kelly Leahy Sent: Wednesday, May 28, 2008 10:37 To: Eva, Mark E (ESL Lab-Boise) Cc: [EMAIL PROTECTED]; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Build Wix v3.4123 Issues http://msdn.microsoft.com/en-us/vsx/default.aspx Not sure if it's what you need, but it wouldn't surprise me. Eva, Mark E (ESL Lab-Boise) [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 05/28/2008 10:33 AM To Kelly Leahy [EMAIL PROTECTED] cc [EMAIL PROTECTED] [EMAIL PROTECTED], wix-users@lists.sourceforge.net wix-users@lists.sourceforge.net Subject Re: [WiX-users] Build Wix v3.4123 Issues I am running VS Team System 2008 Team Suite - ENU I thought it had everything. I will look for the SDK. Thanks, Mark From: Kelly Leahy [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 28, 2008 11:23 AM To: Eva, Mark E (ESL Lab-Boise) Cc: wix-users@lists.sourceforge.net; [EMAIL PROTECTED] Subject: Re: [WiX-users] Build Wix v3.4123 Issues looks like you might be missing VSIP (the visual studio SDK)? Eva, Mark E (ESL Lab-Boise) [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 05/28/2008 10:21 AM To wix-users@lists.sourceforge.net wix-users@lists.sourceforge.net cc Subject [WiX-users] Build Wix v3.4123 Issues [exec] Done building target VsTemplatePathsTarget in project Votive2008.csproj -- FAILED. [exec] [exec] Done building project Votive2008.csproj -- FAILED. [exec] [exec] Build FAILED. See attached details in The following is a list of all issues I have had trying to build Wix. The latest issue #7 is above. I don't have a solution for it as yet. Mark E. Eva - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ** This communication is intended solely for the addressee and is confidential. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Unless indicated to the contrary: it does not constitute professional advice or opinions upon which reliance may be made by the addressee or any other party, and it should be considered to be a work in progress. Unless otherwise noted in this email or its attachments, this communication does not form a Statement of Actuarial Opinion under American Academy of Actuaries guidelines. **- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ** This communication is intended solely for the addressee and is confidential. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Unless indicated to the contrary: it does not constitute professional advice or opinions upon which reliance may be made by the addressee or any other party, and it should be considered to be a work in progress. Unless otherwise noted in this email or its attachments, this communication does not form a Statement of Actuarial Opinion under American Academy of Actuaries guidelines. ** - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WIX 3.0 release date
Hmmm... http://www.productbeautiful.com/2008/05/02/why-product-management-is-open-sources-fatal-flaw/ Bob Arnson [EMAIL PROTECTED] wrote: Christopher Painter wrote: I know a very good product manager that would probably volunteer. The question is, would the engineers yield the power in an open source environment? What does power have to do with it? -- sig://boB http://joyofsetup.com/ Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a really good thread that deserves attention? E-Mail Me - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WIX 3.0 release date
I don't think people read beta as not functionally complete, I think they read full of bugs. I agree that it is missing some very important features but in my experience what is there is very reliable. I seem to remember v2 going through a few releases where the community was asked whether the current build was a good release candidate and then that one was posted as a release. Neil From: Martin MacPherson [mailto:[EMAIL PROTECTED] Sent: 28 May 2008 17:52 To: Neil Sleightholm Cc: Rob Mensching; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] WIX 3.0 release date I understand the pain of trying to convince managers of anything that isn't in black and white but as far as I can see the Wix code is of beta quality ie..not functionally complete. It would problem be a bit irresponsible to paint it otherwise... Rob, What's the deal for the community getting involved to try and push this along? (Sorry if this has been discussed previously) 2008/5/28 Neil Sleightholm [EMAIL PROTECTED]: I would like to make a suggestion: Could the beta tag on v3 be replaced with something less emotive. I am having problems convincing managers to accept v3 because of the beta tag, I think the code is more than that and has so much more than v2 that is worth adopting. I think if we have to wait for another year before the beta tag is removed it will stop a greater adoption of the code. I would suggest that in the near future (one or two months) it is released as something else. I'm not sure what but copying Microsoft you could use CTP (Community Technology Preview). Neil Neil Sleightholm X2 Systems Limited [EMAIL PROTECTED] -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rob Mensching Sent: 27 May 2008 19:22 To: dB.; Daniel Hughes; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] WIX 3.0 release date Interesting. Let's go back and look at the things that are driving the WiX v3 release. 1. Bugs. WiX v2 was marked stable by pushing a number of bugs to WiX v3 (especially Votive bugs). There are still a lot of bugs open that need to be fixed. I do not just want to push a bunch of WiX v2 bugs to WiX v4. 2. Patching. Patching is hard with MSI and the new tools in WiX v3 can help a lot. Those tools are basically done and we're just running down the bug tail now. 3. Votive. Votive was *very* rough in WiX v2. It had years to go before it was going to truly useable. In WiX v3, Justin and a lot of help from members of the VS team have made Votive far more usable. There are still a lot of bugs to fix and the only reason I think it can be done this year is because of the VS help. Otherwise, I'm quite certain we'd *still* have a very crippled VS story. 4. Bootstrapper. Every other day or so there is another request for chaining/bootstrapping. Some of the solutions out there meet some people's needs but IMHO none of them have all of the features that are needed to meet the majority of bootstrapping needs. This part of the WiX toolset is about 2 years late and I think it is a big mistake to go into 2009 without a useable bootstrap story. 5. DTF. After finally deciding that the MSI team was not going to do it, I asked Jason Ginchereau if he would like to add DTF to WiX v3. This codebase was pretty stable so my expectation was that this wouldn't affect our bug count much. Now let's talk about who's doing all of this work. I'm driving the bug count overall with help from the area owners. Peter Marcu (http://blogs.msdn.com/pmarcu) is driving the patching support backed up by Heath Stewart (http://blogs.msdn.com/heaths). Votive is lead by Justin Rockwood (http://blogs.msdn.com/jrock/) and Jason Ginchereau (http://blogs.msdn.com/jasongin)'s http://blogs.msdn.com/jasongin%29%27s team from VS. The bootstrapper code base is being developed by Fredrik Grohn (http://fredrikgrohn.com) and hopefully will be added to WiX soon. DTF is, of course, Jason's baby. Bob Arnson (http://www.joyofsetup.com) basically helps out everywhere. With the exception of the VS team I would guess that each of those people donate about 10 hours per week to the toolset. There are others but that is the bulk of regular development happening on the WiX toolset. The sheer number of hours available to address bugs is why I think it will take until the end of the year. We could cut the bootstrapper (again) to focus solely on bugs and probably finish WiX v3 sooner but I believe the bootstrapper is more important than that. Plus, this is a volunteer project so it is hard to expect everyone to stay excited about solely fixing bugs for 6+ months. smile/ You should look at what parts of the WiX toolset you depend one when judging stability. If you just want the core toolset (candle, light) then that code base is very stable in v3. Arguably it is more stable than it was in WiX v2 (certainly more bug fixes). Granted v3 can change from build to build so you might pick up a
Re: [WiX-users] Build Wix v3.4123 Issues
Thanks Rob. I was referencing make.bat file. :: :: In order to fully build WiX, you must have the following Frameworks and :: SDKs installed: ::* NAnt version 0.86 beta nightly (2008-02-10-0.86 or later) ::* .NET Framework 2.0, 3.0, and 3.5 ::* Windows SDK for Windows Server 2008 and .NET Framework 3.5 ::* Visual C++ 2008 Express or any edition of Visual Studio 2008 with ::Visual C++ default libraries installed ::* HTML Help SDK 1.4 or higher :: :: To build and install Sconce and Votive, you must have Visual Studio 2008, :: Standard edition or higher) Maybe it should point to the WiX.chm. After I loaded the VS 2008 SDK I was able to get farther, but hit a failure in votive2005 clean. It seems to want VS 2005 SDK. I tried loading it, but it requires VS 2005. I don't have VS 2005 loaded. So, I removed references to votive2005 from the wix.build. This helped, but now it fails on the following; [exec] Build FAILED. [exec] C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Microsoft.Common.targets : warning MSB3088: Could not read sta te file C:\Wix_v3_4123\build\obj\debug\x86\Wix\Wix.csproj.GenerateResource.Cache. Unable to cast object of type 'Micro soft.Build.Tasks.ResGenDependencies' to type 'Microsoft.Build.Tasks.StateFileBase'. [exec] C:\Wix_v3_4123\src\votive\SDK_VS2008\Tools\Build\Microsoft.VsSDK.targets(348,5): error MSB4062: The VsTempl atePaths task could not be loaded from the assembly C:\Wix_v3_4123\src\votive\SDK_VS2008\Tools\Build\Microsoft.VsSDK.Bu ild.Tasks.dll. Could not load file or assembly 'file:///C:\Wix_v3_4123\src\votive\SDK_VS2008\Tools\Build\Microsoft.VsSDK .Build.Tasks.dll' or one of its dependencies. The system cannot find the file specified. Confirm that the UsingTask de claration is correct, and that the assembly and all its dependencies are available. [exec] 1 Warning(s) [exec] 1 Error(s) [exec] [exec] Time Elapsed 00:00:52.76 Did I miss another step? Thanks, Mark From: Rob Mensching [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 28, 2008 11:56 AM To: Kelly Leahy; Eva, Mark E (ESL Lab-Boise) Cc: [EMAIL PROTECTED]; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] Build Wix v3.4123 Issues The WiX.chm Building WiX has the list of external SDKs that you must have installed to build fully. The other issues (besides the paths not being set correctly) are bugs, please do feel free to open them on SourceForge so we are sure to fix them. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kelly Leahy Sent: Wednesday, May 28, 2008 10:37 To: Eva, Mark E (ESL Lab-Boise) Cc: [EMAIL PROTECTED]; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Build Wix v3.4123 Issues http://msdn.microsoft.com/en-us/vsx/default.aspx Not sure if it's what you need, but it wouldn't surprise me. Eva, Mark E (ESL Lab-Boise) [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 05/28/2008 10:33 AM To Kelly Leahy [EMAIL PROTECTED] cc [EMAIL PROTECTED] [EMAIL PROTECTED], wix-users@lists.sourceforge.net wix-users@lists.sourceforge.net Subject Re: [WiX-users] Build Wix v3.4123 Issues I am running VS Team System 2008 Team Suite - ENU I thought it had everything. I will look for the SDK. Thanks, Mark From: Kelly Leahy [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 28, 2008 11:23 AM To: Eva, Mark E (ESL Lab-Boise) Cc: wix-users@lists.sourceforge.net; [EMAIL PROTECTED] Subject: Re: [WiX-users] Build Wix v3.4123 Issues looks like you might be missing VSIP (the visual studio SDK)? Eva, Mark E (ESL Lab-Boise) [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 05/28/2008 10:21 AM To wix-users@lists.sourceforge.net wix-users@lists.sourceforge.net cc Subject [WiX-users] Build Wix v3.4123 Issues [exec] Done building target VsTemplatePathsTarget in project Votive2008.csproj -- FAILED. [exec] [exec] Done building project Votive2008.csproj -- FAILED. [exec] [exec] Build FAILED. See attached details in The following is a list of all issues I have had trying to build Wix. The latest issue #7 is above. I don't have a solution for it as yet. Mark E. Eva - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ** This communication is intended solely for the addressee and is confidential. If you are not the intended
Re: [WiX-users] converting .reg to .wxs in WiX 3.0
I don't think heat can do this but tallow from v2 can:
tallow -reg file.reg file.wxs
The output should work ok in v3 (or WixCop will fix it).
Neil
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Pally
Sandher
Sent: 28 May 2008 18:53
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] converting .reg to .wxs in WiX 3.0
Hi,
I'm using v3.0.4116.0 currently (installing v3.0.4123.0 first thing
tomorrow morning).
I have a problem with the COM registration info heat.exe generates for
one of our executables (not written by me). It doesn't seem to get all
the required entries. The generated code is as follows:
?xml version=1.0 encoding=utf-8?
Wix xmlns=http://schemas.microsoft.com/wix/2006/wi;
Fragment
DirectoryRef Id=appsFolder
Component Id=iesoop
Guid=503CDCB9-669D-4c18-BF30-B1319A127326
File Id=iesoop.exe Name=iesoop.exe KeyPath=yes
Source=..\..\..\bin_release\iesoop.exe
TypeLib Id={7749E01A-8723-476D-905F-E8F97EDF8AF6}
Description=iesoop Type Library Language=0 MajorVersion=4
MinorVersion=0
Interface
Id={22624D71-96AA-4581-AF1B-E58539EB3EC3} Name=_IBridgeEvents
ProxyStubClassId={00020420---C000-0046}
ProxyStubClassId32={00020420---C000-0046} /
Interface
Id={93B8BD76-7C0A-4119-84C7-3FDCF9B7477C} Name=IBridge
ProxyStubClassId={00020424---C000-0046}
ProxyStubClassId32={00020424---C000-0046} /
/TypeLib
/File
RegistryValue Root=HKCR
Key=TypeLib\{7749E01A-8723-476D-905F-E8F97EDF8AF6}\4.0\HELPDIR
Value=[appsFolder] Type=string Action=write /
/Component
/DirectoryRef
/Fragment
/Wix
When I use RegSpy on this app it generates much more than those entries
above. When I install our application it fails to run. If I run the
above executable after installation with the /regserver parameter then
run our application it works fine. This is what leads me to believe
heat.exe is missing some of the self-registration info.
In WiX 2.0, tallow.exe happily took a .reg file output the required
XML, heat.exe in 3.0 refuses to play the game (outputs a fragment with a
directory, component file tag for the .reg file!).
Does anyone know how I can convert the .reg file I've extracted using
RegSpy to WiX 3.0 XML? heat.exe seems to have no documentation at all
other than what it outputs when run with /? I really don't want to have
to use a custom action for this.
Cheers,
http://www.iesve.com/
Palbinder Sandher
Software Deployment and
IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com http://www.iesve.com/
**Design, Simulate + Innovate with the Virtual Environment**
Integrated Environmental Solutions Limited. Registered in Scotland No.
SC151456
Registered Office - Helix Building, West Of Scotland Science Park,
Glasgow G20 0SP
Email Disclaimer http://www.iesve.com/disclaimer.html
image001.jpg-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Build Wix v3.4123 Issues
Yeah, totally forgot all that stuff was in make.bat. As for the build failure, sorry, you're in Votive land and I'm not deeply familiar with all the ins and outs of that. Justin is better able to answer those questions. I thought the build would ignore Votive if you didn't have the VS SDK installed... do you want to build Votive? From: Eva, Mark E (ESL Lab-Boise) [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 28, 2008 13:06 To: Rob Mensching; Kelly Leahy Cc: [EMAIL PROTECTED]; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] Build Wix v3.4123 Issues Thanks Rob. I was referencing make.bat file. :: :: In order to fully build WiX, you must have the following Frameworks and :: SDKs installed: ::* NAnt version 0.86 beta nightly (2008-02-10-0.86 or later) ::* .NET Framework 2.0, 3.0, and 3.5 ::* Windows SDK for Windows Server 2008 and .NET Framework 3.5 ::* Visual C++ 2008 Express or any edition of Visual Studio 2008 with ::Visual C++ default libraries installed ::* HTML Help SDK 1.4 or higher :: :: To build and install Sconce and Votive, you must have Visual Studio 2008, :: Standard edition or higher) Maybe it should point to the WiX.chm. After I loaded the VS 2008 SDK I was able to get farther, but hit a failure in votive2005 clean. It seems to want VS 2005 SDK. I tried loading it, but it requires VS 2005. I don't have VS 2005 loaded. So, I removed references to votive2005 from the wix.build. This helped, but now it fails on the following; [exec] Build FAILED. [exec] C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Microsoft.Common.targets : warning MSB3088: Could not read sta te file C:\Wix_v3_4123\build\obj\debug\x86\Wix\Wix.csproj.GenerateResource.Cache. Unable to cast object of type 'Micro soft.Build.Tasks.ResGenDependencies' to type 'Microsoft.Build.Tasks.StateFileBase'. [exec] C:\Wix_v3_4123\src\votive\SDK_VS2008\Tools\Build\Microsoft.VsSDK.targets(348,5): error MSB4062: The VsTempl atePaths task could not be loaded from the assembly C:\Wix_v3_4123\src\votive\SDK_VS2008\Tools\Build\Microsoft.VsSDK.Bu ild.Tasks.dll. Could not load file or assembly 'file:///C:\Wix_v3_4123\src\votive\SDK_VS2008\Tools\Build\Microsoft.VsSDK .Build.Tasks.dll' or one of its dependencies. The system cannot find the file specified. Confirm that the UsingTask de claration is correct, and that the assembly and all its dependencies are available. [exec] 1 Warning(s) [exec] 1 Error(s) [exec] [exec] Time Elapsed 00:00:52.76 Did I miss another step? Thanks, Mark From: Rob Mensching [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 28, 2008 11:56 AM To: Kelly Leahy; Eva, Mark E (ESL Lab-Boise) Cc: [EMAIL PROTECTED]; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] Build Wix v3.4123 Issues The WiX.chm Building WiX has the list of external SDKs that you must have installed to build fully. The other issues (besides the paths not being set correctly) are bugs, please do feel free to open them on SourceForge so we are sure to fix them. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kelly Leahy Sent: Wednesday, May 28, 2008 10:37 To: Eva, Mark E (ESL Lab-Boise) Cc: [EMAIL PROTECTED]; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Build Wix v3.4123 Issues http://msdn.microsoft.com/en-us/vsx/default.aspx Not sure if it's what you need, but it wouldn't surprise me. Eva, Mark E (ESL Lab-Boise) [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 05/28/2008 10:33 AM To Kelly Leahy [EMAIL PROTECTED] cc [EMAIL PROTECTED] [EMAIL PROTECTED], wix-users@lists.sourceforge.net wix-users@lists.sourceforge.net Subject Re: [WiX-users] Build Wix v3.4123 Issues I am running VS Team System 2008 Team Suite - ENU I thought it had everything. I will look for the SDK. Thanks, Mark From: Kelly Leahy [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 28, 2008 11:23 AM To: Eva, Mark E (ESL Lab-Boise) Cc: wix-users@lists.sourceforge.net; [EMAIL PROTECTED] Subject: Re: [WiX-users] Build Wix v3.4123 Issues looks like you might be missing VSIP (the visual studio SDK)? Eva, Mark E (ESL Lab-Boise) [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 05/28/2008 10:21 AM To wix-users@lists.sourceforge.net wix-users@lists.sourceforge.net cc Subject [WiX-users] Build Wix v3.4123 Issues [exec] Done building target VsTemplatePathsTarget in project Votive2008.csproj -- FAILED. [exec] [exec] Done building project Votive2008.csproj -- FAILED. [exec] [exec] Build FAILED. See attached details in The following is a list of all issues I have had trying to build Wix. The latest issue #7 is above. I don't have a solution for it as yet. Mark E. Eva
Re: [WiX-users] Build Wix v3.4123 Issues
I don't really need Votive at this time. My goal was to look at making an enhancement to Heat. But first I wanted to make sure I would successfully build WiX without any changes. Many days later I am still not there Are you suggesting I remove votive2008 from the wix.build? Thanks, Mark From: Rob Mensching [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 28, 2008 2:32 PM To: Eva, Mark E (ESL Lab-Boise); Kelly Leahy Cc: wix-users@lists.sourceforge.net Subject: RE: [WiX-users] Build Wix v3.4123 Issues Yeah, totally forgot all that stuff was in make.bat. As for the build failure, sorry, you're in Votive land and I'm not deeply familiar with all the ins and outs of that. Justin is better able to answer those questions. I thought the build would ignore Votive if you didn't have the VS SDK installed... do you want to build Votive? From: Eva, Mark E (ESL Lab-Boise) [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 28, 2008 13:06 To: Rob Mensching; Kelly Leahy Cc: [EMAIL PROTECTED]; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] Build Wix v3.4123 Issues Thanks Rob. I was referencing make.bat file. :: :: In order to fully build WiX, you must have the following Frameworks and :: SDKs installed: ::* NAnt version 0.86 beta nightly (2008-02-10-0.86 or later) ::* .NET Framework 2.0, 3.0, and 3.5 ::* Windows SDK for Windows Server 2008 and .NET Framework 3.5 ::* Visual C++ 2008 Express or any edition of Visual Studio 2008 with ::Visual C++ default libraries installed ::* HTML Help SDK 1.4 or higher :: :: To build and install Sconce and Votive, you must have Visual Studio 2008, :: Standard edition or higher) Maybe it should point to the WiX.chm. After I loaded the VS 2008 SDK I was able to get farther, but hit a failure in votive2005 clean. It seems to want VS 2005 SDK. I tried loading it, but it requires VS 2005. I don't have VS 2005 loaded. So, I removed references to votive2005 from the wix.build. This helped, but now it fails on the following; [exec] Build FAILED. [exec] C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Microsoft.Common.targets : warning MSB3088: Could not read sta te file C:\Wix_v3_4123\build\obj\debug\x86\Wix\Wix.csproj.GenerateResource.Cache. Unable to cast object of type 'Micro soft.Build.Tasks.ResGenDependencies' to type 'Microsoft.Build.Tasks.StateFileBase'. [exec] C:\Wix_v3_4123\src\votive\SDK_VS2008\Tools\Build\Microsoft.VsSDK.targets(348,5): error MSB4062: The VsTempl atePaths task could not be loaded from the assembly C:\Wix_v3_4123\src\votive\SDK_VS2008\Tools\Build\Microsoft.VsSDK.Bu ild.Tasks.dll. Could not load file or assembly 'file:///C:\Wix_v3_4123\src\votive\SDK_VS2008\Tools\Build\Microsoft.VsSDK .Build.Tasks.dll' or one of its dependencies. The system cannot find the file specified. Confirm that the UsingTask de claration is correct, and that the assembly and all its dependencies are available. [exec] 1 Warning(s) [exec] 1 Error(s) [exec] [exec] Time Elapsed 00:00:52.76 Did I miss another step? Thanks, Mark From: Rob Mensching [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 28, 2008 11:56 AM To: Kelly Leahy; Eva, Mark E (ESL Lab-Boise) Cc: [EMAIL PROTECTED]; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] Build Wix v3.4123 Issues The WiX.chm Building WiX has the list of external SDKs that you must have installed to build fully. The other issues (besides the paths not being set correctly) are bugs, please do feel free to open them on SourceForge so we are sure to fix them. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kelly Leahy Sent: Wednesday, May 28, 2008 10:37 To: Eva, Mark E (ESL Lab-Boise) Cc: [EMAIL PROTECTED]; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Build Wix v3.4123 Issues http://msdn.microsoft.com/en-us/vsx/default.aspx Not sure if it's what you need, but it wouldn't surprise me. Eva, Mark E (ESL Lab-Boise) [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 05/28/2008 10:33 AM To Kelly Leahy [EMAIL PROTECTED] cc [EMAIL PROTECTED] [EMAIL PROTECTED], wix-users@lists.sourceforge.net wix-users@lists.sourceforge.net Subject Re: [WiX-users] Build Wix v3.4123 Issues I am running VS Team System 2008 Team Suite - ENU I thought it had everything. I will look for the SDK. Thanks, Mark From: Kelly Leahy [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 28, 2008 11:23 AM To: Eva, Mark E (ESL Lab-Boise) Cc: wix-users@lists.sourceforge.net; [EMAIL PROTECTED] Subject: Re: [WiX-users] Build Wix v3.4123 Issues looks like you might be missing VSIP (the visual studio SDK)? Eva, Mark E (ESL Lab-Boise) [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED]
[WiX-users] check memory, cpu, and screen resolution
Hi, I couldn't find any useful information on how to get memory, cpu, and screen resolution in the mailing list so I'm wondering, is it still not supported? Is there any workaround? How do most people do instead given the fact that they are unable to detect such information using Wix? Thanks in advance. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] check memory, cpu, and screen resolution
Uhh, the Windows Installer has all kinds of properties for that type of information. PhysicalMemory, VirtualMemory, Intel, Intel64, Msix64, ScreenX, ScreenY. I recommend reading the MSI SDK. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of YungWei Chen Sent: Wednesday, May 28, 2008 17:09 To: WixUser Subject: [WiX-users] check memory, cpu, and screen resolution Hi, I couldn't find any useful information on how to get memory, cpu, and screen resolution in the mailing list so I'm wondering, is it still not supported? Is there any workaround? How do most people do instead given the fact that they are unable to detect such information using Wix? Thanks in advance. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] check memory, cpu, and screen resolution
Have you tried the following properties: - PhysicalMemory (http://msdn.microsoft.com/en-us/library/aa370818(VS.85).aspx) - VirtualMemory (http://msdn.microsoft.com/en-us/library/aa372520(VS.85).aspx) - Intel (http://msdn.microsoft.com/en-us/library/aa369552(VS.85).aspx) - Intel64 (http://msdn.microsoft.com/en-us/library/aa369553(VS.85).aspx) - Msix64 (http://msdn.microsoft.com/en-us/library/aa370522(VS.85).aspx) - ScreenX (http://msdn.microsoft.com/en-us/library/aa371529(VS.85).aspx) - ScreenY (http://msdn.microsoft.com/en-us/library/aa371533(VS.85).aspx) From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of YungWei Chen Sent: Wednesday, May 28, 2008 5:09 PM To: WixUser Subject: [WiX-users] check memory, cpu, and screen resolution Hi, I couldn't find any useful information on how to get memory, cpu, and screen resolution in the mailing list so I'm wondering, is it still not supported? Is there any workaround? How do most people do instead given the fact that they are unable to detect such information using Wix? Thanks in advance. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] FileSharePermission and Permission
Hi, A newbie's stupid question. What is the difference between FileSharePermission and Permission? Could someone please explain the exact meaning of the following code? Directory Id='d_Temp' Name='Temp'Component Id='c_Temp' Guid='GUID'CreateFolder Permission User='Networkservice' GenericAll='yes' / /CreateFolder util:FileShare Id='Temp' Name='Temp' Description='[DESCRIPTION]'util:FileSharePermission User='Networkservice' GenericAll='yes'/ /util:FileShare /Component/Directory Thanks, Zhisheng _ Change the world with e-mail. Join the i’m Initiative from Microsoft. http://im.live.com/Messenger/IM/Join/Default.aspx?source=EML_WL_ChangeWorld- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] FileSharePermission and Permission
zhisheng huang wrote: A newbie's stupid question. What is the difference between FileSharePermission and Permission? Could someone please explain the exact meaning of the following code? Permission manages the NTFS security for the folder (Security tab in Explorer); FileSharePermission manages the permissions on the share (Permissions button in the Sharing tab). -- sig://boB http://joyofsetup.com/ - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WIX 3.0 release date
Christopher Painter wrote: Hmmm... http://www.productbeautiful.com/2008/05/02/why-product-management-is-open-sources-fatal-flaw/ My question stands: What does power have to do with it? Product/project/program management isn't about wielding authority, it's about building consensus. -- sig://boB http://joyofsetup.com/ - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] how to configure application pool to run as integrated mode with WIX iis extension
Could anyone help? Looks like the application pool can only be created in classic mode. thanks, Zhisheng From: [EMAIL PROTECTED]: [EMAIL PROTECTED]: how to configure application pool to run as integrated mode with WIX iis extensionDate: Tue, 27 May 2008 16:19:17 -0400 Hi, how to configure application pool to run as integrated mode with WIX iis extension?I look at the wix help file and search web, but still have no idea yet. Thanks for help!Zhisheng E-mail for the greater good. Join the i’m Initiative from Microsoft. _ Make every e-mail and IM count. Join the i’m Initiative from Microsoft. http://im.live.com/Messenger/IM/Join/Default.aspx?source=EML_WL_ MakeCount- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WIX 3.0 release date
Christopher, Perhaps you could put together your list of 'best case' requirements for a bootstrapper? It seems like building one isn't going to be that difficult, but it also seems that the project is starved of good requirements and direction around the bootstrapper. Once there's a good list of 'this is what it has to do', people can start to hack away at what's the most important of those features... Of course, I'm just an outsider, it just seemed to me that since you have the knowledge, if you could dedicate a few minutes to come up with a list, people may be able to run with it. I'd offer to make such a list myself, but I've got nothing near the experience you have in Deployment Engineering. I do have the C++ skills and would be happy to help out if somebody could help me get 'into' it. The problem I've had so far is that I don't really have a good feel for the problems being solved (and there's not a really good doc on how to get started contributing - i.e. how to get the build environment up and working, etc.). To me, the bootstrapper is a good point to get in, since it shouldn't be tightly integrated to the WiX codebase and as such shouldn't be too difficult to get it up and building... Kelly Christopher Painter [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 05/27/2008 06:27 PM To Rob Mensching [EMAIL PROTECTED], dB. [EMAIL PROTECTED], Daniel Hughes [EMAIL PROTECTED], wix-users@lists.sourceforge.net wix-users@lists.sourceforge.net cc Subject Re: [WiX-users] WIX 3.0 release date I've often thought about creating and marketing my own bootstrapper product. I know the stories and requirements inside out as I've done serviced product lines with vastly more complex prereq requirements then vs and office. The problem is I could only write in in C# as my C++ skills suck. WiX is a lot close to mass adoption then even Rob knows. A solid bootstrapper and a full featured designer exposing the majority of WiX capabilities along with a sprinkling of custom actions would work miracles in terms of adoption. Rob Mensching [EMAIL PROTECTED] wrote: Fair. Of course, I don't think we should be looking to take over the world with the WiX toolset (we probably need more people answering questions and improving the overall documentation before getting thousands and thousands more users ) but I'm always open to suggestions about what we should do. What do other people think about purely fixing the bugs in the WiX toolset and adding no more functionality? That means there will be no bootstrapper in WiX v3 and no improvement to the IIS CustomActions to better handle IIS7. Basically, imagine the WiX v3 toolset functionality of today plus fixing ~150 bugs. Thoughts? -Original Message- From: dB. [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 27, 2008 12:44 To: Rob Mensching; Daniel Hughes; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] WIX 3.0 release date Rob, I think you completely nailed it when you say We could cut the bootstrapper (again) to focus solely on bugs and probably finish WiX v3 sooner but I believe the bootstrapper is more important than that. This is a typical dilemma of any software project. If Wix cost 100$ you could make 100'000$ by the end of the year if you were to ship in October. Or you could delay that revenue into 2009 with the risk of losing market share (people using InstallShield, etc.). I fought several arguments where people were trying to use wix 2.0 + very nasty custom actions vs. wix 3.0 with built-in extensions just because wix 3.0 hasn't shipped yet. I bet many people are having similar arguments in the real world. cheers -dB. -Original Message- From: Rob Mensching [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 27, 2008 2:22 PM To: dB.; Daniel Hughes; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] WIX 3.0 release date Interesting. Let's go back and look at the things that are driving the WiX v3 release. 1. Bugs. WiX v2 was marked stable by pushing a number of bugs to WiX v3 (especially Votive bugs). There are still a lot of bugs open that need to be fixed. I do not just want to push a bunch of WiX v2 bugs to WiX v4. 2. Patching. Patching is hard with MSI and the new tools in WiX v3 can help a lot. Those tools are basically done and we're just running down the bug tail now. 3. Votive. Votive was *very* rough in WiX v2. It had years to go before it was going to truly useable. In WiX v3, Justin and a lot of help from members of the VS team have made Votive far more usable. There are still a lot of bugs to fix and the only reason I think it can be done this year is because of the VS help. Otherwise, I'm quite certain we'd *still* have a very crippled VS story. 4. Bootstrapper. Every other day or so there is another request for chaining/bootstrapping. Some of the solutions out there meet some people's needs but IMHO none of them have all of the features that are needed to meet the majority of
[WiX-users] Пожем с Ипотекой
Срочная помощь в получении ипотечного кредита. Помогаем оформить документы для ипотеки. Подобрать , проверить и оформить квартиру, новостройку, коттедж. 1750-банков Москвы. Оптимальные и выгодные условия ипотеки для Вас. Телефон: Семь Восемь Восемь - Семь Восемь - Семь Шесть с 9-30 до 21-30 без выходных.- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Create EXE wrapper around my MSI?
Kelly Leahy [EMAIL PROTECTED] writes: It sounds like your registration is happening in the wrong 'stage' of the install... Just because you're elevated in some places, it doesn't mean the entire run of the install is elevated. I think the elevation only occurs during the installexecutesequence, and only during the server side part of it, and maybe not even the whole thing. I'm sure this comment isn't all that helpful, but maybe it will point you in the right direction. Can you actually tell where the registration is sequenced? Please do not take this as a personal critique. You wrote I think So that means you are not sure, which is fine but the answers here are often I think that means to me the whole not I'm getting personal crap of MSI was just invented to make programmers live as hard as possible. There is a whole sorry (brain-dead) machinery needed to get something installed and it's even worse if one get's into the COM or even worse device installation area. Just how many tools do exist for building installers? What the hell do we gain with such complex installation voodo? Regards Friedrich - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] custom action
I have written vb script in which i set value to session property .But i dont get that value in wxs file what could be the reson do i need to first create this session property in wxs file ? - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Installing driver when the installer files includesubdirectories
Richard, Just create normal components for the two subdirectories, and a third component just containing the INF file and the difx attributes, and then add all three to the same feature. I think that the difx stuff only has to be attached to the INF file. Regards, John _ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Richard Amos Sent: 27 May 2008 18:59 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Installing driver when the installer files includesubdirectories I've been using the difx:Driver tag to installer a scanner driver - got that working OK. Now I'd like to installer a printer driver using the same technology. The problem is that when I unzip the printer install files it has two subdirectories under the root directory (containing the INF file). These subdirectories are i386 and AMD64. Given that a driver is a single component, and a component can't contain subdirectories, how do I go about installing this printer driver? _ Sent from Yahoo! Mail http://us.rd.yahoo.com/mailuk/taglines/isp/control/*http://us.rd.yahoo. com/evt=52418/*http://uk.docs.yahoo.com/nowyoucan.html . A Smarter Email. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Create EXE wrapper around my MSI?
Hrm, I didn't think that was the case, but I am using a custom UI and thought maybe I was somehow screwing up the timing with that. To be safe I switched to WixUI_Minimal UI and tried things out. Still no luck. I've become so upset over the whole thing that I spent the evening rewriting the core part of my installer with NSIS instead of WiX. And guess what, I get the EXACT same behavior! (DLL registers correctly when UAC is disabled, but not if the user has to allow elevated permissions). I have NO idea how to fix this, apparently I've messed up something good. :( I think I'm going to attempt to automatically cancel the install if the user is running the UAC. This is a terrible, terrible solution but I don't know where else to turn... Colin Kelly Leahy wrote: It sounds like your registration is happening in the wrong 'stage' of the install... Just because you're elevated in some places, it doesn't mean the entire run of the install is elevated. I think the elevation only occurs during the installexecutesequence, and only during the server side part of it, and maybe not even the whole thing. I'm sure this comment isn't all that helpful, but maybe it will point you in the right direction. Can you actually tell where the registration is sequenced? Kelly *Colin Bleckner [EMAIL PROTECTED]* Sent by: [EMAIL PROTECTED] 05/27/2008 05:04 PM To Neil Enns [EMAIL PROTECTED] cc [EMAIL PROTECTED] [EMAIL PROTECTED], Kelly Leahy [EMAIL PROTECTED], wix-users@lists.sourceforge.net wix-users@lists.sourceforge.net Subject Re: [WiX-users] Create EXE wrapper around my MSI? I was finally able to wrap my MSI with an EXE installer and run my installer with elevated permissions. And, of course, my installer still fails to register my DLL correctly (I guess that's what I get for trying to avoid the root problem...). Anyone have any ideas how a DLL can register correctly when UAC is disabled but fail when running with elevated permissions? Is there a difference between running with UAC disabled and running with elevated permissions? Colin Colin Bleckner wrote: Ah, I've never heard of iexpress. Seems simple and pretty much perfect, except that it doesn't seem to recognize an MSI file as a valid file to run as the Install Program entry. My MSI doesn't show up in the dropdown list and typing the name manually ends up with an error during the actual install (I also tried call MyFile.msi as the Install Program, but no such luck). Has anyone triggered an MSI file from iexpress before? I guess I could attempt to figure out where it unpacks the files and hardcode that path into my Install Program line, but that sounds like a terrible idea... :) Colin Neil Enns wrote: Did you try looking at iexpress? I've never used it, but John suggested it last week for building a wrapper exe. Just open a cmd window and type iexpress for the wizard. Neil *From:* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]] On Behalf Of Kelly Leahy [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]]* Sent:* Tuesday, May 27, 2008 12:11 PM* To:* Colin Bleckner* Cc:* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]; [EMAIL PROTECTED] mailto:wix-users@lists.sourceforge.net* Subject:* Re: [WiX-users] Create EXE wrapper around my MSI? Hehehe... just got done blogging about how to make a single-.EXE package with .NET yesterday. The methodology I used can be used for both managed and unmanaged projects (although it's admittedly much easier for managed projects). It may help a little, though its not exactly what you're looking for. _ __http://kleahy-technical.blogspot.com_ http://kleahy-technical.blogspot.com/ Kelly *Colin Bleckner **_[EMAIL PROTECTED]_* mailto:[EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] 05/27/2008 12:06 PM To _wix-users@lists.sourceforge.net_ mailto:wix-users@lists.sourceforge.net _wix-users@lists.sourceforge.net_ mailto:wix-users@lists.sourceforge.net cc Subject [WiX-users] Create EXE wrapper around my MSI? I know this is a total cop out, but I don't know how else to deal with my Vista UAC issues right now. :( People have mentioned that one way around some of the issues is to create an EXE wrapper that requests elevated permissions and then runs my MSI. Is this easy to create? I'd like to try that out but I'm not sure where to start. Colin - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008._ __http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/_ ___ WiX-users mailing list_ [EMAIL PROTECTED] mailto:WiX-users@lists.sourceforge.net_
[WiX-users] Претензии потребителей - новая редакция
ЗАКОН О ЗАЩИТЕ ПРАВ ПОТРЕБИТЕЛЯ: (применение в интересах компаний-ответчиков, против потребителя) Семинар-практикyм. 4-5 июня 2008 г., Москва Тел.: 925-8871 Законодательство РФ всегда было на стороне потребителей. Поправки от 25 октября 07г. сделали потребителя еще более всемогущим. - Как юридически грамотно противостоять необоснованным претензиям потребителя? - Как минимизировать потери времени, денег и нервов при разборе претензий? - Как определить в конкретной ситуации: доводить ли до суда или выгоднее договориться с покупателем на мировую? - Какие превентивные меры позволят предупредить наиболее распространенные виды злоупотреблений потребителем своих прав? Семинар изобилует примерами из практики. В процессе рассмотрения каждого блока программы (будь то продажа товаров по образцам, срок гарантии, оказание услуг с договором смешанного типа, возврат/обмен товара ненадлежащего качества и т.д.) каждый участник может поднять на обсуждение актуальную для него ситуацию и получить квалифицированную консультацию ведущего. В программе: 1. Требования ЗоЗПП и практика его применения, с учетом актуальных изменений от 25.10.07 - Предоставление потребителю информации: - Продажа товара и выполнение работ/ услуг: - Потребительский экстремизм: признаки; профилактика; ошибки; практика. 2. Дистанционный способ продажи товаров. 3. ГК РФ - Розничная купля-продажа товаров - Услуги/работы - Совместное применение ГК РФ и ЗоПП. 4. Постановления Правительства РФ, иные акты 5. Ответственность за нарушения законодательства 6. Судебная практика - Практика Верховного суда РФ. - Практика по рассмотрению судами дел по ЗоЗПП: обращение потребителя в суд (статистика); отношение судей к потребительским спорам/работа с судьями; моральный вред; решение/заочное решение; исполнительное производство. Инофрмация о ведущем: Практикующий юрист. С 1997 по 2001: юрист в Международной конфедерации обществ потребителей (КонфОП). Юридический консультант. С 2002 - настоящее время: ведущий юрист в компании, выступающей на стороне ответчиков (против потребителя). Имеет большой опыт практической, судебной работы. Ведет авторский семинар с 2004 г. Более подробная программа и резюме ведущего высылается по Вашему запросу. Стоимость участия в двухдневном семинаре: 15200 руб./чел. (вкл. НДС). - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Стили управления. Выработка ли чного стиля
nbsp; Эффективное управление: постановка задач, организация и контроль исполнения 17-18 июня 2008 г., Москва Наши телефоны: (495) 50-девять-21-три-9 и 509-216-один nbsp; nbsp; Целевая аудитория: Тренинг предназначен для руководителей всех уровней, которые хотят овладеть основными навыками превращения коллектива в команду единомышленников. В ходе проведения деловых игр, групповых дискуссий и выполнения индивидуальных заданий вы научитесь планировать работу коллектива на перспективу, освоите технику постановки и контроля задач для коллектива, его мобилизации на разрешение сложных ситуаций. Об авторе: Бизнес-тренер с многолетним опытом работы, консультант, автор тренингов по повышению личной эффективности, менеджменту, продажам. Имеет многочисленные публикации по тематике тренинга. В программе:nbsp; Постановка задач, организация и контроль их исполнения Мотивация сотрудников Межличностное общение и его проблемы Корпоративная культура как инструмент управления. Формирование команды Облик руководителя Разрешение конфликтов с сотрудниками Разрешение конфликтов с клиентами Стоимость участия в семинаре: 18.500 руб., НДС не облагается согласно главы 26.2 Налогового кодекса РФ. Выдаваемый документ Сертификат о повышении квалификации установленного образца nbsp;
Re: [WiX-users] Trouble using CloseApplication CA
That may not be a custom action problem at all. I regularly run VS as admin under Vista and you can't even drag a file from the desktop and drop it in to VS as it blocks you. I think these processes are protected under Vista so that they are not easily exploitable by trojans trying to escalate privileges. There must be a way to detect it though. Ryan From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kiran Subhedar (Sogeti) Sent: 28 May 2008 02:11 To: Bob Arnson Cc: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Trouble using CloseApplication CA Hi Bob, So I figured out why this one is failing and the reason is a bit weird. So if I open VS as an administrator, then the MSI does not detect the VS instance else if I open VS by simply clicking the VS link in Programs, the MSI does detect VS. I am executing the MSI on Vista. I think this is the case with only Vista. With all other OS the MSI works just fine and detects the instances of VS. Anyways thanks for the help! Thanks, Kiran From: Kiran Subhedar (Sogeti) Sent: Tuesday, May 27, 2008 12:15 PM To: 'Bob Arnson' Cc: wix-users@lists.sourceforge.net Subject: RE: [WiX-users] Trouble using CloseApplication CA Hi Bob, I am afraid but the log shows that the CA ran successfully, although it doesn't touch the property. Whereas this works with all the other application exes. Wonder why it doesn't work for VS exe. Any clues? Thanks, Kiran From: Bob Arnson [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 27, 2008 11:29 AM To: Kiran Subhedar (Sogeti) Cc: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Trouble using CloseApplication CA Kiran Subhedar (Sogeti) wrote: I am trying to use the 'CloseApplication' CA to avoid installation if any instances of Visual Studio are running. The action does not work properly and the installation continues even if VS is open. I tested the CA by specifying 'notepad.exe' as the target and it works as expected. How come the CA couldn't trace down the VS process? Am I doing anything wrong here? Looks right. Check a verbose log to see if the CA is running correctly and if the property's being touched. -- sig://boB http://joyofsetup.com/ No virus found in this incoming message. Checked by AVG. Version: 8.0.100 / Virus Database: 269.24.1/1469 - Release Date: 27/05/2008 13:25 - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Потребительский экстремизм
ЗАКОН О ЗАЩИТЕ ПРАВ ПОТРЕБИТЕЛЯ: (применение в интересах компаний-ответчиков, против потребителя) Семинар-практикyм. 4-5 июня 2008 г., Москва Тел.: 925-8871 Законодательство РФ всегда было на стороне потребителей. Поправки от 25 октября 07г. сделали потребителя еще более всемогущим. - Как юридически грамотно противостоять необоснованным претензиям потребителя? - Как минимизировать потери времени, денег и нервов при разборе претензий? - Как определить в конкретной ситуации: доводить ли до суда или выгоднее договориться с покупателем на мировую? - Какие превентивные меры позволят предупредить наиболее распространенные виды злоупотреблений потребителем своих прав? Семинар изобилует примерами из практики. В процессе рассмотрения каждого блока программы (будь то продажа товаров по образцам, срок гарантии, оказание услуг с договором смешанного типа, возврат/обмен товара ненадлежащего качества и т.д.) каждый участник может поднять на обсуждение актуальную для него ситуацию и получить квалифицированную консультацию ведущего. В программе: 1. Требования ЗоЗПП и практика его применения, с учетом актуальных изменений от 25.10.07 - Предоставление потребителю информации: - Продажа товара и выполнение работ/ услуг: - Потребительский экстремизм: признаки; профилактика; ошибки; практика. 2. Дистанционный способ продажи товаров. 3. ГК РФ - Розничная купля-продажа товаров - Услуги/работы - Совместное применение ГК РФ и ЗоПП. 4. Постановления Правительства РФ, иные акты 5. Ответственность за нарушения законодательства 6. Судебная практика - Практика Верховного суда РФ. - Практика по рассмотрению судами дел по ЗоЗПП: обращение потребителя в суд (статистика); отношение судей к потребительским спорам/работа с судьями; моральный вред; решение/заочное решение; исполнительное производство. Инофрмация о ведущем: Практикующий юрист. С 1997 по 2001: юрист в Международной конфедерации обществ потребителей (КонфОП). Юридический консультант. С 2002 - настоящее время: ведущий юрист в компании, выступающей на стороне ответчиков (против потребителя). Имеет большой опыт практической, судебной работы. Ведет авторский семинар с 2004 г. Более подробная программа и резюме ведущего высылается по Вашему запросу. Стоимость участия в двухдневном семинаре: 15200 руб./чел. (вкл. НДС). - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] wix 3.0.4123 custom action templates
Jason Ginchereau wrote: The templates were installed properly, but I think I know the problem: the .vstemplate files are marked with a version that is too new for VS2005 to recognize. They need to be version 2.0.0. Can you try this... In notepad, VS, or any text editor, open each of the .vstemplate files in the Program Files\Microsoft Visual Studio 2005\Common7\IDE\ProjectTemplatesCache\WiX\CustomAction*.zip\ directories, and change line 2 from VSTemplate Version=3.0.0 to VSTemplate Version=2.0.0 Note since you're only changing the cache, those template files will get overwritten next time 'devenv /setup' gets run. For a more permanent solution, you can update those files in the zip files under Common7\IDE\ProjectTemplates\WiX. (Or wait for the next build where I'll fix this bug!) That's my way getting the templates working: System WinXP, VS2005, .Net 2.0 only (no 3.0 or 3.5) 1. Changing the version to 2.0.0 in zip files under Microsoft Visual Studio 8\Common7\IDE\ProjectTemplates\WiX\ 2. running devenv.exe /setup - Templeates showed up. 3. removing all $targetframeworkversion$ occurrences from - customaction.vbproj - customaction.csproj - customaction.cs 4. changed MSBuildToolsPath to MSBuildBinPath 3 and 4 were done in TemplatesCache, but could be also done in zip files. I think the best way to handle the templates should be to provide two separate sets for VS2005 and 2008. I think using Version 2.0.0 indicates that the $targetframeworkversion$ variable could not be handled correctly. So this will be a inconsistency. hth Dominik -- View this message in context: http://www.nabble.com/wix-3.0.4123-custom-action-templates-tp17478662p17509128.html Sent from the wix-users mailing list archive at Nabble.com. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] My installer ate my file
John, You're right light.exe replaces the default version, I just checked my msi with orca and found the 'old' version number there. At the time I made this change I also fixed something in the setup so it always does a major upgrade, that probably solved my problem. Good luck, Valentijn Makkenze Vicrea Solutions B.V. Postbus 1489 3800 BL Amersfoort tel: 033-4604080 fax: 033-4604088 gsm: 06-29011926 www.vicrea.nl -Original Message- From: John Hatton [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 28, 2008 10:41 AM To: Valentijn Makkenze Subject: Re: [WiX-users] My installer ate my file Valentijn, Thanks for the pointer. Unfortunately, setting DefaultVersion to 9.9.9 didn't seem to have any effect. Maybe I screwed up, but I'm having trouble getting any useful documentation on this attribute. The wix docs just say This is the default version of this file. The linker will replace this value from the value in the file if the suppress files option is not used. This is confusing to me. Replace this... from... that? If it said replace the value in the file with this value, that would at least make grammatical sense. If default means if the file is missing a version number, this will used, that would make sense, too. I would guess that was the intended meaning. But if so, that's not going to help me, because all the assemblies I work with are versioned already. In a 2003 blog post, Rob wrote: Of course, you can override that rule ... and force all the files in a Component to get installed even if some of the files exist with newer versions... but then didn't describe how. This was perhaps written in the days where it was less common to just install all the pieces you need for a product in its own directory, avoiding dll hell. Now, it seems to me, most simple apps, installing stuff only to their own directly, would want exactly this behavoir. Do you think DefaultVersion should have worked? Other ideas? Thanks John - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WIX 3.0 release date
I know a very good product manager that would probably volunteer. The question is, would the engineers yield the power in an open source environment? Bob Arnson [EMAIL PROTECTED] wrote: dB. wrote: You all speak like a bunch of engineers :) There are rarely enough program managers on open-source projects.g -- sig://boB http://joyofsetup.com/ Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a really good thread that deserves attention? E-Mail Me - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] service fail to install due to networkServiceaccount
Try this: Account=NT AUTHORITY\NetworkService Complete example that works on my machine (tm): ServiceInstall Id=ServiceEXE Name=$(var.ApplicationFullName) DisplayName=$(var.ApplicationFullName) Type=ownProcess Interactive=no Start=auto Account=NT AUTHORITY\NetworkService Vital=yes ErrorControl=normal/ ServiceControl Id=ServiceEXE Name=$(var.ApplicationFullName) Start=install Stop=both Remove=uninstall Wait=yes/ If you need to set additional disk access permissions, check out util:PermissionEx ... /Mathias From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ryan Perlman Sent: den 28 maj 2008 05:08 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] service fail to install due to networkServiceaccount To All, So when I attempted to do this in my service install element I am still getting the Failed because of required permissions. Would it be possible to see a complete snippet of this being used? My ServiceInstall Element is nested under a Component element with a File element whose keypath is set to yes. If I take out the Account attribute all is fine and the service is installed as 'Local System', if I leave the Account and Password attributes and use a created Service Account all is good and the service is installed. All of these configurations for 'Network Service' have failed though: ServiceInstall Id=MyServiceInstall Name=MyService Description=My Description DisplayName=Transaction Service Host Interactive=no Account=[ComputerName]\Network Service Vital=yes ErrorControl=normal Start=auto Type=ownProcess / ServiceControl Id=MyServiceControl Name=MyService Remove=uninstall Stop=both Wait=yes / ServiceInstall Id=MyServiceInstall Name=MyService Description=My Description DisplayName=Transaction Service Host Interactive=no Account=[ComputerName]\NetworkService Vital=yes ErrorControl=normal Start=auto Type=ownProcess / ServiceControl Id=MyServiceControl Name=MyService Remove=uninstall Stop=both Wait=yes / ServiceInstall Id=MyServiceInstall Name=MyService Description=My Description DisplayName=Transaction Service Host Interactive=no Account=NetworkService Vital=yes ErrorControl=normal Start=auto Type=ownProcess / ServiceControl Id=MyServiceControl Name=MyService Remove=uninstall Stop=both Wait=yes / Thanks, Ryan Solved. The network service account needs to be specified with its domain. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] отдых в Геленжике
ОТДЫХ, ПУТЕВКИ НА ЧЕРНОМ МОРЕприглашаем к сотрудничеству всех кто, заинтересован в приобретении путевок, оздоровлении, реабилитации и лечении на Черноморском побережье Краснодарского края.(495) 504-99-38; (918) 007-18-73 Предлагаем путевки в самые любимые и престижные санатории, пансионаты, коттеджи, отели Красная поляна Адлер Сочи Лазаревское Анапа Геленджик Абхазия КМВ Организация и проведение семинаров, конференций, спортивных сборов, корпоративных вечеринок. Для предприятий любой формы собственности, организаций, страховых компаний по программе ДМС и.т.д., в период летнего сезона 2008, предлагаются пакеты путевок, для детей и взрослых, где ценовая политика предполагает согласование цен. Олимпийский Сочи ждет гостей!(495) 504-99-38; (918) 007-18-73 - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Как отказать в возврате товара ?
ЗАКОН О ЗАЩИТЕ ПРАВ ПОТРЕБИТЕЛЯ: (применение в интересах компаний-ответчиков, против потребителя) Семинар-практикyм. 4-5 июня 2008 г., Москва Тел.: 925-8871 Законодательство РФ всегда было на стороне потребителей. Поправки от 25 октября 07г. сделали потребителя еще более всемогущим. - Как юридически грамотно противостоять необоснованным претензиям потребителя? - Как минимизировать потери времени, денег и нервов при разборе претензий? - Как определить в конкретной ситуации: доводить ли до суда или выгоднее договориться с покупателем на мировую? - Какие превентивные меры позволят предупредить наиболее распространенные виды злоупотреблений потребителем своих прав? Семинар изобилует примерами из практики. В процессе рассмотрения каждого блока программы (будь то продажа товаров по образцам, срок гарантии, оказание услуг с договором смешанного типа, возврат/обмен товара ненадлежащего качества и т.д.) каждый участник может поднять на обсуждение актуальную для него ситуацию и получить квалифицированную консультацию ведущего. В программе: 1. Требования ЗоЗПП и практика его применения, с учетом актуальных изменений от 25.10.07 - Предоставление потребителю информации: - Продажа товара и выполнение работ/ услуг: - Потребительский экстремизм: признаки; профилактика; ошибки; практика. 2. Дистанционный способ продажи товаров. 3. ГК РФ - Розничная купля-продажа товаров - Услуги/работы - Совместное применение ГК РФ и ЗоПП. 4. Постановления Правительства РФ, иные акты 5. Ответственность за нарушения законодательства 6. Судебная практика - Практика Верховного суда РФ. - Практика по рассмотрению судами дел по ЗоЗПП: обращение потребителя в суд (статистика); отношение судей к потребительским спорам/работа с судьями; моральный вред; решение/заочное решение; исполнительное производство. Инофрмация о ведущем: Практикующий юрист. С 1997 по 2001: юрист в Международной конфедерации обществ потребителей (КонфОП). Юридический консультант. С 2002 - настоящее время: ведущий юрист в компании, выступающей на стороне ответчиков (против потребителя). Имеет большой опыт практической, судебной работы. Ведет авторский семинар с 2004 г. Более подробная программа и резюме ведущего высылается по Вашему запросу. Стоимость участия в двухдневном семинаре: 15200 руб./чел. (вкл. НДС). - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] 3.0.4123.0 wix_x64.msi install - Votive does not properly detect when source files have changed
Yesterday I noticed this also happened once with my x86 installation as well. However, after closing the solution and reopening it was picking up my changes again. It happened consistently with the x64 MSI, though. On Tue, May 27, 2008 at 10:07 AM, Jason Ginchereau [EMAIL PROTECTED] wrote: Note that there's very little difference between then the x86 MSI and the x64 MSI: just a few extra files installed under ProgramFiles64\MSBuild. Those extra files are not used by Votive builds, so there must be some other explanation. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Andy Kwak Sent: Monday, May 26, 2008 7:58 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] 3.0.4123.0 wix_x64.msi install - Votive does not properly detect when source files have changed I installed build 3.0.4123.0 and opened my wix solution. When I build my solution the first time, everything is fine. However, when I change any of the source files and try to build the project again, it does not rebuild the project at all. I have to close the solution and reopen it to get it to build anything after making any changes. I tried the regular wix.msi and it works fine, so it seems to only be an issue with the wix_x64 install. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WIX 3.0 release date
For what it's worth, I can only echo the comments of those who support the idea of including the bootstrapper framework before declaring WiX v3 released. I'm very much a novice at installation development, though wix-users has been an incredible resource for me to ramp up my personal knowledge base. It was through wix-users that I learned I was going to need a bootstrapper in the first place. My personal installer needs include two big items to be able to port our current installer to an MSI-based installer. The first, managed code custom actions, has been added with the inclusion of Jason's DTF. The second is the ability to create a bootstrapper that can integrate the installation of prerequisite packages with a complete, unified UI experience. As prereqs, it needs to support installing the .NET framework, VSTO-created Office Add-Ins, and optionally SQL Server Express. It should also allow the option of a silent or unattended install, which lets out the Visual Studio deployment package bootstrapper. Like Joel, I don't look forward to writing the bootstrapper from scratch, so I'm really hoping for the inclusion of a bootstrapper in WiX. As an aside, does the design of Fredrik's bootstrapper framework meet my needs? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rob Mensching Sent: Tuesday, May 27, 2008 4:15 PM To: Peterson, Joel; dB.; Daniel Hughes; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] WIX 3.0 release date Joel, the experience you describe is what I've heard regularly enough to believe that WiX v3 needs a bootstrapper. The bootstrapper framework you ask for only needs time to develop. The design is basically squared away and we've been fortunate to have input from all of those teams you listed in verifying the design. Unfortunately, their code was tightly integrated into their processes and available for use in WiX. So we're taking the data from them and Fredrik is building his bootstrapper with the idea of contributing it to the WiX toolset. I'm expecting end of June it'll show up... then bug fixes and additional feature requests go from there. -Original Message- From: Peterson, Joel [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 27, 2008 13:07 To: Rob Mensching; dB.; Daniel Hughes; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] WIX 3.0 release date We -- those who are currently developing with WiX, those who are stuck in purgatory with Windows Installer but InstallShield's interpretation of it, and those who will be writing an installer in the near future -- are in dire need of a decent bootstrapper. I see shining examples of good bootstrappers (Office 2007, SQL 2005, Visual Studio 2008), but there are no frameworks available that make that development process as easy as it should be. It's held back my adoption of WiX for most projects, and I do not look forward to writing a bootstrapper with one of the very limited tools that are out there. If I had to spend $100 on WiX v3 features, $80-$90 would go into a bootstrapper framework, but maybe I want too much. Is the feature set shown in the bootstrappers I listed just too difficult to roll into a decent framework? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rob Mensching Sent: Tuesday, May 27, 2008 12:50 PM To: dB.; Daniel Hughes; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] WIX 3.0 release date Fair. Of course, I don't think we should be looking to take over the world with the WiX toolset (we probably need more people answering questions and improving the overall documentation before getting thousands and thousands more users smile/) but I'm always open to suggestions about what we should do. What do other people think about purely fixing the bugs in the WiX toolset and adding no more functionality? That means there will be no bootstrapper in WiX v3 and no improvement to the IIS CustomActions to better handle IIS7. Basically, imagine the WiX v3 toolset functionality of today plus fixing ~150 bugs. Thoughts? -Original Message- From: dB. [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 27, 2008 12:44 To: Rob Mensching; Daniel Hughes; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] WIX 3.0 release date Rob, I think you completely nailed it when you say We could cut the bootstrapper (again) to focus solely on bugs and probably finish WiX v3 sooner but I believe the bootstrapper is more important than that. This is a typical dilemma of any software project. If Wix cost 100$ you could make 100'000$ by the end of the year if you were to ship in October. Or you could delay that revenue into 2009 with the risk of losing market share (people using InstallShield, etc.). I fought several arguments where people were trying to use wix 2.0 + very nasty custom actions vs. wix 3.0 with built-in extensions just because wix 3.0 hasn't shipped yet. I bet many people are having similar arguments in the
Re: [WiX-users] Create EXE wrapper around my MSI?
Friedrich, I understand your pain, but I'm not a member of the WiX team, I'm not an employee of MS, and I have no involvement with the MSI team, so I'm basically on the same side of the 'problem' as you are. To be totally honest, I haven't found an installation tool I like YET. The thing I do like about WiX is that everything is basically open-box. It's like working with assembly language - if you can't figure out how to do something, it just means one of two things - it isn't possible (at all) or you just don't know enough... I prefer that to 'I think it's possible, but the stupid tool won't let me do it'. Kelly Friedrich Dominicus [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 05/28/2008 12:05 AM To Kelly Leahy [EMAIL PROTECTED] cc Neil Enns [EMAIL PROTECTED], [EMAIL PROTECTED] [EMAIL PROTECTED], wix-users@lists.sourceforge.net wix-users@lists.sourceforge.net Subject Re: [WiX-users] Create EXE wrapper around my MSI? Kelly Leahy [EMAIL PROTECTED] writes: It sounds like your registration is happening in the wrong 'stage' of the install... Just because you're elevated in some places, it doesn't mean the entire run of the install is elevated. I think the elevation only occurs during the installexecutesequence, and only during the server side part of it, and maybe not even the whole thing. I'm sure this comment isn't all that helpful, but maybe it will point you in the right direction. Can you actually tell where the registration is sequenced? Please do not take this as a personal critique. You wrote I think So that means you are not sure, which is fine but the answers here are often I think that means to me the whole not I'm getting personal crap of MSI was just invented to make programmers live as hard as possible. There is a whole sorry (brain-dead) machinery needed to get something installed and it's even worse if one get's into the COM or even worse device installation area. Just how many tools do exist for building installers? What the hell do we gain with such complex installation voodo? Regards Friedrich - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ** This communication is intended solely for the addressee and is confidential. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Unless indicated to the contrary: it does not constitute professional advice or opinions upon which reliance may be made by the addressee or any other party, and it should be considered to be a work in progress. Unless otherwise noted in this email or its attachments, this communication does not form a Statement of Actuarial Opinion under American Academy of Actuaries guidelines. **- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WIX 3.0 release date
Christopher Painter wrote: I know a very good product manager that would probably volunteer. The question is, would the engineers yield the power in an open source environment? What does power have to do with it? -- sig://boB http://joyofsetup.com/ - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WIX 3.0 release date
I would like to make a suggestion: Could the beta tag on v3 be replaced with something less emotive. I am having problems convincing managers to accept v3 because of the beta tag, I think the code is more than that and has so much more than v2 that is worth adopting. I think if we have to wait for another year before the beta tag is removed it will stop a greater adoption of the code. I would suggest that in the near future (one or two months) it is released as something else. I'm not sure what but copying Microsoft you could use CTP (Community Technology Preview). Neil Neil Sleightholm X2 Systems Limited [EMAIL PROTECTED] -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rob Mensching Sent: 27 May 2008 19:22 To: dB.; Daniel Hughes; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] WIX 3.0 release date Interesting. Let's go back and look at the things that are driving the WiX v3 release. 1. Bugs. WiX v2 was marked stable by pushing a number of bugs to WiX v3 (especially Votive bugs). There are still a lot of bugs open that need to be fixed. I do not just want to push a bunch of WiX v2 bugs to WiX v4. 2. Patching. Patching is hard with MSI and the new tools in WiX v3 can help a lot. Those tools are basically done and we're just running down the bug tail now. 3. Votive. Votive was *very* rough in WiX v2. It had years to go before it was going to truly useable. In WiX v3, Justin and a lot of help from members of the VS team have made Votive far more usable. There are still a lot of bugs to fix and the only reason I think it can be done this year is because of the VS help. Otherwise, I'm quite certain we'd *still* have a very crippled VS story. 4. Bootstrapper. Every other day or so there is another request for chaining/bootstrapping. Some of the solutions out there meet some people's needs but IMHO none of them have all of the features that are needed to meet the majority of bootstrapping needs. This part of the WiX toolset is about 2 years late and I think it is a big mistake to go into 2009 without a useable bootstrap story. 5. DTF. After finally deciding that the MSI team was not going to do it, I asked Jason Ginchereau if he would like to add DTF to WiX v3. This codebase was pretty stable so my expectation was that this wouldn't affect our bug count much. Now let's talk about who's doing all of this work. I'm driving the bug count overall with help from the area owners. Peter Marcu (http://blogs.msdn.com/pmarcu) is driving the patching support backed up by Heath Stewart (http://blogs.msdn.com/heaths). Votive is lead by Justin Rockwood (http://blogs.msdn.com/jrock/) and Jason Ginchereau (http://blogs.msdn.com/jasongin)'s team from VS. The bootstrapper code base is being developed by Fredrik Grohn (http://fredrikgrohn.com) and hopefully will be added to WiX soon. DTF is, of course, Jason's baby. Bob Arnson (http://www.joyofsetup.com) basically helps out everywhere. With the exception of the VS team I would guess that each of those people donate about 10 hours per week to the toolset. There are others but that is the bulk of regular development happening on the WiX toolset. The sheer number of hours available to address bugs is why I think it will take until the end of the year. We could cut the bootstrapper (again) to focus solely on bugs and probably finish WiX v3 sooner but I believe the bootstrapper is more important than that. Plus, this is a volunteer project so it is hard to expect everyone to stay excited about solely fixing bugs for 6+ months. smile/ You should look at what parts of the WiX toolset you depend one when judging stability. If you just want the core toolset (candle, light) then that code base is very stable in v3. Arguably it is more stable than it was in WiX v2 (certainly more bug fixes). Granted v3 can change from build to build so you might pick up a bug but we fix core toolset regressions very, very quickly. As for Votive, I don't think you can compare the stability differences from v2 to v3. V3 is so much more feature rich and useful. That said, there is a lot of effort going into Votive right now and there have been some nasty bugs with VS2005 integration lately. Patching (pyro, torch)... those tools are quite stable but new so you might find new things. DTF, has been around for a long time and the bug fixes seem to reflect that. Ultimately, I believe that stability in the WiX toolset is measured by the number of changes going into the codebase. WiX v2 has no development so it is *extremely* stable. smile/ WiX v3 is quite functional but there are bug fixes going in so we have to reserve the right to accidentally break stuff that works. Pick you risk profile and go from there. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008.
Re: [WiX-users] WIX 3.0 release date
I understand the pain of trying to convince managers of anything that isn't in black and white but as far as I can see the Wix code is of beta quality ie..not functionally complete. It would problem be a bit irresponsible to paint it otherwise... Rob, What's the deal for the community getting involved to try and push this along? (Sorry if this has been discussed previously) 2008/5/28 Neil Sleightholm [EMAIL PROTECTED]: I would like to make a suggestion: Could the beta tag on v3 be replaced with something less emotive. I am having problems convincing managers to accept v3 because of the beta tag, I think the code is more than that and has so much more than v2 that is worth adopting. I think if we have to wait for another year before the beta tag is removed it will stop a greater adoption of the code. I would suggest that in the near future (one or two months) it is released as something else. I'm not sure what but copying Microsoft you could use CTP (Community Technology Preview). Neil Neil Sleightholm X2 Systems Limited [EMAIL PROTECTED] -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rob Mensching Sent: 27 May 2008 19:22 To: dB.; Daniel Hughes; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] WIX 3.0 release date Interesting. Let's go back and look at the things that are driving the WiX v3 release. 1. Bugs. WiX v2 was marked stable by pushing a number of bugs to WiX v3 (especially Votive bugs). There are still a lot of bugs open that need to be fixed. I do not just want to push a bunch of WiX v2 bugs to WiX v4. 2. Patching. Patching is hard with MSI and the new tools in WiX v3 can help a lot. Those tools are basically done and we're just running down the bug tail now. 3. Votive. Votive was *very* rough in WiX v2. It had years to go before it was going to truly useable. In WiX v3, Justin and a lot of help from members of the VS team have made Votive far more usable. There are still a lot of bugs to fix and the only reason I think it can be done this year is because of the VS help. Otherwise, I'm quite certain we'd *still* have a very crippled VS story. 4. Bootstrapper. Every other day or so there is another request for chaining/bootstrapping. Some of the solutions out there meet some people's needs but IMHO none of them have all of the features that are needed to meet the majority of bootstrapping needs. This part of the WiX toolset is about 2 years late and I think it is a big mistake to go into 2009 without a useable bootstrap story. 5. DTF. After finally deciding that the MSI team was not going to do it, I asked Jason Ginchereau if he would like to add DTF to WiX v3. This codebase was pretty stable so my expectation was that this wouldn't affect our bug count much. Now let's talk about who's doing all of this work. I'm driving the bug count overall with help from the area owners. Peter Marcu (http://blogs.msdn.com/pmarcu) is driving the patching support backed up by Heath Stewart (http://blogs.msdn.com/heaths). Votive is lead by Justin Rockwood (http://blogs.msdn.com/jrock/) and Jason Ginchereau (http://blogs.msdn.com/jasongin)'s http://blogs.msdn.com/jasongin%29%27steam from VS. The bootstrapper code base is being developed by Fredrik Grohn (http://fredrikgrohn.com) and hopefully will be added to WiX soon. DTF is, of course, Jason's baby. Bob Arnson (http://www.joyofsetup.com) basically helps out everywhere. With the exception of the VS team I would guess that each of those people donate about 10 hours per week to the toolset. There are others but that is the bulk of regular development happening on the WiX toolset. The sheer number of hours available to address bugs is why I think it will take until the end of the year. We could cut the bootstrapper (again) to focus solely on bugs and probably finish WiX v3 sooner but I believe the bootstrapper is more important than that. Plus, this is a volunteer project so it is hard to expect everyone to stay excited about solely fixing bugs for 6+ months. smile/ You should look at what parts of the WiX toolset you depend one when judging stability. If you just want the core toolset (candle, light) then that code base is very stable in v3. Arguably it is more stable than it was in WiX v2 (certainly more bug fixes). Granted v3 can change from build to build so you might pick up a bug but we fix core toolset regressions very, very quickly. As for Votive, I don't think you can compare the stability differences from v2 to v3. V3 is so much more feature rich and useful. That said, there is a lot of effort going into Votive right now and there have been some nasty bugs with VS2005 integration lately. Patching (pyro, torch)... those tools are quite stable but new so you might find new things. DTF, has been around for a long time and the bug fixes seem to reflect that. Ultimately, I
[WiX-users] Build Wix v3.4123 Issues
[exec] Done building target VsTemplatePathsTarget in project Votive2008.csproj -- FAILED. [exec] [exec] Done building project Votive2008.csproj -- FAILED. [exec] [exec] Build FAILED. See attached details in The following is a list of all issues I have had trying to build Wix. The latest issue #7 is above. I don't have a solution for it as yet. Mark E. Eva votive2005: votive2008.inc: [exec] Starting 'C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\msbuild.exe (/property:Configuration=Debug /target:B uild C:\Wix_v3_4123\src\votive\votive\Votive2008.csproj)' in 'C:\Wix_v3_4123' [exec] Microsoft (R) Build Engine Version 2.0.50727.1433 [exec] [Microsoft .NET Framework, Version 2.0.50727.1433] [exec] Copyright (C) Microsoft Corporation 2005. All rights reserved. [exec] [exec] Build started 5/28/2008 10:55:40 AM. [exec] __ [exec] Project C:\Wix_v3_4123\src\votive\votive\Votive2008.csproj (Build target(s)): [exec] [exec] Target GetSdkDirectories: [exec] Registry value at 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SDKs\Windows\v6.1\InstallationFolder' is 'C:\Program Files\Microsoft SDKs\Windows\v6.1\'. [exec] Registry value at 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SDKs\Windows\v6.0a\InstallationFolder ' is 'C:\Program Files\Microsoft SDKs\Windows\v6.0A\'. [exec] PlatformSdkIncludePath=C:\Program Files\Microsoft SDKs\Windows\v6.1\\Include [exec] Registry value at 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\9.0\Setup\VC\ProductDir' is 'C:\Pr ogram Files\Microsoft Visual Studio 9.0\VC\'. [exec] VC9IncludePath=C:\Program Files\Microsoft Visual Studio 9.0\VC\\Include [exec] VC9BinPath=C:\Program Files\Microsoft Visual Studio 9.0\VC\\Bin [exec] Target GetFrameworkPaths: [exec] Could not locate the .NET Framework SDK. The task is looking for the path to the .NET Framework SDK at the location specified in the SDKInstallRootv2.0 value of the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFra mework. You may be able to solve the problem by doing one of the following: 1.) Install the .NET Framework SDK. 2.) M anually set the above registry key to the correct location. [exec] Target PrepareForBuild: [exec] Creating directory C:\Wix_v3_4123\build\obj\debug\x86\Votive2008\. [exec] Target ResolveProjectReferences: [exec] __ [exec] Project C:\Wix_v3_4123\src\votive\votive\Votive2008.csproj is building C:\Wix_v3_4123\src\votive\scon ce\sconce2008.csproj (default targets): [exec] [exec] Target GetSdkDirectories: [exec] Registry value at 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SDKs\Windows\v6.1\InstallationFol der' is 'C:\Program Files\Microsoft SDKs\Windows\v6.1\'. [exec] Registry value at 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SDKs\Windows\v6.0a\InstallationFo lder' is 'C:\Program Files\Microsoft SDKs\Windows\v6.0A\'. [exec] PlatformSdkIncludePath=C:\Program Files\Microsoft SDKs\Windows\v6.1\\Include [exec] Registry value at 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\9.0\Setup\VC\ProductDir' is 'C :\Program Files\Microsoft Visual Studio 9.0\VC\'. [exec] VC9IncludePath=C:\Program Files\Microsoft Visual Studio 9.0\VC\\Include [exec] VC9BinPath=C:\Program Files\Microsoft Visual Studio 9.0\VC\\Bin [exec] Target GetFrameworkPaths: [exec] Could not locate the .NET Framework SDK. The task is looking for the path to the .NET Framework SDK at the location specified in the SDKInstallRootv2.0 value of the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NE TFramework. You may be able to solve the problem by doing one of the following: 1.) Install the .NET Framework SDK. 2 .) Manually set the above registry key to the correct location. [exec] Target PrepareForBuild: [exec] Creating directory C:\Wix_v3_4123\build\obj\debug\x86\sconce2008\. [exec] Target _CopyNonResxEmbeddedResources: [exec] Copying file from ..\SDK_VS2008\Common\Source\CSharp\Project\Resources\imagelis.bmp to C:\Wix_v3_ 4123\build\obj\debug\x86\sconce2008\Resources.imagelis.bmp. [exec] Target CoreResGen: [exec] Processing resource file ..\SDK_VS2008\Common\Source\CSharp\Project\Microsoft.VisualStudio.Package. Project.resx into C:\Wix_v3_4123\build\obj\debug\x86\sconce2008\Microsoft.VisualStudio.Package.Project.resources. [exec] Processing resource file ..\SDK_VS2008\Common\Source\CSharp\Project\SecurityWarningDialog.resx int o C:\Wix_v3_4123\build\obj\debug\x86\sconce2008\Microsoft.VisualStudio.Package.SecurityWarningDialog.resources. [exec] Processing resource file
Re: [WiX-users] WIX 3.0 release date
IMHO, with an open source project there is no such thing as a shipping version. I know that statement is going to bring a vast amount of feedback but here is the deal. There is no REAL support. Compared to commercial products that you can pay to have bugs fixed or work done. In all honesty, the WIX team can stop working on this project tomorrow with no SLA being broken (I know their not going to, but...). In my mind, this is the same issue that occurs with using NAnt, Apache, SVN, CVS or any other open source software. Putting labels on it is not important. It is open source and you either choose to use the version that is stable enough for you, keep upgrading with each release or don't use it at all. I had to run this flag up the totem pole at a few large companies. There is a cost ratio to open source even though the code is free. The cost is no paid support and no time lines. If there is a bug in the code that blocks your product from shipping, then so be it. You have the code, you fix it (additional resources/time needed which equals $$$). This needs to be factored into your companies budget rather than asking the development team to shape up their model. These guys are doing this out of their desire and until MS ponies up and devotes a fully paid staff to the project there should be no solid expections. If the WIX team chooses to offer time and support that is great, but not a necessity. My $0.02... -- Brian Rogers Intelligence removes complexity. - BR http://www.codeplex.com/wixml/ On Wed, May 28, 2008 at 9:27 AM, Neil Sleightholm [EMAIL PROTECTED] wrote: I would like to make a suggestion: Could the beta tag on v3 be replaced with something less emotive. I am having problems convincing managers to accept v3 because of the beta tag, I think the code is more than that and has so much more than v2 that is worth adopting. I think if we have to wait for another year before the beta tag is removed it will stop a greater adoption of the code. I would suggest that in the near future (one or two months) it is released as something else. I'm not sure what but copying Microsoft you could use CTP (Community Technology Preview). Neil Neil Sleightholm X2 Systems Limited [EMAIL PROTECTED] -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rob Mensching Sent: 27 May 2008 19:22 To: dB.; Daniel Hughes; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] WIX 3.0 release date Interesting. Let's go back and look at the things that are driving the WiX v3 release. 1. Bugs. WiX v2 was marked stable by pushing a number of bugs to WiX v3 (especially Votive bugs). There are still a lot of bugs open that need to be fixed. I do not just want to push a bunch of WiX v2 bugs to WiX v4. 2. Patching. Patching is hard with MSI and the new tools in WiX v3 can help a lot. Those tools are basically done and we're just running down the bug tail now. 3. Votive. Votive was *very* rough in WiX v2. It had years to go before it was going to truly useable. In WiX v3, Justin and a lot of help from members of the VS team have made Votive far more usable. There are still a lot of bugs to fix and the only reason I think it can be done this year is because of the VS help. Otherwise, I'm quite certain we'd *still* have a very crippled VS story. 4. Bootstrapper. Every other day or so there is another request for chaining/bootstrapping. Some of the solutions out there meet some people's needs but IMHO none of them have all of the features that are needed to meet the majority of bootstrapping needs. This part of the WiX toolset is about 2 years late and I think it is a big mistake to go into 2009 without a useable bootstrap story. 5. DTF. After finally deciding that the MSI team was not going to do it, I asked Jason Ginchereau if he would like to add DTF to WiX v3. This codebase was pretty stable so my expectation was that this wouldn't affect our bug count much. Now let's talk about who's doing all of this work. I'm driving the bug count overall with help from the area owners. Peter Marcu (http://blogs.msdn.com/pmarcu) is driving the patching support backed up by Heath Stewart (http://blogs.msdn.com/heaths). Votive is lead by Justin Rockwood (http://blogs.msdn.com/jrock/) and Jason Ginchereau (http://blogs.msdn.com/jasongin)'s team from VS. The bootstrapper code base is being developed by Fredrik Grohn (http://fredrikgrohn.com) and hopefully will be added to WiX soon. DTF is, of course, Jason's baby. Bob Arnson (http://www.joyofsetup.com) basically helps out everywhere. With the exception of the VS team I would guess that each of those people donate about 10 hours per week to the toolset. There are others but that is the bulk of regular development happening on the WiX toolset. The sheer number of hours available to address bugs is why I think it will take until the end of the year. We could cut the
