Re: [WiX-users] Recent WIX sources will not build

[Neil Sleightholm]

That is what I thought, it worked on my Vista machine but not on a clean build 
of 2008. I was calling %VS90COMNTOOLS%\vsvars.bat but it still didn't set the 
path, I'll have to check what is different on my build machine.
 
Neil
 
Neil Sleightholm
X2 Systems Limited
[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] 
 



From: Bob Arnson [mailto:[EMAIL PROTECTED]
Sent: Wed 22/10/2008 05:02
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Recent WIX sources will not build



Neil Sleightholm wrote:
 I have found a solution to the error: src\dtf\tools\sfxca\precomp.h(32)
 : fatal error C1083: Cannot open type library file: 'mscorlib.tlb': No
 such file or directory.

 If you add C:\Windows\Microsoft.NET\Framework\v2.0.50727 to the path
 before running the build it should fix it.
  

The build expects to run from a command shell set up by VS or the SDK,
which includes that path.

--
sig://boB
http://joyofsetup.com/



-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK  win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK  win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100url=/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Installing shortcuts to All Users profile in a per-machine installation

[Matt Siebert]

If I move the shortcut to another component with a RegistryValue KeyPath
with Root=HKMU then I can avoid ICE43 and the shortcut will be created in
the All Users profile.  This doesn't 'feel' right though, it seems that
there is an obvious bug in ICE since the shortcut is configured to go to a
per-machine location and ICE just doesn't recognise that.

Also, I still get ICE57.  Google reveals that others seem to think ICE57 is
irrelevant - I even found this forum post (
http://forum.installsite.net/index.php?s=15f9befa23ef0eba0bdb1cb79934aebdshowtopic=15991st=0#entry46021)
which mentions that its going to be removed from the Vista certification
doc.  I did a quick search but can't find a recent Vista certification doc
or anything else to confirm that.  Can anyone else confirm this?

Thanks in advance.

On Wed, Oct 22, 2008 at 4:12 PM, Matt Siebert [EMAIL PROTECTED] wrote:

 Hi all,

 I'm new to WiX and I'm trying to create a test install for a single file
 with a shortcut in the All Users profile.

 The file I'm installing is going to %programfiles%\Company\Product and I
 want to place a shortcut in %allusersprofile%\Desktop.

 I've done a lot of googling and searched the archives for this mailing list
 and it seems that everyone who has had a similar problem has been directed
 to
 http://robmensching.com/blog/archive/2007/04/27/How-to-create-an-uninstall-shortcut-and-pass-all-the.aspx,
 but I can't see how that post solves the issue - it installs shortcuts to
 the current user's profile using a RegistryValue as the KeyPath (I already
 did this to create a per-user test install) but doesn't show how to install
 shortcuts to the All Users profile in a per-machine install.

 Here is my very simple product.wxs:

 Wix xmlns=http://schemas.microsoft.com/wix/2006/wi;
   Product Id={PUT-GUID-HERE} Name=Product Language=1033 Version=
 1.0.0.0 Manufacturer=Company UpgradeCode={PUT-GUID-HERE}
 Package InstallerVersion=200 Compressed=yes/
 Media Id=1 Cabinet=TestApp.cab EmbedCab=yes/
 Property Id=ALLUSERS Value=1/

 Directory Id=TARGETDIR Name=SourceDir
   Directory Id=ProgramFilesFolder
 Directory Id=CompanyFolder Name=Company
   Directory Id=APPLICATIONROOTDIRECTORY Name=Product/
 /Directory
   /Directory
   Directory Id=DesktopFolder/
 /Directory

 DirectoryRef Id=APPLICATIONROOTDIRECTORY
   Component Id=TestApp Guid={PUT-GUID-HERE}
 File Source=Product.exe KeyPath=yes Checksum=yes
 Vital=yes
   Shortcut Id=TestAppShortcut Name=Product
 Directory=DesktopFolder/
 /File
   /Component
 /DirectoryRef

 Feature Id=MainApplication Title=Main Application Level=1
 Absent=disallow AllowAdvertise=no
   ComponentRef Id=TestApp/
 /Feature
   /Product
 /Wix

 I've set ALLUSERS=1 and this should cause the DesktopFolder property to
 point to the desktop folder in the All Users profile on the target
 machine.

 I get the following errors from light.exe:

 error LGHT0204: ICE43: Component TestApp has non-advertised shortcuts. It
 should use a registry key under HKCU as its KeyPath, not a file.
 error LGHT0204: ICE57: Component 'TestApp' has both per-user and
 per-machine data with a per-machine KeyPath.

 Surely its possible to install non-advertised shortcuts to the All Users
 profile...

 Any help would be greatly appreciated.

 Thanks,
 Matt.

-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK  win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] ASP.NET on IIS

[Eitan Behar]

Hi,

Please, how can I set the ASP.NET version for a Web Site ? I just want to
set the general selection on the ASP.NET tab, and leave the default
extensions as they are.

Thanks,

Eitan
-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK  win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Installing shortcuts to All Users profile in aper-machine installation

[Pally Sandher]

In the WiX 3.0 documentation under the How To Guides section there is
a page on creating shortcuts. This works fine without any ICE validation
errors or warnings even when ALLUSERS=1 is set.



Palbinder Sandher 
Software Deployment and IT Administrator 

T: +44 (0) 141 945 8500 
F: +44 (0) 141 945 8501 
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


-Original Message-
From: Matt Siebert [mailto:[EMAIL PROTECTED] 
Sent: 22 October 2008 09:17
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Installing shortcuts to All Users profile in
aper-machine installation

If I move the shortcut to another component with a RegistryValue KeyPath
with Root=HKMU then I can avoid ICE43 and the shortcut will be created
in the All Users profile.  This doesn't 'feel' right though, it seems
that there is an obvious bug in ICE since the shortcut is configured to
go to a per-machine location and ICE just doesn't recognise that.

Also, I still get ICE57.  Google reveals that others seem to think ICE57
is irrelevant - I even found this forum post (
http://forum.installsite.net/index.php?s=15f9befa23ef0eba0bdb1cb79934aeb
dshowtopic=15991st=0#entry46021)
which mentions that its going to be removed from the Vista certification
doc.  I did a quick search but can't find a recent Vista certification
doc or anything else to confirm that.  Can anyone else confirm this?

Thanks in advance.

On Wed, Oct 22, 2008 at 4:12 PM, Matt Siebert [EMAIL PROTECTED]
wrote:

 Hi all,

 I'm new to WiX and I'm trying to create a test install for a single 
 file with a shortcut in the All Users profile.

 The file I'm installing is going to %programfiles%\Company\Product and

 I want to place a shortcut in %allusersprofile%\Desktop.

 I've done a lot of googling and searched the archives for this mailing

 list and it seems that everyone who has had a similar problem has been

 directed to 
 http://robmensching.com/blog/archive/2007/04/27/How-to-create-an-unins
 tall-shortcut-and-pass-all-the.aspx,
 but I can't see how that post solves the issue - it installs shortcuts

 to the current user's profile using a RegistryValue as the KeyPath (I 
 already did this to create a per-user test install) but doesn't show 
 how to install shortcuts to the All Users profile in a per-machine
install.

 Here is my very simple product.wxs:

 Wix xmlns=http://schemas.microsoft.com/wix/2006/wi;
   Product Id={PUT-GUID-HERE} Name=Product Language=1033
Version=
 1.0.0.0 Manufacturer=Company UpgradeCode={PUT-GUID-HERE}
 Package InstallerVersion=200 Compressed=yes/
 Media Id=1 Cabinet=TestApp.cab EmbedCab=yes/
 Property Id=ALLUSERS Value=1/

 Directory Id=TARGETDIR Name=SourceDir
   Directory Id=ProgramFilesFolder
 Directory Id=CompanyFolder Name=Company
   Directory Id=APPLICATIONROOTDIRECTORY Name=Product/
 /Directory
   /Directory
   Directory Id=DesktopFolder/
 /Directory

 DirectoryRef Id=APPLICATIONROOTDIRECTORY
   Component Id=TestApp Guid={PUT-GUID-HERE}
 File Source=Product.exe KeyPath=yes Checksum=yes
 Vital=yes
   Shortcut Id=TestAppShortcut Name=Product
 Directory=DesktopFolder/
 /File
   /Component
 /DirectoryRef

 Feature Id=MainApplication Title=Main Application Level=1
 Absent=disallow AllowAdvertise=no
   ComponentRef Id=TestApp/
 /Feature
   /Product
 /Wix

 I've set ALLUSERS=1 and this should cause the DesktopFolder property 
 to point to the desktop folder in the All Users profile on the 
 target machine.

 I get the following errors from light.exe:

 error LGHT0204: ICE43: Component TestApp has non-advertised shortcuts.

 It should use a registry key under HKCU as its KeyPath, not a file.
 error LGHT0204: ICE57: Component 'TestApp' has both per-user and 
 per-machine data with a per-machine KeyPath.

 Surely its possible to install non-advertised shortcuts to the All
Users
 profile...

 Any help would be greatly appreciated.

 Thanks,
 Matt.


-
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge Build the coolest Linux based applications with Moblin SDK 
win great prizes Grand prize is a trip for two to an Open Source event
anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK  win great prizes
Grand prize is a trip for two to 

Re: [WiX-users] Installing shortcuts to All Users profile in a per-machine installation

[Sébastien Mouren]

2008/10/22 Matt Siebert [EMAIL PROTECTED]:
 Hi all,

 I'm new to WiX and I'm trying to create a test install for a single file
 with a shortcut in the All Users profile.

 The file I'm installing is going to %programfiles%\Company\Product and I
 want to place a shortcut in %allusersprofile%\Desktop.

 I've done a lot of googling and searched the archives for this mailing list
 and it seems that everyone who has had a similar problem has been directed
 to
 http://robmensching.com/blog/archive/2007/04/27/How-to-create-an-uninstall-shortcut-and-pass-all-the.aspx,
 but I can't see how that post solves the issue - it installs shortcuts to
 the current user's profile using a RegistryValue as the KeyPath (I already
 did this to create a per-user test install) but doesn't show how to install
 shortcuts to the All Users profile in a per-machine install.

 Here is my very simple product.wxs:

 Wix xmlns=http://schemas.microsoft.com/wix/2006/wi;
  Product Id={PUT-GUID-HERE} Name=Product Language=1033 Version=
 1.0.0.0 Manufacturer=Company UpgradeCode={PUT-GUID-HERE}
Package InstallerVersion=200 Compressed=yes/
Media Id=1 Cabinet=TestApp.cab EmbedCab=yes/
Property Id=ALLUSERS Value=1/

Directory Id=TARGETDIR Name=SourceDir
  Directory Id=ProgramFilesFolder
Directory Id=CompanyFolder Name=Company
  Directory Id=APPLICATIONROOTDIRECTORY Name=Product/
/Directory
  /Directory
  Directory Id=DesktopFolder/
/Directory

DirectoryRef Id=APPLICATIONROOTDIRECTORY
  Component Id=TestApp Guid={PUT-GUID-HERE}
File Source=Product.exe KeyPath=yes Checksum=yes Vital=yes
  Shortcut Id=TestAppShortcut Name=Product
 Directory=DesktopFolder/
/File
  /Component
/DirectoryRef

Feature Id=MainApplication Title=Main Application Level=1
 Absent=disallow AllowAdvertise=no
  ComponentRef Id=TestApp/
/Feature
  /Product
 /Wix

 I've set ALLUSERS=1 and this should cause the DesktopFolder property to
 point to the desktop folder in the All Users profile on the target
 machine.

 I get the following errors from light.exe:

 error LGHT0204: ICE43: Component TestApp has non-advertised shortcuts. It
 should use a registry key under HKCU as its KeyPath, not a file.
 error LGHT0204: ICE57: Component 'TestApp' has both per-user and per-machine
 data with a per-machine KeyPath.

 Surely its possible to install non-advertised shortcuts to the All Users
 profile...

 Any help would be greatly appreciated.

 Thanks,
 Matt.

The common desktop and a user's desktop uses the same DesktopFolder
property: the ALLUSERS property allows to choose between the two.
Some ICE tests implements best practices compliance defined by the
Windows Installer team. These best practices makes harder sometimes
for the user to think its setup . There are a few corner case and you
seem to be in one of these.
A few workaround are possible:
-your setup needs to be deployed per machine (ProgramFilesFolder and
shortcut place in the common DesktopFolder), why don't you advertise
your shorcut and enforce local deployment of the parent feature?
-create, as other indicated in their answers, another component like this one:
Component Id=Shortcut Guid=* Directory=ProgramFilesFolder
  RegistryKey Id='TestAppKey' Root='HKCU'
Action='createAndRemoveOnUninstall' Key='Software\Company\Product'
RegistryValue Id='TestAppValue' Name='TestAppValue'
Type='string' Value='installed' Action='write' KeyPath='yes' /
  /RegistryKey
  Shortcut Id=Link
  Name=Product
  Description=My Application Description
  WorkingDirectory=APPLICATIONROOTDIRECTORY
  Directory=DesktopFolder
  Target=[APPLICATIONROOTDIRECTORY]Product.exe /
/Component
include this one in your only feature. This one is trickier but read
ICE 57 (http://msdn.microsoft.com/en-us/library/aa368994(VS.85).aspx)
and 43 (http://msdn.microsoft.com/en-us/library/aa368968(VS.85).aspx).
They explain why you should use another component, a per-user reg key
as a keypath for a per-machine shortcut. It has a default of orphaning
registry key and value if reinstalled multiple times by different
users.
This snippet won't work as is: requires some cleaning and corrections
to your original example.

-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK  win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Heat and COM executable registry extraction

[Pally Sandher]

I have the exact same problem with a Out-Of-Process COM server  it
would be absolutely awesome if heat.exe would be able to process these
in the same manner as it does for DLL's  OCX's which have a
DLLRegisterServer entrypoint but I doubt that'll ever happen. I'd much
prefer having the fragment for registering this executable to be the
similar to the rest of my fragments for COM registration as it is much
tidier using TypeLibs  Class ID's  Interfaces than a huge list of
RegistryKeys  RegistryValues.

Just a tip, you can automate step 3 using WiXCop.exe from WiX v3. It
won't fix the hard-coded paths but at least it will save you the trouble
of having to convert all the Registry tags to either RegistryKey or
RegistryValue (again it would be nice if heat.exe would convert .reg to
wix code as it's supposed to be the successor to tallow but I doubt
it'll ever happen  it would be a moot point if heat.exe did the first
thing anyway).


Palbinder Sandher 
Software Deployment and IT Administrator 

T: +44 (0) 141 945 8500 
F: +44 (0) 141 945 8501 
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



-Original Message-
From: Arunkumar Viswanathan [mailto:[EMAIL PROTECTED] 
Sent: 11 October 2008 04:29
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Heat and COM executable registry extraction

Phil,

Thanks for your tip. Here is what I did to solve the problem:

1) As Phil suggested I ran RegSpy2 and gathered all the registry
information from the COM Executable and saved it in a .reg file.
2) I used Tallow option to generate a wix file by passing in the .reg
file.
3) Tallow uses Registry instead of the newer RegistryKey and
RegistryValue tags. The older Registry key logic causes primary key
errors in the Registry table. Hence I did a very fast search and replace
of the older keys into the newer format. For example, part of the final
output looks like this - 

RegistryKey Root=HKCR
Key=Interface\{41A7D761-6018-11CF-9016-00AA0068841E}
Action=createAndRemoveOnUninstall
RegistryValue Value=DataObjectFiles Type=string /
  /RegistryKey
  RegistryKey Root=HKCR
Key=Interface\{41A7D761-6018-11CF-9016-00AA0068841E}\ProxyStubClsid
Action=createAndRemoveOnUninstall
RegistryValue Value={00020424---C000-0046}
Type=string /
  /RegistryKey
  RegistryKey Root=HKCR
Key=Interface\{41A7D761-6018-11CF-9016-00AA0068841E}\ProxyStubClsid32
Action=createAndRemoveOnUninstall
RegistryValue Value={00020424---C000-0046}
Type=string /
  /RegistryKey
  RegistryKey Root=HKCR
Key=Interface\{41A7D761-6018-11CF-9016-00AA0068841E}\TypeLib
Action=createAndRemoveOnUninstall
RegistryValue Value={EA544A21-C82D-11D1-A3E4-00A0C90AEA82}
Type=string /
RegistryValue Name=Version Value=6.0 Type=string /
  /RegistryKey

4) Next I replaced hard coded file paths to MSI friendly ones like
[INSTALLDIR], [SystemFolder]\MSVBVM60.DLL\3 etc.

5) I included the new component fragment where it is necessary and
linked with the feature.

Thanks a lot for all your help.

-Arun

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Wilson,
Phil
Sent: 2008-Oct-09 Thu 12:49 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Heat and COM executable registry extraction

If you scroll down here:
http://installsite.org/pages/en/msi/tips.htm
to RegSpy you'll find the source for a tool that works with Dlls and exe
COM servers.

It uses the registry overrides to redirect the registration entries. Exe
servers are handled by running them with /regserver suspended, then
injecting registry redirection, then resuming them to do the
registration to the redirected registry location.

Someone updated it to include typelib information too, that's what
RegSpy2 is.

Phil Wilson

-Original Message-
From: Arunkumar Viswanathan [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 09, 2008 4:32 AM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Heat and COM executable registry extraction

Kamil  Michael, thanks a lot for the information you have provided.

Kamil, I am very interested in trying out your tool. I can use Oleview
and extract the threading model and other default information. Do post
details on where to get your tool and how to use it.

Thanks
-Arun

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Kamil
Mierzejewski
Sent: 2008-Oct-09 Thu 6:01 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Heat and COM executable registry extraction

Hi,

I also encountered this problem. My solution was to design a special
tool which scans .tlb files and 

[WiX-users] Bug in x64 build of WiX UtilExtension?

[Pally Sandher]

I'm trying to use util:XMLFile to modify the inner text of a tag in an XML file 
during installation which is installed by my MSI for one of our plug-ins.

The XML file is named IESveInterfaceParameters.xml and contains the following 
code:

?xml version='1.0'?
IESInterface
  IESveLocationM:\IES\apps /IESveLocation
  OutputveXMLLocation /OutputveXMLLocation
  Preferences city='Boulder (CO)' latitude='40.017' minimumFloorArea='0.0' 
buildingAreaType='Office' thinWalls='1' 
buildingRoomService='VariableRefrigerantFlow' 
verticalHorizontalElementTransitionAngle='45.0' 
adjacencySeparationDistance='0.9144923921' longitude='-105.283' 
diagnosticAids='no' minimumRoomHeight='0.0'/
/IESInterface
 
My installer code is as follows:
 
Component Id=Dialogs DiskId=1 Guid=myguid
...
  File Id=IESveInterfaceParameters.xml Name=IESveInterfaceParameters.xml 
Source=..\..\..\code\Sketchup\Plugins\IESLink\Dialogs\IESveInterfaceParameters.xml
 /
...
  util:XmlFile Id=updateVELocation Action=setValue 
File=[#IESveInterfaceParameters.xml] Value=[VE59LOCATION]apps 
ElementPath=/IESInterface/IESveLocation SelectionLanguage=XPath /
/Component


All the above code is supposed to do is replace the inner text of the 
IESveLocation tag. Unfortunately the documentation for util:XMLFile leaves a 
lot to be desired so it doesn't work as yet (back to good old trial  error 
again). Any help would be appreciated however this isn't what I'm referring to 
as a bug.

The machine that I use to build my MSIs runs XP64. I install the Wix3_x64.msi 
package when updating my WiX compiler (currently using v3.0.4617.0). When I 
build my MSI in Visual Studio it is set to build as x86  checking it in Orca 
shows the Platform set to Intel.

If I attempt to install it on an XP64 Virtual Machine I get the following in 
the log:

Action 12:08:28: ExecXmlFile. 
MSI (s) (40:C4) [12:08:28:138]: Executing op: 
CustomActionSchedule(Action=ExecXmlFile,ActionType=3073,Source=BinaryData,Target=ExecXmlFile,CustomActionData=1€1€C:\Program
 Files (x86)\Google\Google SketchUp 
6\Plugins\IESLink\Dialogs\IESveInterfaceParameters.xml€3€/IESInterface/IESveLocation€€C:\Program
 Files (x86)\IES\VE 59\)
MSI (s) (40:C4) [12:08:28:138]: Creating MSIHANDLE (10) of type 790536 for 
thread 1988
MSI (s) (40:C0) [12:08:28:138]: Invoking remote custom action. DLL: 
C:\WINDOWS\Installer\MSI4.tmp, Entrypoint: ExecXmlFile
MSI (s) (40:C0) [12:08:28:169]: Generating random cookie.
MSI (s) (40:C0) [12:08:28:169]: Created Custom Action Server with PID 1464 
(0x5B8).
MSI (s) (40:A8) [12:08:28:216]: Running as a service.
MSI (s) (40:A8) [12:08:28:216]: Hello, I'm your 32bit Elevated custom action 
server.
MSI (s) (40:C0) [12:08:28:497]: Closing MSIHANDLE (10) of type 790536 for 
thread 1988
Action ended 12:08:28: InstallFinalize. Return value 3. 

It then does a rollback  throws up the FatalError dialog. I'm guessing this is 
because my code is incorrect however when I attempt to install the same MSI on 
an XP32 Virtual Machine I get the following in the log:

Action 12:09:11: ExecXmlFile. 
MSI (s) (94:10) [12:09:11:325]: Executing op: 
CustomActionSchedule(Action=ExecXmlFile,ActionType=3073,Source=BinaryData,Target=ExecXmlFile,CustomActionData=1€1€C:\Program
 Files\Google\Google SketchUp 
6\Plugins\IESLink\Dialogs\IESveInterfaceParameters.xml€3€/IESInterface/IESveLocation€€C:\Program
 Files\IES\VE 59\)
MSI (s) (94:10) [12:09:11:340]: Creating MSIHANDLE (10) of type 790536 for 
thread 1296
MSI (s) (94:38) [12:09:11:340]: Invoking remote custom action. DLL: 
C:\WINDOWS\Installer\MSI4.tmp, Entrypoint: ExecXmlFile
MSI (s) (94:A0) [12:09:11:340]: Generating random cookie.
MSI (s) (94:A0) [12:09:11:356]: Created Custom Action Server with PID 532 
(0x214).
MSI (s) (94:BC) [12:09:11:418]: Running as a service.
MSI (s) (94:BC) [12:09:11:418]: Hello, I'm your 32bit Elevated custom action 
server.
MSI (s) (94!88) [12:09:13:637]: Creating MSIHANDLE (11) of type 790531 for 
thread 648
ExecXmlFile:  Found Wow64 API, but unable to link to 
Wow64DisableWow64FsRedirection function in kernel32.dll
MSI (s) (94!88) [12:09:13:653]: Closing MSIHANDLE (11) of type 790531 for 
thread 648
MSI (s) (94!88) [12:09:13:653]: Creating MSIHANDLE (12) of type 790531 for 
thread 648
ExecXmlFile:  Found Wow64 API, but unable to link to 
Wow64RevertWow64FsRedirection function in kernel32.dll
MSI (s) (94!88) [12:09:13:653]: Closing MSIHANDLE (12) of type 790531 for 
thread 648
MSI (s) (94:38) [12:09:13:715]: Closing MSIHANDLE (10) of type 790536 for 
thread 1296
Action ended 12:09:13: InstallFinalize. Return value 3.

Why any mention of the WoW64 API exists when running on 32-bit XP is bizarre. 
Hence I reckon it's a bug. I haven't tried installing the non-x64 WiX MSI as 
yet but while I do, if anyone could confirm or deny this as being a bug before 
I report it on the SourceForge tracker it would be a great help.

Cheers,


Palbinder Sandher 
Software Deployment and IT Administrator 

T: +44 (0) 141 945 8500 
F: +44 (0) 

[WiX-users] Program Menu: How To Implement An Icon?

[Andrew Kendall]

Hi,

I've worked out how to a top-level Program Menu entry which contains a nested 
list of shortcuts, viz:

...
  Directory Id=ProgramMenuFolder
Directory Id=ShortcutFolder Name=AutoTrack
  Component Id=menu_SavoyCADExe 
Guid={8597C461-16C4-4E8B-A97C-A4B80813C522}
ConditionNOT VersionNT64/Condition
Shortcut Id=menu_SavoyCADExe Directory=ShortcutFolder 
Name=SavoyCAD
  Icon=atricon.exe IconIndex=0 
  Target=[INSTALLDIR]atr.exe /
CreateFolder /
RemoveFolder Id=RemoveShortcutFolder On=uninstall /
  /Component
/Directory
  /Directory

...


Though I am able to attach icons to the nested shortcuts, is anybody able to 
tell me how to attach an icon to the top-level Program Menu item, ie. the 
ShortcutFolder item?

Many thanks.
Andrew


  
-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK  win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] problems configuring MSDTC via installer

[Scott Sam]

I'm trying to configure the MSDTC settings by changing the registry values.  I 
am able to do this by hand using regedit without any problems.  When I try do 
this using wix I get an error. Below is the wix code followed by the error.  
What am I doing wrong? Is there a better way to do this?

RegistryValue Id=NetworkDtcAccessAdmin Root=HKLM 
Key=HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDTC\Security 
Name=NetworkDtcAccessAdmin Type=integer Value=1 /

Could not write value NetworkDtcAccessAdmin to key 
\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDTC\Security.  Verify that you have 
sufficient access to that key, or contact your support personnel.

Could not wr

Scott Sam
Software Developer

 Clearview Enterprise Content Management
www.clearviewecm.com  |  248 290 0230 ext 218

The information contained in this message is privileged and confidential and is 
intended solely for the addressee(s). 
If you are not the intended recipient, please reply, and then delete this 
message from your mail server.

-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK  win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Program Menu: How To Implement An Icon?

[Sébastien Mouren]

2008/10/22 Andrew Kendall [EMAIL PROTECTED]:
 Hi,

 I've worked out how to a top-level Program Menu entry which contains a nested 
 list of shortcuts, viz:

 ...
  Directory Id=ProgramMenuFolder
Directory Id=ShortcutFolder Name=AutoTrack
  Component Id=menu_SavoyCADExe 
 Guid={8597C461-16C4-4E8B-A97C-A4B80813C522}
ConditionNOT VersionNT64/Condition
Shortcut Id=menu_SavoyCADExe Directory=ShortcutFolder 
 Name=SavoyCAD
  Icon=atricon.exe IconIndex=0
  Target=[INSTALLDIR]atr.exe /
CreateFolder /
RemoveFolder Id=RemoveShortcutFolder On=uninstall /
  /Component
/Directory
  /Directory

 ...
I am not able to read the imperative and/or sequential way you wrote
your example:
Wix allows a declarative approach so I could separate things:
   !--Condition declaration
   ConditionNOT VersionNT64/Condition
...
  !--Directory declaration
  Directory Id=ProgramMenuFolder
Directory Id=ShortcutFolder Name=AutoTrack
  /Directory
  /Directory
...
  !--Component declaration
  Component Id=menu_SavoyCADExe Directory=ShortcutFolder
Guid={8597C461-16C4-4E8B-A97C-A4B80813C522}
 Shortcut Id=menu_SavoyCADExe
Name=SavoyCAD
Icon=atricon.exe
IconIndex=0
Target=[INSTALLDIR]atr.exe /
 CreateFolder /
 RemoveFolder Id=RemoveShortcutFolder On=uninstall /
   /Component


 Though I am able to attach icons to the nested shortcuts, is anybody able to 
 tell me how to attach an icon to the top-level Program Menu item, ie. the 
 ShortcutFolder item?

 Many thanks.
 Andrew

If I understand it well, you ask: how to change a folder icon?
Sorry if I misunderstood but this has nothing to do with Wix. MSDN
explains how to do it here:
http://msdn.microsoft.com/en-us/library/cc144102(VS.85).aspx

-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK  win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] ASP.NET on IIS

[Eitan Behar]

Thanks Siv,

But, this way I need to define every extension, is there a way that I can
tell WIX to change ONLY the default extensions, similar of when doing it
from IIS' GUI (on the ASP.NET tab).

Regards,

Eitan




On Wed, Oct 22, 2008 at 4:22 PM, Kalvagadda, SivaKrishna (MLX Technology) 
[EMAIL PROTECTED] wrote:

 This is how ssearch for t he verion of installed framework
 Property Id=ASPNETISAPIDLL
  DirectorySearch Id =AspnetIsapiDll
 Path=[WindowsFolder]Microsoft.NET\Framework Depth=1
FileSearch Id=AspnetIsapiDll LongName=aspnet_isapi.dll
 MinVersion=2.0 MaxVersion=3.5 /
  /DirectorySearch
/Property

 iis:WebApplicationExtension Extension=ascx CheckPath=yes
 Script=yes Executable=[ASPNETISAPIDLL]  Verbs=GET,HEAD,POST /
  iis:WebApplicationExtension Extension=ashx
 CheckPath=no Script=yes Executable=[ASPNETISAPIDLL]
 Verbs=GET,HEAD,POST /
  iis:WebApplicationExtension Extension=asmx
 CheckPath=no Script=yes Executable=[ASPNETISAPIDLL]
 Verbs=GET,HEAD,POST /

 Regards,
 SivaKrishna Kalvagadda,
 201-671-5552.

 -Original Message-
 From: Eitan Behar [mailto:[EMAIL PROTECTED]
 Sent: Wednesday, October 22, 2008 4:54 AM
 To: General discussion for Windows Installer XML toolset.
 Subject: [WiX-users] ASP.NET http://asp.net/ on IIS

 Hi,

 Please, how can I set the ASP.NET http://asp.net/ version for a Web Site
 ? I just want
 to
 set the general selection on the ASP.NET http://asp.net/ tab, and leave
 the default
 extensions as they are.

 Thanks,

 Eitan
 
 -
 This SF.Net email is sponsored by the Moblin Your Move Developer's
 challenge
 Build the coolest Linux based applications with Moblin SDK  win great
 prizes
 Grand prize is a trip for two to an Open Source event anywhere in the
 world
 http://moblin-contest.org/redirect.php?banner_id=100url=/
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users
 

 This message w/attachments (message) may be privileged, confidential or
 proprietary, and if you are not an intended recipient, please notify the
 sender, do not use or share it and delete it. Unless specifically indicated,
 this message is not an offer to sell or a solicitation of any investment
 products or other financial product or service, an official confirmation of
 any transaction, or an official statement of Merrill Lynch. Subject to
 applicable law, Merrill Lynch may monitor, review and retain
 e-communications (EC) traveling through its networks/systems. The laws of
 the country of each sender/recipient may impact the handling of EC, and EC
 may be archived, supervised and produced in countries other than the country
 in which you are located. This message cannot be guaranteed to be secure or
 error-free. This message is subject to terms available at the following
 link: http://www.ml.com/e-communications_terms/. By messaging with Merrill
 Lynch you consent to the foregoing.
 

 -
 This SF.Net email is sponsored by the Moblin Your Move Developer's
 challenge
 Build the coolest Linux based applications with Moblin SDK  win great
 prizes
 Grand prize is a trip for two to an Open Source event anywhere in the world
 http://moblin-contest.org/redirect.php?banner_id=100url=/
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users

-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK  win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Bug in x64 build of WiX UtilExtension?

[Joel Paula (hotmail)]

Hi,

I was stuck with the same error. I moved on to use XmlConfig instead.
I guess there really is a bug with XmlFile.

Anyway, those commands only add or delete nodes. I had to delete nodes and then 
re-add them with the correct information.

Example using XmlConfig:
util:XmlConfig Id=DelVELocation File=[#IESveInterfaceParameters.xml] 
Action=delete
ElementPath=/IESInterface
VerifyPath=IESveLocation
Node=element On=install Sequence=1 /
!--Create Nodes for Viewpoint--
util:XmlConfig Id=ViewpointButtonPicture 
File=[#IESveInterfaceParameters.xml] Action=create
ElementPath=/IESInterface 
Name=IESveLocation
Value=[VE59LOCATION]apps
Node=element On=install Sequence=2 /

HTH
Joel

-Original Message-
From: Pally Sandher [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, October 22, 2008 2:12 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Bug in x64 build of WiX UtilExtension?

I'm trying to use util:XMLFile to modify the inner text of a tag in an XML file 
during installation which is installed by my MSI for one of our plug-ins.

The XML file is named IESveInterfaceParameters.xml and contains the following 
code:

?xml version='1.0'?
IESInterface
  IESveLocationM:\IES\apps /IESveLocation
  OutputveXMLLocation /OutputveXMLLocation
  Preferences city='Boulder (CO)' latitude='40.017' minimumFloorArea='0.0' 
buildingAreaType='Office' thinWalls='1' 
buildingRoomService='VariableRefrigerantFlow' 
verticalHorizontalElementTransitionAngle='45.0' 
adjacencySeparationDistance='0.9144923921' longitude='-105.283' 
diagnosticAids='no' minimumRoomHeight='0.0'/
/IESInterface
 
My installer code is as follows:
 
Component Id=Dialogs DiskId=1 Guid=myguid
...
  File Id=IESveInterfaceParameters.xml Name=IESveInterfaceParameters.xml 
Source=..\..\..\code\Sketchup\Plugins\IESLink\Dialogs\IESveInterfaceParameters.xml
 /
...
  util:XmlFile Id=updateVELocation Action=setValue 
File=[#IESveInterfaceParameters.xml] Value=[VE59LOCATION]apps 
ElementPath=/IESInterface/IESveLocation SelectionLanguage=XPath /
/Component


All the above code is supposed to do is replace the inner text of the 
IESveLocation tag. Unfortunately the documentation for util:XMLFile leaves a 
lot to be desired so it doesn't work as yet (back to good old trial  error 
again). Any help would be appreciated however this isn't what I'm referring to 
as a bug.

The machine that I use to build my MSIs runs XP64. I install the Wix3_x64.msi 
package when updating my WiX compiler (currently using v3.0.4617.0). When I 
build my MSI in Visual Studio it is set to build as x86  checking it in Orca 
shows the Platform set to Intel.

If I attempt to install it on an XP64 Virtual Machine I get the following in 
the log:

Action 12:08:28: ExecXmlFile. 
MSI (s) (40:C4) [12:08:28:138]: Executing op: 
CustomActionSchedule(Action=ExecXmlFile,ActionType=3073,Source=BinaryData,Target=ExecXmlFile,CustomActionData=1€1€C:\Program
 Files (x86)\Google\Google SketchUp 
6\Plugins\IESLink\Dialogs\IESveInterfaceParameters.xml€3€/IESInterface/IESveLocation€€C:\Program
 Files (x86)\IES\VE 59\)
MSI (s) (40:C4) [12:08:28:138]: Creating MSIHANDLE (10) of type 790536 for 
thread 1988
MSI (s) (40:C0) [12:08:28:138]: Invoking remote custom action. DLL: 
C:\WINDOWS\Installer\MSI4.tmp, Entrypoint: ExecXmlFile
MSI (s) (40:C0) [12:08:28:169]: Generating random cookie.
MSI (s) (40:C0) [12:08:28:169]: Created Custom Action Server with PID 1464 
(0x5B8).
MSI (s) (40:A8) [12:08:28:216]: Running as a service.
MSI (s) (40:A8) [12:08:28:216]: Hello, I'm your 32bit Elevated custom action 
server.
MSI (s) (40:C0) [12:08:28:497]: Closing MSIHANDLE (10) of type 790536 for 
thread 1988
Action ended 12:08:28: InstallFinalize. Return value 3. 

It then does a rollback  throws up the FatalError dialog. I'm guessing this is 
because my code is incorrect however when I attempt to install the same MSI on 
an XP32 Virtual Machine I get the following in the log:

Action 12:09:11: ExecXmlFile. 
MSI (s) (94:10) [12:09:11:325]: Executing op: 
CustomActionSchedule(Action=ExecXmlFile,ActionType=3073,Source=BinaryData,Target=ExecXmlFile,CustomActionData=1€1€C:\Program
 Files\Google\Google SketchUp 
6\Plugins\IESLink\Dialogs\IESveInterfaceParameters.xml€3€/IESInterface/IESveLocation€€C:\Program
 Files\IES\VE 59\)
MSI (s) (94:10) [12:09:11:340]: Creating MSIHANDLE (10) of type 790536 for 
thread 1296
MSI (s) (94:38) [12:09:11:340]: Invoking remote custom action. DLL: 
C:\WINDOWS\Installer\MSI4.tmp, Entrypoint: ExecXmlFile
MSI (s) (94:A0) [12:09:11:340]: Generating random cookie.
MSI (s) (94:A0) [12:09:11:356]: Created Custom Action Server with PID 532 
(0x214).
MSI (s) (94:BC) [12:09:11:418]: Running as a service.
MSI (s) (94:BC) [12:09:11:418]: Hello, I'm your 32bit Elevated custom action 
server.
MSI (s) (94!88) [12:09:13:637]: Creating MSIHANDLE (11) of type 790531 for 
thread 648
ExecXmlFile:  Found Wow64 API, but unable to link to 

Re: [WiX-users] XmlConfig vs XmlFile

[Chad Petersen]

I believe they are very much interchangeable. I've got one existing
project that I use XMLFile in some older routines and XMLConfig in the
newer ones. I personally prefer XMLConfig. In searching the last few
weeks of posts here the questions are about XMLConfig, not XMLFile, so I
have a hunch more people are leaning toward XMLConfig, but that's mostly
a guess. But, yeah, they both add or remove .xml file entries. I presume
XMLFile predates XMLConfig.

-Original Message-
From: Alex Ivanoff [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, October 22, 2008 8:59 AM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] XmlConfig vs XmlFile

I am a little bit confused by existence of both XmlFile and XmlConfig.
Is there any docs/posts/etc on where to use which?




-
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK  win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the
world
http://moblin-contest.org/redirect.php?banner_id=100url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK  win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Help with XmlFile, FileCopy and ExeCommand

[Joel Paula (hotmail)]

I ended up using XmlConfig instead.

-Original Message-
From: Pally Sandher [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, October 22, 2008 4:32 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Help with XmlFile, FileCopy and ExeCommand

I have the same problem trying to modify the inner text of a node.

My code looks like the following:

Component Id=Dialogs DiskId=1 Guid=myguid
  ...
  File Id=IESveInterfaceParameters.xml Name=IESveInterfaceParameters.xml 
Source=..\..\..\code\Sketchup\Plugins\IESLink\Dialogs\IESveInterfaceParameters.xml
 /
  ...
  util:XmlFile Id=updateVELocation Action=setValue 
File=[#IESveInterfaceParameters.xml] Value=[VE59LOCATION]apps 
ElementPath=/IESInterface/IESveLocation SelectionLanguage=XPath / 
/Component

The contents of the IESveInterfaceParameters.xml file are as follows:

?xml version='1.0'?
IESInterface
  IESveLocationM:\IES\apps/IESveLocation
  OutputveXMLLocation /OutputveXMLLocation
  Preferences city='Boulder (CO)' latitude='40.017' minimumFloorArea='0.0' 
buildingAreaType='Office' thinWalls='1' 
buildingRoomService='VariableRefrigerantFlow' 
VerticalHorizontalElementTransitionAngle='45.0' 
adjacencySeparationDistance='0.9144923921' longitude='-105.283' 
diagnosticAids='no' minimumRoomHeight='0.0'/
/IESInterface

And I get the same result in my log file:

Action 12:08:28: ExecXmlFile. 
MSI (s) (40:C4) [12:08:28:138]: Executing op: 
CustomActionSchedule(Action=ExecXmlFile,ActionType=3073,Source=BinaryData,Target=ExecXmlFile,CustomActionData=1€1€C:\Program
 Files (x86)\Google\Google SketchUp 
6\Plugins\IESLink\Dialogs\IESveInterfaceParameters.xml€3€/IESInterface/IESveLocation€€C:\Program
 Files (x86)\IES\VE 59\)
MSI (s) (40:C4) [12:08:28:138]: Creating MSIHANDLE (10) of type 790536 for 
thread 1988
MSI (s) (40:C0) [12:08:28:138]: Invoking remote custom action. DLL: 
C:\WINDOWS\Installer\MSI4.tmp, Entrypoint: ExecXmlFile
MSI (s) (40:C0) [12:08:28:169]: Generating random cookie.
MSI (s) (40:C0) [12:08:28:169]: Created Custom Action Server with PID 1464 
(0x5B8).
MSI (s) (40:A8) [12:08:28:216]: Running as a service.
MSI (s) (40:A8) [12:08:28:216]: Hello, I'm your 32bit Elevated custom action 
server.
MSI (s) (40:C0) [12:08:28:497]: Closing MSIHANDLE (10) of type 790536 for 
thread 1988
Action ended 12:08:28: InstallFinalize. Return value 3. 


I'm about to give up  write a small console app to do the modification for me 
when passed the location of the xml file  the path I need added to it  then 
schedule it using QtExec as I've tried both util:XMLFile  util:XMLConfig  
neither work. It doesn't help that their documentation consists solely of very 
basic descriptions of their attributes in the Util schema section.


Palbinder Sandher 
Software Deployment and IT Administrator 

T: +44 (0) 141 945 8500 
F: +44 (0) 141 945 8501 
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


-Original Message-
From: Joel Paula (hotmail) [mailto:[EMAIL PROTECTED] 
Sent: 21 October 2008 19:09
To: WiX-users@lists.sourceforge.net
Subject: [WiX-users] Help with XmlFile, FileCopy and ExeCommand

I have an Xml file I need to put in another application file, write some xml to 
it and run it with that 3rd party application.
Sequence of events:
 1. Write Xml to file
 2. Get the Directory/Folder where the 3rd party application is sitting from 
win.ini  3. Copy Xml file to 3rd party app folder  4. Run 3rd party app against 
my Xml File.

My code:
!-- Get the Folder from Win.ini --
Property Id=GALILEOFOLDER
  IniFileSearch Id=win.ini Name=win.ini Section=Focalpoint
Key=SWDIR Type=directory
  /IniFileSearch
/Property

!-- copy Xml file to app folder, write xml to it and copy it to the 3rd 
party app folder.
   3rd party app exists if the win.ini entry is there --
  Directory Id=ProgramFilesFolder
Directory Id=INSTALLLOCATION Name=MyApp
  Component Id=aero.justify.xml
Guid=6C65CE83-50D0-4D73-AE3B-868536D56081 
File Id=aero.justify.xml Name=aero.justify.xml
KeyPath=yes Source=aero.justify.xml /
Condition![CDATA[Installed OR GALILEOFOLDER]]/Condition
util:XmlFile Id=ViewpointButtonPicture
File=aero.justify.xml Action=setValue 
 
ElementPath=//[EMAIL PROTECTED]'PNRViewGalileo.Toolbar.xml'[\]]/Add/Button/Pic
ture
 
Value=lt;![\[]CDATA[\[][INSTALLLOCATION]Panorama22.bmp[\]][\]]gt;
SelectionLanguage=XPath/
util:XmlFile Id=ViewpointButtonAction File=aero.justify.xml
Action=setValue
 
ElementPath=//[EMAIL PROTECTED]'PNRViewGalileo.Toolbar.xml'[\]]/Add/Button/Act
ion
 
Value=lt;![\[]CDATA[\[][INSTALLLOCATION]$(var.Aero.TargetFileName)[\]][\]]
gt; SelectionLanguage=XPath/
util:XmlFile Id=FocalpointButtonPicture

Re: [WiX-users] Bug in x64 build of WiX UtilExtension?

[Rob Mensching]

XmlFile is limited.  That's why we created XmlConfig.

-Original Message-
From: Joel Paula (hotmail) [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 22, 2008 09:11
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Bug in x64 build of WiX UtilExtension?

Hi,

I was stuck with the same error. I moved on to use XmlConfig instead.
I guess there really is a bug with XmlFile.

Anyway, those commands only add or delete nodes. I had to delete nodes and then 
re-add them with the correct information.

Example using XmlConfig:
util:XmlConfig Id=DelVELocation File=[#IESveInterfaceParameters.xml] 
Action=delete
ElementPath=/IESInterface
VerifyPath=IESveLocation
Node=element On=install Sequence=1 /
!--Create Nodes for Viewpoint--
util:XmlConfig Id=ViewpointButtonPicture 
File=[#IESveInterfaceParameters.xml] Action=create
ElementPath=/IESInterface 
Name=IESveLocation
Value=[VE59LOCATION]apps
Node=element On=install Sequence=2 /

HTH
Joel

-Original Message-
From: Pally Sandher [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 22, 2008 2:12 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Bug in x64 build of WiX UtilExtension?

I'm trying to use util:XMLFile to modify the inner text of a tag in an XML file 
during installation which is installed by my MSI for one of our plug-ins.

The XML file is named IESveInterfaceParameters.xml and contains the following 
code:

?xml version='1.0'?
IESInterface
  IESveLocationM:\IES\apps /IESveLocation
  OutputveXMLLocation /OutputveXMLLocation
  Preferences city='Boulder (CO)' latitude='40.017' minimumFloorArea='0.0' 
buildingAreaType='Office' thinWalls='1' 
buildingRoomService='VariableRefrigerantFlow' 
verticalHorizontalElementTransitionAngle='45.0' 
adjacencySeparationDistance='0.9144923921' longitude='-105.283' 
diagnosticAids='no' minimumRoomHeight='0.0'/
/IESInterface

My installer code is as follows:

Component Id=Dialogs DiskId=1 Guid=myguid
...
  File Id=IESveInterfaceParameters.xml Name=IESveInterfaceParameters.xml 
Source=..\..\..\code\Sketchup\Plugins\IESLink\Dialogs\IESveInterfaceParameters.xml
 /
...
  util:XmlFile Id=updateVELocation Action=setValue 
File=[#IESveInterfaceParameters.xml] Value=[VE59LOCATION]apps 
ElementPath=/IESInterface/IESveLocation SelectionLanguage=XPath /
/Component


All the above code is supposed to do is replace the inner text of the 
IESveLocation tag. Unfortunately the documentation for util:XMLFile leaves a 
lot to be desired so it doesn't work as yet (back to good old trial  error 
again). Any help would be appreciated however this isn't what I'm referring to 
as a bug.

The machine that I use to build my MSIs runs XP64. I install the Wix3_x64.msi 
package when updating my WiX compiler (currently using v3.0.4617.0). When I 
build my MSI in Visual Studio it is set to build as x86  checking it in Orca 
shows the Platform set to Intel.

If I attempt to install it on an XP64 Virtual Machine I get the following in 
the log:

Action 12:08:28: ExecXmlFile.
MSI (s) (40:C4) [12:08:28:138]: Executing op: 
CustomActionSchedule(Action=ExecXmlFile,ActionType=3073,Source=BinaryData,Target=ExecXmlFile,CustomActionData=1€1€C:\Program
 Files (x86)\Google\Google SketchUp 
6\Plugins\IESLink\Dialogs\IESveInterfaceParameters.xml€3€/IESInterface/IESveLocation€€C:\Program
 Files (x86)\IES\VE 59\)
MSI (s) (40:C4) [12:08:28:138]: Creating MSIHANDLE (10) of type 790536 for 
thread 1988
MSI (s) (40:C0) [12:08:28:138]: Invoking remote custom action. DLL: 
C:\WINDOWS\Installer\MSI4.tmp, Entrypoint: ExecXmlFile
MSI (s) (40:C0) [12:08:28:169]: Generating random cookie.
MSI (s) (40:C0) [12:08:28:169]: Created Custom Action Server with PID 1464 
(0x5B8).
MSI (s) (40:A8) [12:08:28:216]: Running as a service.
MSI (s) (40:A8) [12:08:28:216]: Hello, I'm your 32bit Elevated custom action 
server.
MSI (s) (40:C0) [12:08:28:497]: Closing MSIHANDLE (10) of type 790536 for 
thread 1988
Action ended 12:08:28: InstallFinalize. Return value 3.

It then does a rollback  throws up the FatalError dialog. I'm guessing this is 
because my code is incorrect however when I attempt to install the same MSI on 
an XP32 Virtual Machine I get the following in the log:

Action 12:09:11: ExecXmlFile.
MSI (s) (94:10) [12:09:11:325]: Executing op: 
CustomActionSchedule(Action=ExecXmlFile,ActionType=3073,Source=BinaryData,Target=ExecXmlFile,CustomActionData=1€1€C:\Program
 Files\Google\Google SketchUp 
6\Plugins\IESLink\Dialogs\IESveInterfaceParameters.xml€3€/IESInterface/IESveLocation€€C:\Program
 Files\IES\VE 59\)
MSI (s) (94:10) [12:09:11:340]: Creating MSIHANDLE (10) of type 790536 for 
thread 1296
MSI (s) (94:38) [12:09:11:340]: Invoking remote custom action. DLL: 
C:\WINDOWS\Installer\MSI4.tmp, Entrypoint: ExecXmlFile
MSI (s) (94:A0) [12:09:11:340]: Generating random cookie.
MSI (s) (94:A0) [12:09:11:356]: Created Custom Action Server with PID 532 
(0x214).
MSI (s) 

Re: [WiX-users] Bug in x64 build of WiX UtilExtension?

[Joel Paula (hotmail)]

Brian,

XmlConfig only allows for adding or deleting elements. 
I understand this is more straightforward when you want to rollback.

How do you edit an XML file?
XmlFile seemed to be the thing to use, but it always throws the error  
ExecXmlFile:  Found Wow64 API, but unable to link to 
Wow64DisableWow64FsRedirection function in kernel32.dll, no matter what I try 
to feed it.
Is it a bug and should we file a bug, or are we doing something wrong?

By the way, the example you give produces a value attribute on the 
/IESInterface/IESveLocation node when I build and run it. Is there anything 
that may influence how it works, depending on the machine or the .Net framework 
version?
I had to use something like:
util:XmlConfig Id=AddVELocation 
File=[#IESveInterfaceParameters.xml] 
Action=create
ElementPath=/IESInterface 
Name=IESveLocation
Node=element
Value=[VE59LOCATION]apps/

Thanks for your help.

Joel Paula


-Original Message-
From: Brian Rogers [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, October 22, 2008 4:47 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Bug in x64 build of WiX UtilExtension?

I'd recommend using XmlConfig instead of XmlFile.  The following should achieve 
what you want:

util:XmlConfig Id=updateVELocation
File=[#IESveInterfaceParameters.xml]
Action=create
On=install
ElementPath=/IESInterface/IESveLocation
Node=value
Value=[VE59LOCATION]apps /

This blog post has some more examples of using XmlConfig: 
http://blogs.msdn.com/gisenberg/archive/2007/10/09/wix-v3-and-xmlconfig-xmlfile-troubleshooting.aspx


##
$_='^#(/||/@[EMAIL PROTECTED]@:^[-['^;@@@\\])@..
{)/];)^{;$,+=(++$,);$_.=$,;`$_`;


-Original Message-
From: Pally Sandher [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 22, 2008 6:12 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Bug in x64 build of WiX UtilExtension?

I'm trying to use util:XMLFile to modify the inner text of a tag in an XML file 
during installation which is installed by my MSI for one of our plug-ins.

The XML file is named IESveInterfaceParameters.xml and contains the following 
code:

?xml version='1.0'?
IESInterface
  IESveLocationM:\IES\apps /IESveLocation
  OutputveXMLLocation /OutputveXMLLocation
  Preferences city='Boulder (CO)' latitude='40.017' minimumFloorArea='0.0' 
buildingAreaType='Office' thinWalls='1' 
buildingRoomService='VariableRefrigerantFlow' 
verticalHorizontalElementTransitionAngle='45.0' 
adjacencySeparationDistance='0.9144923921' longitude='-105.283' 
diagnosticAids='no' minimumRoomHeight='0.0'/
/IESInterface

My installer code is as follows:

Component Id=Dialogs DiskId=1 Guid=myguid
...
  File Id=IESveInterfaceParameters.xml Name=IESveInterfaceParameters.xml 
Source=..\..\..\code\Sketchup\Plugins\IESLink\Dialogs\IESveInterfaceParameters.xml
 /
...
  util:XmlFile Id=updateVELocation Action=setValue 
File=[#IESveInterfaceParameters.xml] Value=[VE59LOCATION]apps 
ElementPath=/IESInterface/IESveLocation SelectionLanguage=XPath /
/Component


All the above code is supposed to do is replace the inner text of the 
IESveLocation tag. Unfortunately the documentation for util:XMLFile leaves a 
lot to be desired so it doesn't work as yet (back to good old trial  error 
again). Any help would be appreciated however this isn't what I'm referring to 
as a bug.

The machine that I use to build my MSIs runs XP64. I install the Wix3_x64.msi 
package when updating my WiX compiler (currently using v3.0.4617.0). When I 
build my MSI in Visual Studio it is set to build as x86  checking it in Orca 
shows the Platform set to Intel.

If I attempt to install it on an XP64 Virtual Machine I get the following in 
the log:

Action 12:08:28: ExecXmlFile.
MSI (s) (40:C4) [12:08:28:138]: Executing op: 
CustomActionSchedule(Action=ExecXmlFile,ActionType=3073,Source=BinaryData,Target=ExecXmlFile,CustomActionData=1€1€C:\Program
 Files (x86)\Google\Google SketchUp 
6\Plugins\IESLink\Dialogs\IESveInterfaceParameters.xml€3€/IESInterface/IESveLocation€€C:\Program
 Files (x86)\IES\VE 59\)
MSI (s) (40:C4) [12:08:28:138]: Creating MSIHANDLE (10) of type 790536 for 
thread 1988
MSI (s) (40:C0) [12:08:28:138]: Invoking remote custom action. DLL: 
C:\WINDOWS\Installer\MSI4.tmp, Entrypoint: ExecXmlFile
MSI (s) (40:C0) [12:08:28:169]: Generating random cookie.
MSI (s) (40:C0) [12:08:28:169]: Created Custom Action Server with PID 1464 
(0x5B8).
MSI (s) (40:A8) [12:08:28:216]: Running as a service.
MSI (s) (40:A8) [12:08:28:216]: Hello, I'm your 32bit Elevated custom action 
server.
MSI (s) (40:C0) [12:08:28:497]: Closing MSIHANDLE (10) of type 790536 for 
thread 1988
Action ended 12:08:28: InstallFinalize. Return value 3.

It then does a rollback  throws up the FatalError dialog. I'm guessing this is 
because my code is incorrect 

Re: [WiX-users] grant permissions on a folder to a specific userifthe user happens to be NT AUTHORITY\Network Service

[Amy Rosewater]

That was a great idea Michael, and I tried it but the PermissionEx
element is still failing to add the appropriate permissions to the
directory.  Now instead of failing to add permissions for Network
Service it fails to add permissions for the IIS_WPG.

Is anyone else having a similar problems with wix v3.0.4513?

A

-Original Message-
From: Michael Osmond [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, October 21, 2008 11:38 PM
To: General discussion for Windows Installer XML toolset.; General
discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] grant permissions on a folder to a specific
userifthe user happens to be NT AUTHORITY\Network Service

Hello Amy,
 
I actually use [ComputerName]\iis_wpg this is IIS Working Process
Group of which network service is a member.  Although that said, this
group only exists if  IIS is an installed windows component.   This
covers, system, network service, local service and I think Aspnet.
 
Michael



From: Amy Rosewater [mailto:[EMAIL PROTECTED]
Sent: Wed 22/10/2008 1:29 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] grant permissions on a folder to a specific
user ifthe user happens to be NT AUTHORITY\Network Service



Thanks Ian, but I need to add to permissions on the directory rather
than reset them altogether.

Does anyone else know what values I would need to use for user and
domain in the PermissionEx element to get permissions assigned to that
directory for NT AUTHORITY\NETWORK SERVICE?

Just as an FYI, I am using wix v3 and I have tried empty domain with
Network Service based on Ian's suggestion and empty domain with
NetworkService based on several other postings on this site to no
avail.  Is anyone else able to get this to work?

Thanks in advance for anyone that can help me.

-Original Message-
From: Ian Elliott (Excell Data Corporation)
[mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 21, 2008 11:54 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] grant permissions on a folder to a specific
user if the user happens to be NT AUTHORITY\Network Service

Here is code from an installer I have that works for me:

Component Id=CID_Logs Guid={837A1B74-98C9-4042-B51D-58F38448CE46}
Location=local DiskId=1
CreateFolder
Permission GenericAll=yes User=Administrators /
Permission GenericRead=yes GenericWrite=yes User=Network Service
/
/CreateFolder
/Component


-Original Message-
From: Amy Rosewater [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 21, 2008 10:44 AM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] grant permissions on a folder to a specific user if
the user happens to be NT AUTHORITY\Network Service

Hi All,



How do you grant permissions to a folder for a specific user if the user
happens to be the built in Network Service account?



I have tried:



Component Id=AssignDataDirectoryPermissionsGeneric
Guid=5A9D6D2B-CBA0-4E4C-8935-FACA2446256E

CreateFolder Directory=DataDirectory

util:PermissionEx CreateFile=yes GenericAll=yes Read=yes
ReadAttributes=yes WriteAttributes=yes User=NetworkService /

/CreateFolder

/Component



Component Id=AssignDataDirectoryPermissionsGeneric
Guid=5A9D6D2B-CBA0-4E4C-8935-FACA2446256E

CreateFolder Directory=DataDirectory

util:PermissionEx CreateFile=yes GenericAll=yes Read=yes
ReadAttributes=yes WriteAttributes=yes User=[SQLSERVERSERVICEUSER]
/

/CreateFolder

/Component



In this scenario SQLSERVERSERVICEUSER is equal to NT AUTHORITY\Network
Service.



Component Id=AssignDataDirectoryPermissionsGeneric
Guid=5A9D6D2B-CBA0-4E4C-8935-FACA2446256E

CreateFolder Directory=DataDirectory

util:PermissionEx CreateFile=yes GenericAll=yes Read=yes
ReadAttributes=yes WriteAttributes=yes
Domain=[SQLSERVERSERVICEDOMAIN] User=[SQLSERVERSERVICEUSER] /

/CreateFolder

/Component



In this scenario SQLSERVERSERVICEDOMAIN = NT AUTHORITY and
SQLSERVERSERVICEUSER = Network Service.



Component Id=AssignDataDirectoryPermissionsGeneric
Guid=5A9D6D2B-CBA0-4E4C-8935-FACA2446256E

CreateFolder Directory=DataDirectory

util:PermissionEx CreateFile=yes GenericAll=yes Read=yes
ReadAttributes=yes WriteAttributes=yes Domain=[ComputerName]
User=[SQLSERVERSERVICEUSER] /

/CreateFolder

/Component



In this scenario SQLSERVERSERVICEUSER = NT AUTHORITY\Network Service


Rather than just keep trying, does anyone know the answer to this one?



Thanks,



Amy



Amy Rosewater

SPECTRUM Human Resource Systems Corporation

707 17th Street Suite 3800

Denver CO, 80202

303.592.3403

[EMAIL PROTECTED]




-
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK  win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the
world
http://moblin-contest.org/redirect.php?banner_id=100url=/

Re: [WiX-users] ASP.NET on IIS

[Chad Petersen]

I'll throw this out as an option I have been using since we converted to
.NET 2.0. No calls on it, so I have to assumje it is working great. All
it does is set ASPNET 2.0 as the version on the ASP.NET tab in IIS. We
require 2.0 to be installed prior to running our installer. I gather the
[SITE_ID] during the UI sequence.

CustomAction Id=ASPNET_REGIIS_PATH Property=ASPNET_REGIIS_PATH
Value=[DOTNET20PATH]v2.0.50727/
CustomAction Id=ASPNET_REGIIS_SET
Property=ASPNET_REGIIS_SET
Value=quot;[ASPNET_REGIIS_PATH]\ASPNET_REGIIS.exequot; -sn
W3SVC/[SITE_ID]/Root/E3Container HideTarget=yes/
CustomAction Id=caASPNET_REGIIS_SET Execute=deferred
Return=check ExeCommand=[ASPNET_REGIIS_SET] Directory=TARGETDIR/

-Original Message-
From: Eitan Behar [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, October 22, 2008 9:10 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] ASP.NET on IIS

Thanks Siv,

But, this way I need to define every extension, is there a way that I
can
tell WIX to change ONLY the default extensions, similar of when doing it
from IIS' GUI (on the ASP.NET tab).

Regards,

Eitan




On Wed, Oct 22, 2008 at 4:22 PM, Kalvagadda, SivaKrishna (MLX
Technology) 
[EMAIL PROTECTED] wrote:

 This is how ssearch for t he verion of installed framework
 Property Id=ASPNETISAPIDLL
  DirectorySearch Id =AspnetIsapiDll
 Path=[WindowsFolder]Microsoft.NET\Framework Depth=1
FileSearch Id=AspnetIsapiDll LongName=aspnet_isapi.dll
 MinVersion=2.0 MaxVersion=3.5 /
  /DirectorySearch
/Property

 iis:WebApplicationExtension Extension=ascx CheckPath=yes
 Script=yes Executable=[ASPNETISAPIDLL]  Verbs=GET,HEAD,POST /
  iis:WebApplicationExtension Extension=ashx
 CheckPath=no Script=yes Executable=[ASPNETISAPIDLL]
 Verbs=GET,HEAD,POST /
  iis:WebApplicationExtension Extension=asmx
 CheckPath=no Script=yes Executable=[ASPNETISAPIDLL]
 Verbs=GET,HEAD,POST /

 Regards,
 SivaKrishna Kalvagadda,
 201-671-5552.

 -Original Message-
 From: Eitan Behar [mailto:[EMAIL PROTECTED]
 Sent: Wednesday, October 22, 2008 4:54 AM
 To: General discussion for Windows Installer XML toolset.
 Subject: [WiX-users] ASP.NET http://asp.net/ on IIS

 Hi,

 Please, how can I set the ASP.NET http://asp.net/ version for a Web
Site
 ? I just want
 to
 set the general selection on the ASP.NET http://asp.net/ tab, and
leave
 the default
 extensions as they are.

 Thanks,

 Eitan


 -
 This SF.Net email is sponsored by the Moblin Your Move Developer's
 challenge
 Build the coolest Linux based applications with Moblin SDK  win great
 prizes
 Grand prize is a trip for two to an Open Source event anywhere in the
 world
 http://moblin-contest.org/redirect.php?banner_id=100url=/
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users
 

 This message w/attachments (message) may be privileged, confidential
or
 proprietary, and if you are not an intended recipient, please notify
the
 sender, do not use or share it and delete it. Unless specifically
indicated,
 this message is not an offer to sell or a solicitation of any
investment
 products or other financial product or service, an official
confirmation of
 any transaction, or an official statement of Merrill Lynch. Subject to
 applicable law, Merrill Lynch may monitor, review and retain
 e-communications (EC) traveling through its networks/systems. The laws
of
 the country of each sender/recipient may impact the handling of EC,
and EC
 may be archived, supervised and produced in countries other than the
country
 in which you are located. This message cannot be guaranteed to be
secure or
 error-free. This message is subject to terms available at the
following
 link: http://www.ml.com/e-communications_terms/. By messaging with
Merrill
 Lynch you consent to the foregoing.
 



-
 This SF.Net email is sponsored by the Moblin Your Move Developer's
 challenge
 Build the coolest Linux based applications with Moblin SDK  win great
 prizes
 Grand prize is a trip for two to an Open Source event anywhere in the
world
 http://moblin-contest.org/redirect.php?banner_id=100url=/
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users


-
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK  win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the
world

Re: [WiX-users] ASP.NET on IIS

[Luke Bakken]

 But, this way I need to define every extension, is there a way that I can
 tell WIX to change ONLY the default extensions, similar of when doing it
 from IIS' GUI (on the ASP.NET tab).

There aren't that many extensions ... I would just enumerate them all.

-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK  win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Bug in x64 build of WiX UtilExtension?

[Brian Rogers]

Hmm, I guess there is no straightforward way to edit existing values in an XML 
file with XmlConfig.  As you mention, if it were possible, it would make it 
hard to rollback changes if something goes wrong (it would somehow have to read 
and store the original value so it could be reverted later).

I guess you'll have to use XmlFile if you want to do that.  I don't think 
you'll be able to rollback/uninstall the change unless you write a custom 
action doing what I describe above (reading the original value and saving it 
off somewhere).

That WOW64 message is not an error.  From the WiX source code:

// If we fail, log the error but proceed, because we may not need a 
particular function, or the Wow64 API at all
if (!s_pfnDisableWow64)
{
WcaLog(LOGMSG_STANDARD, Found Wow64 API, but unable to link to 
Wow64DisableWow64FsRedirection function in kernel32.dll);
}

XmlConfig cannot vary due to any .NET Framework version because it is a C++ 
custom action with no .NET dependencies.

##
$_='^#(/||/@[EMAIL PROTECTED]@:^[-['^;@@@\\])@..
{)/];)^{;$,+=(++$,);$_.=$,;`$_`;


-Original Message-
From: Joel Paula (hotmail) [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 22, 2008 9:27 AM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Bug in x64 build of WiX UtilExtension?

Brian,

XmlConfig only allows for adding or deleting elements.
I understand this is more straightforward when you want to rollback.

How do you edit an XML file?
XmlFile seemed to be the thing to use, but it always throws the error  
ExecXmlFile:  Found Wow64 API, but unable to link to 
Wow64DisableWow64FsRedirection function in kernel32.dll, no matter what I try 
to feed it.
Is it a bug and should we file a bug, or are we doing something wrong?

By the way, the example you give produces a value attribute on the 
/IESInterface/IESveLocation node when I build and run it. Is there anything 
that may influence how it works, depending on the machine or the .Net framework 
version?
I had to use something like:
util:XmlConfig Id=AddVELocation
File=[#IESveInterfaceParameters.xml]
Action=create
ElementPath=/IESInterface 
Name=IESveLocation
Node=element
Value=[VE59LOCATION]apps/

Thanks for your help.

Joel Paula


-Original Message-
From: Brian Rogers [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 22, 2008 4:47 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Bug in x64 build of WiX UtilExtension?

I'd recommend using XmlConfig instead of XmlFile.  The following should achieve 
what you want:

util:XmlConfig Id=updateVELocation
File=[#IESveInterfaceParameters.xml]
Action=create
On=install
ElementPath=/IESInterface/IESveLocation
Node=value
Value=[VE59LOCATION]apps /

This blog post has some more examples of using XmlConfig: 
http://blogs.msdn.com/gisenberg/archive/2007/10/09/wix-v3-and-xmlconfig-xmlfile-troubleshooting.aspx


##
$_='^#(/||/@[EMAIL PROTECTED]@:^[-['^;@@@\\])@..
{)/];)^{;$,+=(++$,);$_.=$,;`$_`;


-Original Message-
From: Pally Sandher [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 22, 2008 6:12 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Bug in x64 build of WiX UtilExtension?

I'm trying to use util:XMLFile to modify the inner text of a tag in an XML file 
during installation which is installed by my MSI for one of our plug-ins.

The XML file is named IESveInterfaceParameters.xml and contains the following 
code:

?xml version='1.0'?
IESInterface
  IESveLocationM:\IES\apps /IESveLocation
  OutputveXMLLocation /OutputveXMLLocation
  Preferences city='Boulder (CO)' latitude='40.017' minimumFloorArea='0.0' 
buildingAreaType='Office' thinWalls='1' 
buildingRoomService='VariableRefrigerantFlow' 
verticalHorizontalElementTransitionAngle='45.0' 
adjacencySeparationDistance='0.9144923921' longitude='-105.283' 
diagnosticAids='no' minimumRoomHeight='0.0'/
/IESInterface

My installer code is as follows:

Component Id=Dialogs DiskId=1 Guid=myguid
...
  File Id=IESveInterfaceParameters.xml Name=IESveInterfaceParameters.xml 
Source=..\..\..\code\Sketchup\Plugins\IESLink\Dialogs\IESveInterfaceParameters.xml
 /
...
  util:XmlFile Id=updateVELocation Action=setValue 
File=[#IESveInterfaceParameters.xml] Value=[VE59LOCATION]apps 
ElementPath=/IESInterface/IESveLocation SelectionLanguage=XPath /
/Component


All the above code is supposed to do is replace the inner text of the 
IESveLocation tag. Unfortunately the documentation for util:XMLFile leaves a 
lot to be desired so it doesn't work as yet (back to good old trial  error 
again). Any help would be appreciated however this isn't what I'm referring to 
as a bug.

The machine that I use to build my MSIs runs XP64. I install the 

Re: [WiX-users] Bug in x64 build of WiX UtilExtension?

[Rob Mensching]

XmlConfig *can* edit existing XML files and on rollback it reverts any changes 
it makes.  XmlFile does not have those capabilities.

-Original Message-
From: Brian Rogers [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 22, 2008 09:42
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Bug in x64 build of WiX UtilExtension?

Hmm, I guess there is no straightforward way to edit existing values in an XML 
file with XmlConfig.  As you mention, if it were possible, it would make it 
hard to rollback changes if something goes wrong (it would somehow have to read 
and store the original value so it could be reverted later).

I guess you'll have to use XmlFile if you want to do that.  I don't think 
you'll be able to rollback/uninstall the change unless you write a custom 
action doing what I describe above (reading the original value and saving it 
off somewhere).

That WOW64 message is not an error.  From the WiX source code:

// If we fail, log the error but proceed, because we may not need a 
particular function, or the Wow64 API at all
if (!s_pfnDisableWow64)
{
WcaLog(LOGMSG_STANDARD, Found Wow64 API, but unable to link to 
Wow64DisableWow64FsRedirection function in kernel32.dll);
}

XmlConfig cannot vary due to any .NET Framework version because it is a C++ 
custom action with no .NET dependencies.

##
$_='^#(/||/@[EMAIL PROTECTED]@:^[-['^;@@@\\])@..
{)/];)^{;$,+=(++$,);$_.=$,;`$_`;


-Original Message-
From: Joel Paula (hotmail) [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 22, 2008 9:27 AM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Bug in x64 build of WiX UtilExtension?

Brian,

XmlConfig only allows for adding or deleting elements.
I understand this is more straightforward when you want to rollback.

How do you edit an XML file?
XmlFile seemed to be the thing to use, but it always throws the error  
ExecXmlFile:  Found Wow64 API, but unable to link to 
Wow64DisableWow64FsRedirection function in kernel32.dll, no matter what I try 
to feed it.
Is it a bug and should we file a bug, or are we doing something wrong?

By the way, the example you give produces a value attribute on the 
/IESInterface/IESveLocation node when I build and run it. Is there anything 
that may influence how it works, depending on the machine or the .Net framework 
version?
I had to use something like:
util:XmlConfig Id=AddVELocation
File=[#IESveInterfaceParameters.xml]
Action=create
ElementPath=/IESInterface 
Name=IESveLocation
Node=element
Value=[VE59LOCATION]apps/

Thanks for your help.

Joel Paula


-Original Message-
From: Brian Rogers [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 22, 2008 4:47 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Bug in x64 build of WiX UtilExtension?

I'd recommend using XmlConfig instead of XmlFile.  The following should achieve 
what you want:

util:XmlConfig Id=updateVELocation
File=[#IESveInterfaceParameters.xml]
Action=create
On=install
ElementPath=/IESInterface/IESveLocation
Node=value
Value=[VE59LOCATION]apps /

This blog post has some more examples of using XmlConfig: 
http://blogs.msdn.com/gisenberg/archive/2007/10/09/wix-v3-and-xmlconfig-xmlfile-troubleshooting.aspx


##
$_='^#(/||/@[EMAIL PROTECTED]@:^[-['^;@@@\\])@..
{)/];)^{;$,+=(++$,);$_.=$,;`$_`;


-Original Message-
From: Pally Sandher [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 22, 2008 6:12 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Bug in x64 build of WiX UtilExtension?

I'm trying to use util:XMLFile to modify the inner text of a tag in an XML file 
during installation which is installed by my MSI for one of our plug-ins.

The XML file is named IESveInterfaceParameters.xml and contains the following 
code:

?xml version='1.0'?
IESInterface
  IESveLocationM:\IES\apps /IESveLocation
  OutputveXMLLocation /OutputveXMLLocation
  Preferences city='Boulder (CO)' latitude='40.017' minimumFloorArea='0.0' 
buildingAreaType='Office' thinWalls='1' 
buildingRoomService='VariableRefrigerantFlow' 
verticalHorizontalElementTransitionAngle='45.0' 
adjacencySeparationDistance='0.9144923921' longitude='-105.283' 
diagnosticAids='no' minimumRoomHeight='0.0'/
/IESInterface

My installer code is as follows:

Component Id=Dialogs DiskId=1 Guid=myguid
...
  File Id=IESveInterfaceParameters.xml Name=IESveInterfaceParameters.xml 
Source=..\..\..\code\Sketchup\Plugins\IESLink\Dialogs\IESveInterfaceParameters.xml
 /
...
  util:XmlFile Id=updateVELocation Action=setValue 
File=[#IESveInterfaceParameters.xml] Value=[VE59LOCATION]apps 
ElementPath=/IESInterface/IESveLocation SelectionLanguage=XPath /
/Component


All the 

Re: [WiX-users] grant permissions on a folder to a specific userifthe user happens to be NT AUTHORITY\Network Service

[Rob Mensching]

What does a verbose log file say?

-Original Message-
From: Amy Rosewater [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 22, 2008 09:31
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] grant permissions on a folder to a specific userifthe 
user happens to be NT AUTHORITY\Network Service

That was a great idea Michael, and I tried it but the PermissionEx
element is still failing to add the appropriate permissions to the
directory.  Now instead of failing to add permissions for Network
Service it fails to add permissions for the IIS_WPG.

Is anyone else having a similar problems with wix v3.0.4513?

A

-Original Message-
From: Michael Osmond [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 21, 2008 11:38 PM
To: General discussion for Windows Installer XML toolset.; General
discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] grant permissions on a folder to a specific
userifthe user happens to be NT AUTHORITY\Network Service

Hello Amy,

I actually use [ComputerName]\iis_wpg this is IIS Working Process
Group of which network service is a member.  Although that said, this
group only exists if  IIS is an installed windows component.   This
covers, system, network service, local service and I think Aspnet.

Michael



From: Amy Rosewater [mailto:[EMAIL PROTECTED]
Sent: Wed 22/10/2008 1:29 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] grant permissions on a folder to a specific
user ifthe user happens to be NT AUTHORITY\Network Service



Thanks Ian, but I need to add to permissions on the directory rather
than reset them altogether.

Does anyone else know what values I would need to use for user and
domain in the PermissionEx element to get permissions assigned to that
directory for NT AUTHORITY\NETWORK SERVICE?

Just as an FYI, I am using wix v3 and I have tried empty domain with
Network Service based on Ian's suggestion and empty domain with
NetworkService based on several other postings on this site to no
avail.  Is anyone else able to get this to work?

Thanks in advance for anyone that can help me.

-Original Message-
From: Ian Elliott (Excell Data Corporation)
[mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 21, 2008 11:54 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] grant permissions on a folder to a specific
user if the user happens to be NT AUTHORITY\Network Service

Here is code from an installer I have that works for me:

Component Id=CID_Logs Guid={837A1B74-98C9-4042-B51D-58F38448CE46}
Location=local DiskId=1
CreateFolder
Permission GenericAll=yes User=Administrators /
Permission GenericRead=yes GenericWrite=yes User=Network Service
/
/CreateFolder
/Component


-Original Message-
From: Amy Rosewater [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 21, 2008 10:44 AM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] grant permissions on a folder to a specific user if
the user happens to be NT AUTHORITY\Network Service

Hi All,



How do you grant permissions to a folder for a specific user if the user
happens to be the built in Network Service account?



I have tried:



Component Id=AssignDataDirectoryPermissionsGeneric
Guid=5A9D6D2B-CBA0-4E4C-8935-FACA2446256E

CreateFolder Directory=DataDirectory

util:PermissionEx CreateFile=yes GenericAll=yes Read=yes
ReadAttributes=yes WriteAttributes=yes User=NetworkService /

/CreateFolder

/Component



Component Id=AssignDataDirectoryPermissionsGeneric
Guid=5A9D6D2B-CBA0-4E4C-8935-FACA2446256E

CreateFolder Directory=DataDirectory

util:PermissionEx CreateFile=yes GenericAll=yes Read=yes
ReadAttributes=yes WriteAttributes=yes User=[SQLSERVERSERVICEUSER]
/

/CreateFolder

/Component



In this scenario SQLSERVERSERVICEUSER is equal to NT AUTHORITY\Network
Service.



Component Id=AssignDataDirectoryPermissionsGeneric
Guid=5A9D6D2B-CBA0-4E4C-8935-FACA2446256E

CreateFolder Directory=DataDirectory

util:PermissionEx CreateFile=yes GenericAll=yes Read=yes
ReadAttributes=yes WriteAttributes=yes
Domain=[SQLSERVERSERVICEDOMAIN] User=[SQLSERVERSERVICEUSER] /

/CreateFolder

/Component



In this scenario SQLSERVERSERVICEDOMAIN = NT AUTHORITY and
SQLSERVERSERVICEUSER = Network Service.



Component Id=AssignDataDirectoryPermissionsGeneric
Guid=5A9D6D2B-CBA0-4E4C-8935-FACA2446256E

CreateFolder Directory=DataDirectory

util:PermissionEx CreateFile=yes GenericAll=yes Read=yes
ReadAttributes=yes WriteAttributes=yes Domain=[ComputerName]
User=[SQLSERVERSERVICEUSER] /

/CreateFolder

/Component



In this scenario SQLSERVERSERVICEUSER = NT AUTHORITY\Network Service


Rather than just keep trying, does anyone know the answer to this one?



Thanks,



Amy



Amy Rosewater

SPECTRUM Human Resource Systems Corporation

707 17th Street Suite 3800

Denver CO, 80202

303.592.3403

[EMAIL PROTECTED]

Re: [WiX-users] ASP.NET on IIS

[Eitan Behar]

Well, the issue is that I have several setups which have a few Web
Applications each, and each one is supported by a different team, therefore
I wanted something easy to tell everyone to do



-Original Message-
From: Luke Bakken [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, October 22, 2008 6:36 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] ASP.NET on IIS

 But, this way I need to define every extension, is there a way that I can
 tell WIX to change ONLY the default extensions, similar of when doing it
 from IIS' GUI (on the ASP.NET tab).

There aren't that many extensions ... I would just enumerate them all.

-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK  win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK  win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Candle/Light output to output window within dev studio?

[Brian Gillespie]

Hi,

We automate our daily builds by running devenv on the command line 
(instead of using MsBuild, because it looks like a big learning curve). 
For example:

devenve.exe /build Beta_EN|x64 /project MyProj.wixproj /out MyProj.log

We've got a lot of WiX source files in our installers, and we've got 
dozens of configurations, so running candle and light from a script and 
also maintaining a project for votive seems error prone.

WiX works just fine this way, except that we get no errors and warnings 
in the standard output (the output window when running dev studio GUI). 
This means that logging of WiX errors and warnings are not working.

Is there a switch to display errors and warnings in both the output 
window and the Errors/Warnings pane?

Or is there a better way for me to do this?
 
  - Brian

Brian Gillespie
Rhinoceros Development | Robert McNeel  Associates | 
http://www.rhino3d.com

/In theory, there is no difference between theory and practice. But, in 
practice, there is./
-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK  win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Getting Error LGHT0102

[Sandeep Gautam (HCL Technologies Ltd)]

Hi Runnning Light command from command line, I am getting LGHT0102 error .
Please find the error:

c:\delivery\dev\wix\src\ext\sqlextension\wixlib\sqlextension.wxs(18) : error 
LGHT0102 : The localization variable !(loc.ConfigureSql) is unknown.  Please 
ensure the variable is defined.

Please help me out what I am doing wrong.

Regards
Sandeep

-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK  win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Bug in x64 build of WiX UtilExtension?

[Brian Rogers]

I think the problem here is that there is no corresponding uninstall action 
for an operation like the following:

util:XmlConfig Id=AddElementText
File=[SOMEEXISTINGFILE]
Action=create
ElementPath=/someElement
Node=value
Value=NEW TEXT
On=install
Sequence=1 /

(Sample text for SOMEEXISTINGFILE:)

?xml version=1.0 encoding=utf-8?
someElementORIGINAL TEXT, THIS COULD BE ANYTHING/someElement

I do see that rollback works in the case of a problem during installation (I 
just tested it and it reverted to the original file).  Uninstall seems 
trickier, and I can't think of a way to do this without resorting to a 
user-defined custom action (e.g. backing up the file before changing it and 
restoring it on uninstall).

##
$_='^#(/||/@[EMAIL PROTECTED]@:^[-['^;@@@\\])@..
{)/];)^{;$,+=(++$,);$_.=$,;`$_`;


-Original Message-
From: Rob Mensching [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 22, 2008 10:09 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Bug in x64 build of WiX UtilExtension?

XmlConfig *can* edit existing XML files and on rollback it reverts any changes 
it makes.  XmlFile does not have those capabilities.

-Original Message-
From: Brian Rogers [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 22, 2008 09:42
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Bug in x64 build of WiX UtilExtension?

Hmm, I guess there is no straightforward way to edit existing values in an XML 
file with XmlConfig.  As you mention, if it were possible, it would make it 
hard to rollback changes if something goes wrong (it would somehow have to read 
and store the original value so it could be reverted later).

I guess you'll have to use XmlFile if you want to do that.  I don't think 
you'll be able to rollback/uninstall the change unless you write a custom 
action doing what I describe above (reading the original value and saving it 
off somewhere).

That WOW64 message is not an error.  From the WiX source code:

// If we fail, log the error but proceed, because we may not need a 
particular function, or the Wow64 API at all
if (!s_pfnDisableWow64)
{
WcaLog(LOGMSG_STANDARD, Found Wow64 API, but unable to link to 
Wow64DisableWow64FsRedirection function in kernel32.dll);
}

XmlConfig cannot vary due to any .NET Framework version because it is a C++ 
custom action with no .NET dependencies.

##
$_='^#(/||/@[EMAIL PROTECTED]@:^[-['^;@@@\\])@..
{)/];)^{;$,+=(++$,);$_.=$,;`$_`;


-Original Message-
From: Joel Paula (hotmail) [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 22, 2008 9:27 AM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Bug in x64 build of WiX UtilExtension?

Brian,

XmlConfig only allows for adding or deleting elements.
I understand this is more straightforward when you want to rollback.

How do you edit an XML file?
XmlFile seemed to be the thing to use, but it always throws the error  
ExecXmlFile:  Found Wow64 API, but unable to link to 
Wow64DisableWow64FsRedirection function in kernel32.dll, no matter what I try 
to feed it.
Is it a bug and should we file a bug, or are we doing something wrong?

By the way, the example you give produces a value attribute on the 
/IESInterface/IESveLocation node when I build and run it. Is there anything 
that may influence how it works, depending on the machine or the .Net framework 
version?
I had to use something like:
util:XmlConfig Id=AddVELocation
File=[#IESveInterfaceParameters.xml]
Action=create
ElementPath=/IESInterface 
Name=IESveLocation
Node=element
Value=[VE59LOCATION]apps/

Thanks for your help.

Joel Paula


-Original Message-
From: Brian Rogers [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 22, 2008 4:47 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Bug in x64 build of WiX UtilExtension?

I'd recommend using XmlConfig instead of XmlFile.  The following should achieve 
what you want:

util:XmlConfig Id=updateVELocation
File=[#IESveInterfaceParameters.xml]
Action=create
On=install
ElementPath=/IESInterface/IESveLocation
Node=value
Value=[VE59LOCATION]apps /

This blog post has some more examples of using XmlConfig: 
http://blogs.msdn.com/gisenberg/archive/2007/10/09/wix-v3-and-xmlconfig-xmlfile-troubleshooting.aspx


##
$_='^#(/||/@[EMAIL PROTECTED]@:^[-['^;@@@\\])@..
{)/];)^{;$,+=(++$,);$_.=$,;`$_`;


-Original Message-
From: Pally Sandher [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 22, 2008 6:12 AM
To: wix-users@lists.sourceforge.net
Subject: 

Re: [WiX-users] Candle/Light output to output window within dev studio?

[Brian Rogers]

MSBuild actually integrates quite nicely with VS projects and solutions.  Using 
your example below, you should be able to do this:

  MSBuild.exe /p:Configuration=Beta_EN /p:Platform=x64 MyProj.wixproj

You should be able to do this for any SLN file, in fact... it generally just 
works.

##
$_='^#(/||/@[EMAIL PROTECTED]@:^[-['^;@@@\\])@..
{)/];)^{;$,+=(++$,);$_.=$,;`$_`;


-Original Message-
From: Brian Gillespie [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 22, 2008 10:50 AM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Candle/Light output to output window within dev studio?

Hi,

We automate our daily builds by running devenv on the command line
(instead of using MsBuild, because it looks like a big learning curve).
For example:

devenve.exe /build Beta_EN|x64 /project MyProj.wixproj /out MyProj.log

We've got a lot of WiX source files in our installers, and we've got
dozens of configurations, so running candle and light from a script and
also maintaining a project for votive seems error prone.

WiX works just fine this way, except that we get no errors and warnings
in the standard output (the output window when running dev studio GUI).
This means that logging of WiX errors and warnings are not working.

Is there a switch to display errors and warnings in both the output
window and the Errors/Warnings pane?

Or is there a better way for me to do this?

  - Brian

Brian Gillespie
Rhinoceros Development | Robert McNeel  Associates |
http://www.rhino3d.com

/In theory, there is no difference between theory and practice. But, in
practice, there is./
-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK  win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK  win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Bug in x64 build of WiX UtilExtension?

[Rob Mensching]

XmlConfig does not automatically create an uninstall step for you.  That's why 
there is the On attribute.  You get to specify what you want to have happen 
on uninstall.  Much like SQL Strings/Scripts.

-Original Message-
From: Brian Rogers [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 22, 2008 10:52
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Bug in x64 build of WiX UtilExtension?

I think the problem here is that there is no corresponding uninstall action 
for an operation like the following:

util:XmlConfig Id=AddElementText
File=[SOMEEXISTINGFILE]
Action=create
ElementPath=/someElement
Node=value
Value=NEW TEXT
On=install
Sequence=1 /

(Sample text for SOMEEXISTINGFILE:)

?xml version=1.0 encoding=utf-8?
someElementORIGINAL TEXT, THIS COULD BE ANYTHING/someElement

I do see that rollback works in the case of a problem during installation (I 
just tested it and it reverted to the original file).  Uninstall seems 
trickier, and I can't think of a way to do this without resorting to a 
user-defined custom action (e.g. backing up the file before changing it and 
restoring it on uninstall).

##
$_='^#(/||/@[EMAIL PROTECTED]@:^[-['^;@@@\\])@..
{)/];)^{;$,+=(++$,);$_.=$,;`$_`;


-Original Message-
From: Rob Mensching [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 22, 2008 10:09 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Bug in x64 build of WiX UtilExtension?

XmlConfig *can* edit existing XML files and on rollback it reverts any changes 
it makes.  XmlFile does not have those capabilities.

-Original Message-
From: Brian Rogers [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 22, 2008 09:42
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Bug in x64 build of WiX UtilExtension?

Hmm, I guess there is no straightforward way to edit existing values in an XML 
file with XmlConfig.  As you mention, if it were possible, it would make it 
hard to rollback changes if something goes wrong (it would somehow have to read 
and store the original value so it could be reverted later).

I guess you'll have to use XmlFile if you want to do that.  I don't think 
you'll be able to rollback/uninstall the change unless you write a custom 
action doing what I describe above (reading the original value and saving it 
off somewhere).

That WOW64 message is not an error.  From the WiX source code:

// If we fail, log the error but proceed, because we may not need a 
particular function, or the Wow64 API at all
if (!s_pfnDisableWow64)
{
WcaLog(LOGMSG_STANDARD, Found Wow64 API, but unable to link to 
Wow64DisableWow64FsRedirection function in kernel32.dll);
}

XmlConfig cannot vary due to any .NET Framework version because it is a C++ 
custom action with no .NET dependencies.

##
$_='^#(/||/@[EMAIL PROTECTED]@:^[-['^;@@@\\])@..
{)/];)^{;$,+=(++$,);$_.=$,;`$_`;


-Original Message-
From: Joel Paula (hotmail) [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 22, 2008 9:27 AM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Bug in x64 build of WiX UtilExtension?

Brian,

XmlConfig only allows for adding or deleting elements.
I understand this is more straightforward when you want to rollback.

How do you edit an XML file?
XmlFile seemed to be the thing to use, but it always throws the error  
ExecXmlFile:  Found Wow64 API, but unable to link to 
Wow64DisableWow64FsRedirection function in kernel32.dll, no matter what I try 
to feed it.
Is it a bug and should we file a bug, or are we doing something wrong?

By the way, the example you give produces a value attribute on the 
/IESInterface/IESveLocation node when I build and run it. Is there anything 
that may influence how it works, depending on the machine or the .Net framework 
version?
I had to use something like:
util:XmlConfig Id=AddVELocation
File=[#IESveInterfaceParameters.xml]
Action=create
ElementPath=/IESInterface 
Name=IESveLocation
Node=element
Value=[VE59LOCATION]apps/

Thanks for your help.

Joel Paula


-Original Message-
From: Brian Rogers [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 22, 2008 4:47 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Bug in x64 build of WiX UtilExtension?

I'd recommend using XmlConfig instead of XmlFile.  The following should achieve 
what you want:

util:XmlConfig Id=updateVELocation
File=[#IESveInterfaceParameters.xml]
Action=create
On=install
ElementPath=/IESInterface/IESveLocation
Node=value
Value=[VE59LOCATION]apps /

This blog 

Re: [WiX-users] Candle/Light output to output window within dev studio?

[Brian Gillespie]

Thanks Brian, I'll give it a shot.

OT:
Nice sig, though I admit hoping for more of an easter egg after running 
it through the interpreter :)
Is this stunnix output?
 
  - Brian

Brian Gillespie
Rhinoceros Development | Robert McNeel  Associates | 
http://www.rhino3d.com

/In theory, there is no difference between theory and practice. But, in 
practice, there is./

Brian Rogers wrote:
 MSBuild actually integrates quite nicely with VS projects and solutions.  
 Using your example below, you should be able to do this:

   MSBuild.exe /p:Configuration=Beta_EN /p:Platform=x64 MyProj.wixproj

 You should be able to do this for any SLN file, in fact... it generally just 
 works.

 ##
 $_='^#(/||/@[EMAIL PROTECTED]@:^[-['^;@@@\\])@..
 {)/];)^{;$,+=(++$,);$_.=$,;`$_`;


 -Original Message-
 From: Brian Gillespie [mailto:[EMAIL PROTECTED]
 Sent: Wednesday, October 22, 2008 10:50 AM
 To: General discussion for Windows Installer XML toolset.
 Subject: [WiX-users] Candle/Light output to output window within dev studio?

 Hi,

 We automate our daily builds by running devenv on the command line
 (instead of using MsBuild, because it looks like a big learning curve).
 For example:

 devenve.exe /build Beta_EN|x64 /project MyProj.wixproj /out MyProj.log

 We've got a lot of WiX source files in our installers, and we've got
 dozens of configurations, so running candle and light from a script and
 also maintaining a project for votive seems error prone.

 WiX works just fine this way, except that we get no errors and warnings
 in the standard output (the output window when running dev studio GUI).
 This means that logging of WiX errors and warnings are not working.

 Is there a switch to display errors and warnings in both the output
 window and the Errors/Warnings pane?

 Or is there a better way for me to do this?

   - Brian

 Brian Gillespie
 Rhinoceros Development | Robert McNeel  Associates |
 http://www.rhino3d.com

 /In theory, there is no difference between theory and practice. But, in
 practice, there is./
 -
 This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
 Build the coolest Linux based applications with Moblin SDK  win great prizes
 Grand prize is a trip for two to an Open Source event anywhere in the world
 http://moblin-contest.org/redirect.php?banner_id=100url=/
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users


 -
 This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
 Build the coolest Linux based applications with Moblin SDK  win great prizes
 Grand prize is a trip for two to an Open Source event anywhere in the world
 http://moblin-contest.org/redirect.php?banner_id=100url=/
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users
   
-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK  win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Getting Error LGHT0102

[Joel Paula (hotmail)]

This probably happens because you are trying to build a culture other then
en-us.
Get WiX source code, go to folder \src\ext\SqlExtension\wixlib\ and get the
en-us.wxl language file. Make a copy of it, but translated to the culture
you are using, and include it in your project.


Joel Paula



-Original Message-
From: Sandeep Gautam (HCL Technologies Ltd) [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, October 22, 2008 6:52 PM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Getting Error LGHT0102

Hi Runnning Light command from command line, I am getting LGHT0102 error .
Please find the error:

c:\delivery\dev\wix\src\ext\sqlextension\wixlib\sqlextension.wxs(18) : error
LGHT0102 : The localization variable !(loc.ConfigureSql) is unknown.  Please
ensure the variable is defined.

Please help me out what I am doing wrong.

Regards
Sandeep




-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK  win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Torch generating mst with cabs question

[Michael Ballou]

I have two MSI's built with Wix that are the same except one MSI has a
couple extra files in it.  The extra files are stored in a separate .cab
file embedded in the MSI.  All cabs are embedded in the MSI's.

 

I then use torch.exe to generate an MST file so that I can later
transform the smaller install to the large one.  The problem is that
torch doesn't seem to be including the extra embedded cab file.  The
transform is very small (6K), and when I apply it to the small MSI and
run it, I get an Internal Error 2356 for the missing cab file.

 

I was previously building the MSI's with Wise for Windows Installer
which embeds the cabs in the Cabs table.  Using torch on those MSI's
would give me the desired result.  However the Wix generated MSI doesn't
have the Cabs table since the cabs are embedded in the _Streams which
doesn't seem to be detected by Torch.

 

I tried some different parameters to Torch but nothing seemed to give me
what I want. Am I missing something?

 

Thanks,

Mike Ballou

 

 

 

-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK  win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Recent WIX sources will not build

[Neil Sleightholm]

I think I have figured this out, if you run the shortcut that VS2008
sets up Visual Studio 2008 Command Prompt (C:\Program Files\Microsoft
Visual Studio 9.0\VC\vcvarsall.bat x86) it doesn't include the
framework in the path. But if you run %VS90COMNTOOLS%\vsvars32.bat or
the Visual Studio 2005 Command Prompt shortcut it does setup the
framework path.

Neil

-Original Message-
From: Neil Sleightholm [mailto:[EMAIL PROTECTED] 
Sent: 22 October 2008 08:01
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Recent WIX sources will not build

That is what I thought, it worked on my Vista machine but not on a clean
build of 2008. I was calling %VS90COMNTOOLS%\vsvars.bat but it still
didn't set the path, I'll have to check what is different on my build
machine.
 
Neil
 
Neil Sleightholm
X2 Systems Limited
[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] 
 



From: Bob Arnson [mailto:[EMAIL PROTECTED]
Sent: Wed 22/10/2008 05:02
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Recent WIX sources will not build



Neil Sleightholm wrote:
 I have found a solution to the error: 
 src\dtf\tools\sfxca\precomp.h(32)
 : fatal error C1083: Cannot open type library file: 'mscorlib.tlb': No

 such file or directory.

 If you add C:\Windows\Microsoft.NET\Framework\v2.0.50727 to the path

 before running the build it should fix it.
  

The build expects to run from a command shell set up by VS or the SDK,
which includes that path.

--
sig://boB
http://joyofsetup.com/




-
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge Build the coolest Linux based applications with Moblin SDK 
win great prizes Grand prize is a trip for two to an Open Source event
anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK  win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Getting the MSI Main UI window handle

[Michael Owings]

I have some C++ custom actions in my installer that will occasionally 
pop up message box warnings or prompts. I'm using NULL (Desktop) as the 
parent window handle for these message boxes, but under vista, they tend 
to show up hidden beneath the main WIX ui. Is there a way to get a 
useable window handle to the main wizard UI that I can use as a parent 
to prevent this from happening?

Thanx -- mikey
-- 
Teleoperate a roving mobile robot from the web:
http://www.swampgas.com/robotics/rover.html

-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK  win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Getting the MSI Main UI window handle

[Rob Mensching]

Use MsiProcessMessage() and the right thing happens.

-Original Message-
From: Michael Owings [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 22, 2008 13:56
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Getting the MSI Main UI window handle

I have some C++ custom actions in my installer that will occasionally
pop up message box warnings or prompts. I'm using NULL (Desktop) as the
parent window handle for these message boxes, but under vista, they tend
to show up hidden beneath the main WIX ui. Is there a way to get a
useable window handle to the main wizard UI that I can use as a parent
to prevent this from happening?

Thanx -- mikey
--
Teleoperate a roving mobile robot from the web:
http://www.swampgas.com/robotics/rover.html

-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK  win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK  win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Building WiX

[Neil Sleightholm]

If anyone is interested in building WiX from the source I have written a
blog that details the bits that aren't in the help file:
http://neilsleightholm.blogspot.com/2008/10/how-to-create-wix-build-mach
ine.html. 

 

Neil

 

Neil Sleightholm
X2 Systems Limited
[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] 

 

-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK  win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Getting the MSI Main UI window handle

[Michael Owings]

Works perfectly -- thanx.

Rob Mensching wrote:
 Use MsiProcessMessage() and the right thing happens.
 
 -Original Message-
 From: Michael Owings [mailto:[EMAIL PROTECTED]
 Sent: Wednesday, October 22, 2008 13:56
 To: General discussion for Windows Installer XML toolset.
 Subject: [WiX-users] Getting the MSI Main UI window handle
 
 I have some C++ custom actions in my installer that will occasionally
 pop up message box warnings or prompts. I'm using NULL (Desktop) as the
 parent window handle for these message boxes, but under vista, they tend
 to show up hidden beneath the main WIX ui. Is there a way to get a
 useable window handle to the main wizard UI that I can use as a parent
 to prevent this from happening?
 
 Thanx -- mikey
 --
 Teleoperate a roving mobile robot from the web:
 http://www.swampgas.com/robotics/rover.html
 
 -
 This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
 Build the coolest Linux based applications with Moblin SDK  win great prizes
 Grand prize is a trip for two to an Open Source event anywhere in the world
 http://moblin-contest.org/redirect.php?banner_id=100url=/
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users
 
 
 


-- 
Teleoperate a roving mobile robot from the web:
http://www.swampgas.com/robotics/rover.html

-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK  win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Building WiX

[Rob Mensching]

Can we get the appropriate details added to the help file?  Detailed bugs would 
be fantastic.

-Original Message-
From: Neil Sleightholm [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 22, 2008 15:08
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Building WiX

If anyone is interested in building WiX from the source I have written a
blog that details the bits that aren't in the help file:
http://neilsleightholm.blogspot.com/2008/10/how-to-create-wix-build-mach
ine.html.



Neil



Neil Sleightholm
X2 Systems Limited
[EMAIL PROTECTED] mailto:[EMAIL PROTECTED]



-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK  win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK  win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Error 0x800706d9: failed to get firewall profile

[Rob Mensching]

ExitOnFailure does not show message boxes.

-Original Message-
From: Wendell Joost [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 22, 2008 15:58
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Error 0x800706d9: failed to get firewall profile

Looking through the code, I'm seeing that ExitOnFailure is being
called in firewall.cpp/GetFirewallProfile, the line that contains:

hr = pfwPolicy-get_CurrentProfile(ppfwProfile);
ExitOnFailure(hr, failed to get current profile);


So, any tips on how I get ExitOnFailure to *not* display a messagebox
to the user when this fails?

Thanks!

Wendell

On Tue, Oct 21, 2008 at 9:08 PM, Bob Arnson [EMAIL PROTECTED] wrote:
 Brian Rogers wrote:
 I think you answered your own question.  I imagine stopping the firewall 
 service makes it so you can't configure it in this way.  Perhaps you can add 
 a ServiceControl element to ensure the firewall service is started (although 
 I'm not sure it would be guaranteed to be sequenced at the right time).


 It might cross the line to rudeness to turn on the firewall if a user
 turned it off. If the firewall custom actions can't connect to the
 firewall service, it will prompt (if the UI level supports it). You can
 use the IgnoreFailure attribute to let such failures be ignored.

 --
 sig://boB
 http://joyofsetup.com/



 -
 This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
 Build the coolest Linux based applications with Moblin SDK  win great prizes
 Grand prize is a trip for two to an Open Source event anywhere in the world
 http://moblin-contest.org/redirect.php?banner_id=100url=/
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users




--
Some people come visit Europe and are really let down when they find
out it's not like a credit-card commercial; others really get into
meeting all the quirky people and careening along narrow mountain
roads in rickety cabs driven by suicidal, gap-toothed Carpathians. I
guess it's pretty obvious which one you are... - Justin Crevier, May
'01

-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK  win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK  win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] UPGRADINGPRODUCTCODE is not working

[Wilson, Phil]

Unfortunately we're picking at this bit by bit and not actually getting all the 
information required to solve this.

It seems that the actual issue is that your custom action is failing, basically 
because you have some kind of installer class custom action that depends on the 
presence of an InstallState file.  The problem isn't directly related to your 
sequencing of RemoveExistingProducts, but it does seem to be an issue with your 
Installer class custom action - these are the only ones I've seen that 
internally use an InstallState file. The fact that there is a missing 
InstallState file is typically caused by using just (for example) a Commit 
custom action installer class call, but the base Install method is what creates 
the InstallState file so you must call it.  So every time you say it doesn't 
work - it still throws an error you need to say exactly what's going on and 
what the error is.

Phil Wilson

-Original Message-
From: Amit Shrivastav [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 21, 2008 6:00 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] UPGRADINGPRODUCTCODE is not working

No i tried that also. but still it is not working. that custom action is
throwing error.

On Tue, Oct 21, 2008 at 5:30 PM, Wilson, Phil [EMAIL PROTECTED]wrote:

 That uninstall for the older version of the product is already out there on
 the systems where the product is installed. You can't change its behavior
 unless you apply a patch or other minor upgrade.

 You may be able to correct your problem with this sequence towards the end
 of your InstallExecute sequence:

 ..
 InstallExecute
 RemoveExistingProducts
 your deferred custom action to install perfcounters
 InstallFinalize


 Phil Wilson


 -Original Message-
 From: Amit Shrivastav [mailto:[EMAIL PROTECTED]
 Sent: Tuesday, October 21, 2008 5:05 PM
 To: General discussion for Windows Installer XML toolset.
  Subject: Re: [WiX-users] UPGRADINGPRODUCTCODE is not working

 original msi doen not contain that condition NOT UPGRADINGPRODUCTCODE.
 Is this mandatory? Is there any other way so that i can stop executing that
 custom action in the uninstallation through Major upgrade.




 On Tue, Oct 21, 2008 at 4:57 PM, Amit Shrivastav [EMAIL PROTECTED]
 wrote:

  i have placed that in the second msi(upgraded msi). but it is not working
  though :(
 
  thanks
  amit
 
On Tue, Oct 21, 2008 at 4:32 PM, Ian Elliott (Excell Data Corporation)
 
  [EMAIL PROTECTED] wrote:
 
  If you don't want the original msi to execute the custom action when
 being
  uninstalled via major upgrade, you need the condition of NOT
  UPGRADINGPRODUCTCODE to be in the original msi. It's not clear to me if
 you
  have that condition in the original msi or the second msi.
 
 
  -Original Message-
  From: Amit Shrivastav [mailto:[EMAIL PROTECTED]
  Sent: Tuesday, October 21, 2008 4:20 PM
  To: General discussion for Windows Installer XML toolset.
  Subject: [WiX-users] UPGRADINGPRODUCTCODE is not working
 
  Hi,
 
  I am trying to upgrade my installer using property
 *UPGRADINGPRODUCTCODE.
  *In
  the previous MSI it was not there. now In the latest version i.e.
 upgraded
  msi contains that version. I have an custom action in original msi which
  execute at the time of uninstallation. In the upgrade msi i dont want to
  execute that custom action at the time of when major upgrade uninstall
 the
  previous product. but i want to execute that in the uninstallation of
 the
  new msi. I am mentioning the condition* *REMOVE=ALL AND NOT
  *UPGRADINGPRODUCTCODE
  *according to msdn article* **
  http://msdn.microsoft.com/en-us/library/aa369786.aspx*
  http://msdn.microsoft.com/en-us/library/aa369786.aspx
  *. *but it is not working. althoug my custom action is executing when
  major
  upgrade uninstall the previous version and when i uninstalling the new
  upgraded msi it is not executing.
  I am using windows 2003 platform for testing. and wix 3.0 for the
  development.
 
  Please let me know if anybody previously faced this issue.
  **
  Thanks in advance
  Amit
 
 -
  This SF.Net email is sponsored by the Moblin Your Move Developer's
  challenge
  Build the coolest Linux based applications with Moblin SDK  win great
  prizes
  Grand prize is a trip for two to an Open Source event anywhere in the
  world
  http://moblin-contest.org/redirect.php?banner_id=100url=/
  ___
  WiX-users mailing list
  WiX-users@lists.sourceforge.net
  https://lists.sourceforge.net/lists/listinfo/wix-users
 
 
 
 -
  This SF.Net email is sponsored by the Moblin Your Move Developer's
  challenge
  Build the coolest Linux based applications with Moblin SDK  win great
  prizes
  Grand prize is a trip for two to an Open Source event anywhere in the
  world
  

[WiX-users] Custom action Error

[Sandeep Gautam (HCL Technologies Ltd)]

Hi,
I have one custom action to start the service. If some service is not getting 
start , I want to invoke user defined error message.
Please suggest how can I do this.

Regards
Sandeep

-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK  win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Error 0x800706d9: failed to get firewall profile

[Wendell Joost]

When I stop the Firewall service (Windows Firewall, Internet Sharing
Service (SharedAccess)) and run setup and it executes:

get_CurrentProfile executes in firewall.cpp/GetFirewallProfile

http://msdn.microsoft.com/en-us/library/aa365325(VS.85).aspx

I get an error:

(HRESULT_FROM_WIN32(EPT_S_NOT_REGISTERED)

The GetFireWallProfile is causing the ErrorDialog to display with the
error message and abort/retry/ignore.  I'm trying to track down
exactly what causes this to display and, if possible, make it not
display.  ANy tips/pointers most appreciated.

Thanks!

Wendell



On Wed, Oct 22, 2008 at 4:03 PM, Rob Mensching
[EMAIL PROTECTED] wrote:
 ExitOnFailure does not show message boxes.

 -Original Message-
 From: Wendell Joost [mailto:[EMAIL PROTECTED]
 Sent: Wednesday, October 22, 2008 15:58
 To: General discussion for Windows Installer XML toolset.
 Subject: Re: [WiX-users] Error 0x800706d9: failed to get firewall profile

 Looking through the code, I'm seeing that ExitOnFailure is being
 called in firewall.cpp/GetFirewallProfile, the line that contains:

hr = pfwPolicy-get_CurrentProfile(ppfwProfile);
ExitOnFailure(hr, failed to get current profile);


 So, any tips on how I get ExitOnFailure to *not* display a messagebox
 to the user when this fails?

 Thanks!

 Wendell

 On Tue, Oct 21, 2008 at 9:08 PM, Bob Arnson [EMAIL PROTECTED] wrote:
 Brian Rogers wrote:
 I think you answered your own question.  I imagine stopping the firewall 
 service makes it so you can't configure it in this way.  Perhaps you can 
 add a ServiceControl element to ensure the firewall service is started 
 (although I'm not sure it would be guaranteed to be sequenced at the right 
 time).


 It might cross the line to rudeness to turn on the firewall if a user
 turned it off. If the firewall custom actions can't connect to the
 firewall service, it will prompt (if the UI level supports it). You can
 use the IgnoreFailure attribute to let such failures be ignored.

 --
 sig://boB
 http://joyofsetup.com/



 -
 This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
 Build the coolest Linux based applications with Moblin SDK  win great prizes
 Grand prize is a trip for two to an Open Source event anywhere in the world
 http://moblin-contest.org/redirect.php?banner_id=100url=/
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users




 --
 Some people come visit Europe and are really let down when they find
 out it's not like a credit-card commercial; others really get into
 meeting all the quirky people and careening along narrow mountain
 roads in rickety cabs driven by suicidal, gap-toothed Carpathians. I
 guess it's pretty obvious which one you are... - Justin Crevier, May
 '01

 -
 This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
 Build the coolest Linux based applications with Moblin SDK  win great prizes
 Grand prize is a trip for two to an Open Source event anywhere in the world
 http://moblin-contest.org/redirect.php?banner_id=100url=/
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users


 -
 This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
 Build the coolest Linux based applications with Moblin SDK  win great prizes
 Grand prize is a trip for two to an Open Source event anywhere in the world
 http://moblin-contest.org/redirect.php?banner_id=100url=/
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users




-- 
Some people come visit Europe and are really let down when they find
out it's not like a credit-card commercial; others really get into
meeting all the quirky people and careening along narrow mountain
roads in rickety cabs driven by suicidal, gap-toothed Carpathians. I
guess it's pretty obvious which one you are... - Justin Crevier, May
'01

-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK  win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Error 0x800706d9: failed to get firewall profile

[Rob Mensching]

If you do a silent (/qn) install the dialogs should not appear.

-Original Message-
From: Wendell Joost [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 22, 2008 16:41
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Error 0x800706d9: failed to get firewall profile

When I stop the Firewall service (Windows Firewall, Internet Sharing
Service (SharedAccess)) and run setup and it executes:

get_CurrentProfile executes in firewall.cpp/GetFirewallProfile

http://msdn.microsoft.com/en-us/library/aa365325(VS.85).aspx

I get an error:

(HRESULT_FROM_WIN32(EPT_S_NOT_REGISTERED)

The GetFireWallProfile is causing the ErrorDialog to display with the
error message and abort/retry/ignore.  I'm trying to track down
exactly what causes this to display and, if possible, make it not
display.  ANy tips/pointers most appreciated.

Thanks!

Wendell



On Wed, Oct 22, 2008 at 4:03 PM, Rob Mensching
[EMAIL PROTECTED] wrote:
 ExitOnFailure does not show message boxes.

 -Original Message-
 From: Wendell Joost [mailto:[EMAIL PROTECTED]
 Sent: Wednesday, October 22, 2008 15:58
 To: General discussion for Windows Installer XML toolset.
 Subject: Re: [WiX-users] Error 0x800706d9: failed to get firewall profile

 Looking through the code, I'm seeing that ExitOnFailure is being
 called in firewall.cpp/GetFirewallProfile, the line that contains:

hr = pfwPolicy-get_CurrentProfile(ppfwProfile);
ExitOnFailure(hr, failed to get current profile);


 So, any tips on how I get ExitOnFailure to *not* display a messagebox
 to the user when this fails?

 Thanks!

 Wendell

 On Tue, Oct 21, 2008 at 9:08 PM, Bob Arnson [EMAIL PROTECTED] wrote:
 Brian Rogers wrote:
 I think you answered your own question.  I imagine stopping the firewall 
 service makes it so you can't configure it in this way.  Perhaps you can 
 add a ServiceControl element to ensure the firewall service is started 
 (although I'm not sure it would be guaranteed to be sequenced at the right 
 time).


 It might cross the line to rudeness to turn on the firewall if a user
 turned it off. If the firewall custom actions can't connect to the
 firewall service, it will prompt (if the UI level supports it). You can
 use the IgnoreFailure attribute to let such failures be ignored.

 --
 sig://boB
 http://joyofsetup.com/



 -
 This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
 Build the coolest Linux based applications with Moblin SDK  win great prizes
 Grand prize is a trip for two to an Open Source event anywhere in the world
 http://moblin-contest.org/redirect.php?banner_id=100url=/
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users




 --
 Some people come visit Europe and are really let down when they find
 out it's not like a credit-card commercial; others really get into
 meeting all the quirky people and careening along narrow mountain
 roads in rickety cabs driven by suicidal, gap-toothed Carpathians. I
 guess it's pretty obvious which one you are... - Justin Crevier, May
 '01

 -
 This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
 Build the coolest Linux based applications with Moblin SDK  win great prizes
 Grand prize is a trip for two to an Open Source event anywhere in the world
 http://moblin-contest.org/redirect.php?banner_id=100url=/
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users


 -
 This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
 Build the coolest Linux based applications with Moblin SDK  win great prizes
 Grand prize is a trip for two to an Open Source event anywhere in the world
 http://moblin-contest.org/redirect.php?banner_id=100url=/
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users




--
Some people come visit Europe and are really let down when they find
out it's not like a credit-card commercial; others really get into
meeting all the quirky people and careening along narrow mountain
roads in rickety cabs driven by suicidal, gap-toothed Carpathians. I
guess it's pretty obvious which one you are... - Justin Crevier, May
'01

-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK  win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world

[WiX-users] Passing command line arguments to an app launched after setup

[chaiguy1337]

Hi all. I'm looking for a way to pass command line arguments to my app
launched when the installation is complete, so that my app knows it was
launched by the installer.

I basically copied the example from the help file:

Property Id=WixShellExecTarget
Value=[#OrangeNote.exe] /
CustomAction Id=LaunchApplication
BinaryKey=WixCA
DllEntry=WixShellExec
Impersonate=yes /

Where might I add my -installer switch? I tried changing the Value of the
property to [#OrangeNote.exe] -installer but that didn't work at all, and
the app never launched.

Logan

-
A. Logan Murray
http://pihole.org/
-- 
View this message in context: 
http://n2.nabble.com/Passing-command-line-arguments-to-an-app-launched-after-setup-tp1366362p1366362.html
Sent from the wix-users mailing list archive at Nabble.com.


-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK  win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Installing shortcuts to All Users profile in a per-machine installation

[Matt Siebert]

Please forgive my ignorance but creating a per-user reg key as a keypath for
a per-machine shortcut seems very wrong in that the reg key can easily
become orphaned.

Perhaps this is why the Windows Server 2008 Software Logo
Specificationshttp://go.microsoft.com/fwlink/?LinkID=111723don't
include ICEs 43 or 57...

On Wed, Oct 22, 2008 at 8:35 PM, Sébastien Mouren 
[EMAIL PROTECTED] wrote:

 2008/10/22 Matt Siebert [EMAIL PROTECTED]:
  Hi all,
 
  I'm new to WiX and I'm trying to create a test install for a single file
  with a shortcut in the All Users profile.
 
  The file I'm installing is going to %programfiles%\Company\Product and I
  want to place a shortcut in %allusersprofile%\Desktop.
 
  I've done a lot of googling and searched the archives for this mailing
 list
  and it seems that everyone who has had a similar problem has been
 directed
  to
 
 http://robmensching.com/blog/archive/2007/04/27/How-to-create-an-uninstall-shortcut-and-pass-all-the.aspx
 ,
  but I can't see how that post solves the issue - it installs shortcuts to
  the current user's profile using a RegistryValue as the KeyPath (I
 already
  did this to create a per-user test install) but doesn't show how to
 install
  shortcuts to the All Users profile in a per-machine install.
 
  Here is my very simple product.wxs:
 
  Wix xmlns=http://schemas.microsoft.com/wix/2006/wi;
   Product Id={PUT-GUID-HERE} Name=Product Language=1033 Version=
  1.0.0.0 Manufacturer=Company UpgradeCode={PUT-GUID-HERE}
 Package InstallerVersion=200 Compressed=yes/
 Media Id=1 Cabinet=TestApp.cab EmbedCab=yes/
 Property Id=ALLUSERS Value=1/
 
 Directory Id=TARGETDIR Name=SourceDir
   Directory Id=ProgramFilesFolder
 Directory Id=CompanyFolder Name=Company
   Directory Id=APPLICATIONROOTDIRECTORY Name=Product/
 /Directory
   /Directory
   Directory Id=DesktopFolder/
 /Directory
 
 DirectoryRef Id=APPLICATIONROOTDIRECTORY
   Component Id=TestApp Guid={PUT-GUID-HERE}
 File Source=Product.exe KeyPath=yes Checksum=yes
 Vital=yes
   Shortcut Id=TestAppShortcut Name=Product
  Directory=DesktopFolder/
 /File
   /Component
 /DirectoryRef
 
 Feature Id=MainApplication Title=Main Application Level=1
  Absent=disallow AllowAdvertise=no
   ComponentRef Id=TestApp/
 /Feature
   /Product
  /Wix
 
  I've set ALLUSERS=1 and this should cause the DesktopFolder property to
  point to the desktop folder in the All Users profile on the target
  machine.
 
  I get the following errors from light.exe:
 
  error LGHT0204: ICE43: Component TestApp has non-advertised shortcuts. It
  should use a registry key under HKCU as its KeyPath, not a file.
  error LGHT0204: ICE57: Component 'TestApp' has both per-user and
 per-machine
  data with a per-machine KeyPath.
 
  Surely its possible to install non-advertised shortcuts to the All
 Users
  profile...
 
  Any help would be greatly appreciated.
 
  Thanks,
  Matt.

 The common desktop and a user's desktop uses the same DesktopFolder
 property: the ALLUSERS property allows to choose between the two.
 Some ICE tests implements best practices compliance defined by the
 Windows Installer team. These best practices makes harder sometimes
 for the user to think its setup . There are a few corner case and you
 seem to be in one of these.
 A few workaround are possible:
 -your setup needs to be deployed per machine (ProgramFilesFolder and
 shortcut place in the common DesktopFolder), why don't you advertise
 your shorcut and enforce local deployment of the parent feature?
 -create, as other indicated in their answers, another component like this
 one:
Component Id=Shortcut Guid=* Directory=ProgramFilesFolder
  RegistryKey Id='TestAppKey' Root='HKCU'
 Action='createAndRemoveOnUninstall' Key='Software\Company\Product'
RegistryValue Id='TestAppValue' Name='TestAppValue'
 Type='string' Value='installed' Action='write' KeyPath='yes' /
  /RegistryKey
  Shortcut Id=Link
  Name=Product
  Description=My Application Description
  WorkingDirectory=APPLICATIONROOTDIRECTORY
  Directory=DesktopFolder
  Target=[APPLICATIONROOTDIRECTORY]Product.exe /
/Component
 include this one in your only feature. This one is trickier but read
 ICE 57 
 (http://msdn.microsoft.com/en-us/library/aa368994(VS.85).aspxhttp://msdn.microsoft.com/en-us/library/aa368994%28VS.85%29.aspx
 )
 and 43 
 (http://msdn.microsoft.com/en-us/library/aa368968(VS.85).aspxhttp://msdn.microsoft.com/en-us/library/aa368968%28VS.85%29.aspx
 ).
 They explain why you should use another component, a per-user reg key
 as a keypath for a per-machine shortcut. It has a default of orphaning
 registry key and value if reinstalled multiple times by different
 users.
 This snippet won't work as is: requires some cleaning and corrections
 to your original example.

 

Re: [WiX-users] Error 0x800706d9: failed to get firewall profile

[Bob Arnson]

Wendell Joost wrote:
 The GetFireWallProfile is causing the ErrorDialog to display with the
 error message and abort/retry/ignore.  I'm trying to track down
 exactly what causes this to display and, if possible, make it not
 display.  ANy tips/pointers most appreciated.
   

Right now, that dialog is always shown if the user interface level 
supports it, from the call to WcaErrorMessage. That's parallel with the 
behavior of other WiX custom actions. Feel free to open a feature 
request to support suppressing that message.

-- 
sig://boB
http://joyofsetup.com/



-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK  win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Passing command line arguments to an app launched after setup

[Bob Arnson]

chaiguy1337 wrote:
 Hi all. I'm looking for a way to pass command line arguments to my app
 launched when the installation is complete, so that my app knows it was
 launched by the installer.

 I basically copied the example from the help file:

 Property Id=WixShellExecTarget
   Value=[#OrangeNote.exe] /
 CustomAction Id=LaunchApplication
   BinaryKey=WixCA
   DllEntry=WixShellExec
   Impersonate=yes /

 Where might I add my -installer switch? I tried changing the Value of the
 property to [#OrangeNote.exe] -installer but that didn't work at all, and
 the app never launched.
   

WixShellExecTarget must be only the path of the executable/document. 
There's no support to add arguments. For that, use a normal exe custom 
action instead of WixShellExec.

-- 
sig://boB
http://joyofsetup.com/



-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK  win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Torch generating mst with cabs question

[Bob Arnson]

Michael Ballou wrote:
 I then use torch.exe to generate an MST file so that I can later
 transform the smaller install to the large one.  The problem is that
 torch doesn't seem to be including the extra embedded cab file.  The
 transform is very small (6K), and when I apply it to the small MSI and
 run it, I get an Internal Error 2356 for the missing cab file.
   

Transforms only change databases. From the MSI SDK doc:

A transform can modify information that is in any persistent table in 
the installer database installer_database.htm. A transform can also 
add or remove persistent tables in the installer database. Transforms 
cannot modify any part of an installation package that is not in a 
database table, such as information in the summary information stream 
summary_information_stream.htm, information in substorages, or files 
in embedded cabinets.

To add files in an embedded cab, you need a patch.

 I was previously building the MSI's with Wise for Windows Installer
 which embeds the cabs in the Cabs table.  

That's not a standard table; maybe Wise adds a custom action to extract 
it somehow?

-- 
sig://boB
http://joyofsetup.com/

-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK  win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Passing command line arguments to an app launched after setup

[chaiguy1337]

Is there a particular reason the example in the help file didn't use normal
exe custom actions? I don't want to do something that might cause problems
later.


Bob Arnson-6 wrote:
 
 chaiguy1337 wrote:
 Hi all. I'm looking for a way to pass command line arguments to my app
 launched when the installation is complete, so that my app knows it was
 launched by the installer.

 I basically copied the example from the help file:

 Property Id=WixShellExecTarget
  Value=[#OrangeNote.exe] /
 CustomAction Id=LaunchApplication
  BinaryKey=WixCA
  DllEntry=WixShellExec
  Impersonate=yes /

 Where might I add my -installer switch? I tried changing the Value of
 the
 property to [#OrangeNote.exe] -installer but that didn't work at all,
 and
 the app never launched.
   
 
 WixShellExecTarget must be only the path of the executable/document. 
 There's no support to add arguments. For that, use a normal exe custom 
 action instead of WixShellExec.
 
 -- 
 sig://boB
 http://joyofsetup.com/
 
 
 
 -
 This SF.Net email is sponsored by the Moblin Your Move Developer's
 challenge
 Build the coolest Linux based applications with Moblin SDK  win great
 prizes
 Grand prize is a trip for two to an Open Source event anywhere in the
 world
 http://moblin-contest.org/redirect.php?banner_id=100url=/
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users
 
 


-
A. Logan Murray
http://pihole.org/
-- 
View this message in context: 
http://n2.nabble.com/Passing-command-line-arguments-to-an-app-launched-after-setup-tp1366362p1366652.html
Sent from the wix-users mailing list archive at Nabble.com.


-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK  win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Passing command line arguments to an app launched after setup

[Bob Arnson]

chaiguy1337 wrote:
 Is there a particular reason the example in the help file didn't use normal
 exe custom actions? I don't want to do something that might cause problems
 later.
   

Because a more typical use case is to launch a document (like a 
readme.html or .pdf). WixShellExec was designed just for that purpose. 
Most users won't expect another install to launch after finishing one.

-- 
sig://boB
http://joyofsetup.com/


-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK  win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Passing command line arguments to an app launched after setup

[chaiguy1337]

I wasn't talking about launching another install, I was talking about
launching the application that was just installed. I guess that makes sense
as to why ShellExec was chosen for the example. I will fiddle around with
normal custom actions and see if I can get it working.


Bob Arnson-6 wrote:
 
 chaiguy1337 wrote:
 Is there a particular reason the example in the help file didn't use
 normal
 exe custom actions? I don't want to do something that might cause
 problems
 later.
   
 
 Because a more typical use case is to launch a document (like a 
 readme.html or .pdf). WixShellExec was designed just for that purpose. 
 Most users won't expect another install to launch after finishing one.
 
 -- 
 sig://boB
 http://joyofsetup.com/
 
 
 -
 This SF.Net email is sponsored by the Moblin Your Move Developer's
 challenge
 Build the coolest Linux based applications with Moblin SDK  win great
 prizes
 Grand prize is a trip for two to an Open Source event anywhere in the
 world
 http://moblin-contest.org/redirect.php?banner_id=100url=/
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users
 
 


-
A. Logan Murray
http://pihole.org/
-- 
View this message in context: 
http://n2.nabble.com/Passing-command-line-arguments-to-an-app-launched-after-setup-tp1366362p1366725.html
Sent from the wix-users mailing list archive at Nabble.com.


-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK  win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Passing command line arguments to an app launched after setup

[chaiguy1337]

Thanks! Got it working.


Bob Arnson-6 wrote:
 
 chaiguy1337 wrote:
 Is there a particular reason the example in the help file didn't use
 normal
 exe custom actions? I don't want to do something that might cause
 problems
 later.
   
 
 Because a more typical use case is to launch a document (like a 
 readme.html or .pdf). WixShellExec was designed just for that purpose. 
 Most users won't expect another install to launch after finishing one.
 
 -- 
 sig://boB
 http://joyofsetup.com/
 
 
 -
 This SF.Net email is sponsored by the Moblin Your Move Developer's
 challenge
 Build the coolest Linux based applications with Moblin SDK  win great
 prizes
 Grand prize is a trip for two to an Open Source event anywhere in the
 world
 http://moblin-contest.org/redirect.php?banner_id=100url=/
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users
 
 


-
A. Logan Murray
http://pihole.org/
-- 
View this message in context: 
http://n2.nabble.com/Passing-command-line-arguments-to-an-app-launched-after-setup-tp1366362p1366796.html
Sent from the wix-users mailing list archive at Nabble.com.


-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK  win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users