[WiX-users] Looking for a consultant

[Sean Farrow]

Hi:
I'm in the process of finishing up a job, the installation is created, but I'd 
like to add a few other features that require user interface changes.
Are there any wix/msi consultants out there that would be prepared to help.
This would be paid work.
Any help appreciated.
Sean.
--
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Trouble when uninstalling a WiX msi under 64-bit machines

[Blair]

(sorry for the late response - I've suddenly been very busy these past two 
months)

This has the "v" in the logging properties, but it doesn't have all of the 
information ("v" does not turn on all of the other values. Also, "x" is a very 
useful one for that often elusive piece of data that makes everything fall into 
place). But, I did find this as an interesting starting point:

MSI (s) (60:30) [11:04:27:568]: Feature: Complete; Installed: Local; Request: 
Absent;   Action: Absent
MSI (s) (60:30) [11:04:27:568]: Component: redemption.dll; Installed: Local; 
Request: Absent;   Action: Null
MSI (s) (60:30) [11:04:27:568]: Component: __redemption.dll65; Installed: Null; 
  Request: Absent;   Action: Null

On that same computer after removing the product, use the MsiEnumClients() or 
the Installer.ComponentClients API with the component guid 
"{869E2B20-FCC0-423A-B553-39147E30A174}" and see if it reports as still 
installed, and what product(s) it is still associated with.

-Original Message-
From: NirK [mailto:n...@od.co.il] 
Sent: Sunday, August 29, 2010 1:07 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Trouble when uninstalling a WiX msi under 64-bit 
machines


Hi all,

(I was out on a vacation so sorry for the late reply).



--
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] HeatDirectory failing on Team Build 2010 x64

[Reed, Daryl]

Just putting this back out there before I go do something drastic, like write 
my own quick and dirty version...

I am using a HeatDirectory entry which fails on my build server (TFS 2010 x64, 
details below).  I've added the RunWixToolsOutOfProc and have the latest build 
of 3.5 and 3.6, but nothing seems to work.  Any help would be greatly 
appreciated.


Daryl

-Original Message-
From: Reed, Daryl [mailto:daryl.r...@ga-asi.com] 
Sent: Monday, September 20, 2010 11:52 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] HeatDirectory failing on Team Build 2010 x64

I have a wixproj that uses HeatDirectory to build the file references I need 
for an MSI.  It is running fine on my machine, but failing on the build server, 
which is running Team Foundation Server 2010's Team Build.  I have not 
installed WiX on the build server, but instead checked the files in and 
reference them from there.  I have included the  
true element, but am still getting 
'Unhandled Exception: System.BadImageFormatException: Could not load file or 
assembly 'file:///C:\Builds\1\claw3x\Continuous 
Integration\Sources\Builds\Common\Libraries\WiX 3.6\Heat.exe' or one of its 
dependencies. An attempt was made to load a program with an incorrect format.'  
I've tried different builds of 3.5 and 3.6 to no avail.  I don't know where to 
go from here.  I'm including a portion of the .wixproj file to show how things 
are setup...


http://schemas.microsoft.com/developer/msbuild/2003";>

$(MSBuildProjectDirectory)..\..\..\Common\Libraries\WiX 
3.6\
$(WixToolPath)\Wix.targets
$(WixToolPath)\wixtasks.dll
true


Release ...

ClawAppDirPath=$(SolutionDropPath)$(Platform)\$(Configuration)\CLAWDemoApp\


Debug;$(HeatDefinitions)


$(HeatDefinitions)

...








--
Start uncovering the many advantages of virtual appliances and start using them 
to simplify application deployment and accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Question about InstallValidation for uninstall

[Blair]

In case no one answered, EmbeddedUI is the most effective way.

-Original Message-
From: Elfe Xu [mailto:elf...@microsoft.com] 
Sent: Thursday, August 26, 2010 6:33 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Question about InstallValidation for uninstall


Thanks Phil.

My question is: is there anyway for me to hide the MsiRMFilesInUse dialog,
and do the close/restart application automatically? I want to use the
Restart Mananger rather than implement start/stop functions by myself, but I
don't want user to see this dialog.

Thanks,
-Elfe

-- 
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Question-about
-InstallValidation-for-uninstall-tp5464620p5467912.html
Sent from the wix-users mailing list archive at Nabble.com.


--
Sell apps to millions through the Intel(R) Atom(Tm) Developer Program
Be part of this innovative community and reach millions of netbook users 
worldwide. Take advantage of special opportunities to increase revenue and 
speed time-to-market. Join now, and jumpstart your future.
http://p.sf.net/sfu/intel-atom-d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Command Line Parameters toDeferred CustomAction on Vista

[Bob Arnson]

  On 22-Sep-10 13:07, Matt Walker wrote:
> I don't know if I mentioned this before, but my Deferred Custom Action
> fires an .exe stored in the Binary Table with the following command line
> parameters being passed [ProductCode] [OURVERSION], the later being the
> pre-populated property.

The reason it works is that your deferred action is being scheduled 
during the script generation phase of the execute sequence, when 
properties are still available. Your CA isn't trying to read properties 
-- it's an .exe whose command line was set when it was scheduled. 
SecureCustomProperties is necessary to get a property out of the UI 
sequence and into the script generation phase of the execute sequence. 
SecureCustomProperties won't get a property into the *script execution* 
phase of the execute sequence; that's what CustomActionData is for.

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


--
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] listbox/view with check boxes in

[Bob Arnson]

  On 20-Sep-10 13:09, Sean Farrow wrote:
> Is it possible within the current user interface of wix to have a 
> listbox/listview with checkboxes in?

MSI doesn't support that.

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


--
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Sub-feature in separate wxs file

[Bob Arnson]

  On 22-Sep-10 12:13, pcristini wrote:
> And I don't want the Plugin.Users.wxs file to have any reference to the
> Plugin.UserSync.wxs

The most likely cause is that the fragment containing the child feature 
isn't getting linked in. WiX follows references from the entry section 
(Product) to its children; it doesn't go the other way, so you can't 
cause a fragment to be linked by having a child refer to a parent. Once 
it's linked in, the child-to-parent reference will generate the feature 
tree you're looking for.

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


--
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Problems with UninstallCertificates custom action

[Bob Arnson]

  On 22-Sep-10 20:15, Dario Amiri wrote:
> So it looks like no one has any advice for this issue. Is there any way
> I can submit this as a bug?

The WiX home page has links to the bug database: https://wix.codeplex.com/

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


--
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Heat.exe

[Bob Arnson]

  On 22-Sep-10 18:11, David Amey wrote:
> Basically I'm using heat to harvest a folder, simples. However I'm using the 
> "-var" property in the command line (to replace the "sourceDir" in the output 
> component's source attribute), using a variable declared in the main.wxs. 
> This replaces the "sourceDir" as expected, but when it comes to candle to 
> compile , it flags an error as if the variable isn't populated.

You have to define the values for any preprocessor variables you use in 
your source code. How you do that depends on how you run the compiler 
(e.g., -d on the command line or DefineConstants in MSBuild) but both 
are documented in WiX.chm.

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


--
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] How does patching decide which files to includein msp?

[Bob Arnson]

  On 20-Sep-10 06:44, Pally Sandher wrote:
> IIRC I had similar issues when attempting to create patches using the
> Pyro method in WiX 3.0 hence I've stuck with the PatchWiz method. I'm
> sure if I stuck at it I could probably work out what's going wrong when
> I try using the Pyro method but since I have a method which works
> there's not much incentive.

And without bug reports, it's hard finding and fixing bugs.

> Travis have you tried using the PatchWiz method? It's described in the
> WiX.chm (you'll require the Windows SDK installed to get the required
> tools which is freely downloadable from microsoft.com). You may find it
> works more reliably than the Pyro method for your situation.

Until it doesn't and PatchWiz error messages are useless for diagnosing 
the problem...

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


--
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Problems with UninstallCertificates custom action

[Dario Amiri]

Hi,

So it looks like no one has any advice for this issue. Is there any way
I can submit this as a bug? Because as far as I can tell the
"iis:Certificate" custom action is broke.

Regards,

Dario

-Original Message-
From: Dario Amiri [mailto:dam...@osisoft.com] 
Sent: Tuesday, September 21, 2010 9:28 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Problems with UninstallCertificates custom action

Hi all,

 

This is my first time post. I want to thank the wix team for developing
their product. It has been great thus far.

 

When I was using Visual Studio 2008 and wix 3.0 I was able to create
MSIs that installed certificates and uninstalled them just fine when
doing a product uninstall. I recently upgraded to Visual Studio 2010 and
wix 3.6 and now the MSI builds in a way that installs fine but does not
uninstall well. I get the following error:

 

UninstallCertificates:  Entering UninstallCertificates in
C:\Windows\Installer\MSID41F.tmp, version 3.6.910.0

DEBUG: Error 2769:  Custom Action UninstallCertificates did not close 3
MSIHANDLEs.

 

I contacted one of the wix developers by email and he suggested I try
wix 3.5 because 3.6 is unstable. So I downgraded but the results are the
same. I have attached both logs to this email. Below is a snippet of the
.wxs file showing how I specify the certificate installation using the
iis:Certificates extenstion. If anyone can help me out I would greatly
appreciate it. Otherwise I have no option but to develop in VS 2010 and
build my kits in VS 2008.

 

Thanks,

 

Dario

 

 



   

 

  



 



  

 



.

.

.





 

 


--
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Question with performance on installer using cab files

[Leung, John C.H.]

I have some performance question on installer setup that uses cab files.  I'm 
wondering if I just didn't set up my WiX project properly or it this is how cab 
files install behaves.

I notice that during installation of the files listed in the cab files, it 
always read 16 and 256 bytes (see below table from Process Monitor) near the 
start of the cab file and then seek forward to read 32KB chunks and write data. 
 This is happening for every single file in the cab file.  We have over 10,000 
files in the cab file.  This constantly seeking back and forth on the DVD drive 
seems inefficient.  Is this normal?  Or is there something I'm supposed to do 
in my WiX project setup?  I've tried different compression level (default, 
none, low, etc), they don't seem to have any effect on this behaviour.


"4:36:31.9308030 
PM","msiexec.exe","4992","ReadFile","F:\CabGroup.cab","SUCCESS","Offset: 108, 
Length: 16, Priority: Normal"  < - - - Reading 16 + 256 bytes near 
beginning of cab file.
"4:36:31.9308395 
PM","msiexec.exe","4992","ReadFile","F:\CabGroup.cab","SUCCESS","Offset: 124, 
Length: 256, Priority: Normal"
"4:36:31.9337166 
PM","msiexec.exe","4992","WriteFile","C:\Config.Msi\b684f13.rbs","SUCCESS","Offset:
 4,766, Length: 97"
"4:36:31.9387399 PM","msiexec.exe","4992","WriteFile","C:\Program Files\Test 
Install\SimpleTest\TestCabGrp\TestFolder1\SubFolder11\DummyImage2.bmp","SUCCESS","Offset:
 0, Length: 10,850, Priority: Normal"
"4:36:31.9388491 PM","msiexec.exe","4992","ReadFile","C:","SUCCESS","Offset: 
41,885,696, Length: 96, I/O Flags: Non-cached, Paging I/O, Synchronous Paging 
I/O, Priority: Normal"
"4:36:31.9389737 
PM","msiexec.exe","4992","ReadFile","F:\CabGroup.cab","SUCCESS","Offset: 
27,673, Length: 8, Priority: Normal"
"4:36:31.9390101 
PM","msiexec.exe","4992","ReadFile","F:\CabGroup.cab","SUCCESS","Offset: 
27,681, Length: 194, Priority: Normal"
"4:36:31.9392198 PM","msiexec.exe","4992","WriteFile","C:\Program Files\Test 
Install\SimpleTest\TestCabGrp\TestFolder1\SubFolder11\DummyImage2.bmp","SUCCESS","Offset:
 10,850, Length: 32,768, Priority: Normal"
"4:36:31.9396917 
PM","msiexec.exe","4992","ReadFile","F:\CabGroup.cab","SUCCESS","Offset: 
27,875, Length: 8, Priority: Normal"
"4:36:31.9397258 
PM","msiexec.exe","4992","ReadFile","F:\CabGroup.cab","SUCCESS","Offset: 
27,883, Length: 178, Priority: Normal"
"4:36:31.9398968 PM","msiexec.exe","4992","WriteFile","C:\Program Files\Test 
Install\SimpleTest\TestCabGrp\TestFolder1\SubFolder11\DummyImage2.bmp","SUCCESS","Offset:
 43,618, Length: 32,768"
...
"4:36:31.9776340 PM","msiexec.exe","4992","WriteFile","C:\Program Files\Test 
Install\SimpleTest\TestCabGrp\TestFolder1\SubFolder11\DummyImage2.bmp","SUCCESS","Offset:
 2,468,450, Length: 11,068"
"4:36:31.9813752 
PM","msiexec.exe","4992","ReadFile","F:\CabGroup.cab","SUCCESS","Offset: 172, 
Length: 16, Priority: Normal"  < - - - Reading 16 + 256 bytes near 
beginning of cab file.
"4:36:31.9814126 
PM","msiexec.exe","4992","ReadFile","F:\CabGroup.cab","SUCCESS","Offset: 188, 
Length: 256, Priority: Normal"
"4:36:31.9840158 
PM","msiexec.exe","4992","WriteFile","C:\Config.Msi\b684f13.rbs","SUCCESS","Offset:
 4,863, Length: 92"
"4:36:31.9886911 PM","msiexec.exe","4992","WriteFile","C:\Program Files\Test 
Install\SimpleTest\TestCabGrp\TestFolder1\SubFolder11\Image3.bmp","SUCCESS","Offset:
 0, Length: 21,700, Priority: Normal"
"4:36:31.9888493 
PM","msiexec.exe","4992","ReadFile","F:\CabGroup.cab","SUCCESS","Offset: 
57,571, Length: 8, Priority: Normal"
"4:36:31.981 
PM","msiexec.exe","4992","ReadFile","F:\CabGroup.cab","SUCCESS","Offset: 
57,579, Length: 2,174, Priority: Normal"
"4:36:31.9891042 PM","msiexec.exe","4992","WriteFile","C:\Program Files\Test 
Install\SimpleTest\TestCabGrp\TestFolder1\SubFolder11\Image3.bmp","SUCCESS","Offset:
 21,700, Length: 32,768, Priority: Normal"
...
"4:36:32.0270798 PM","msiexec.exe","4992","WriteFile","C:\Program Files\Test 
Install\SimpleTest\TestCabGrp\TestFolder1\SubFolder11\Image3.bmp","SUCCESS","Offset:
 2,282,692, Length: 18,770"
"4:36:32.0306709 
PM","msiexec.exe","4992","ReadFile","F:\CabGroup.cab","SUCCESS","Offset: 231, 
Length: 16, Priority: Normal" < - - - Reading 16 + 256 bytes near beginning 
of cab file.
"4:36:32.0307078 
PM","msiexec.exe","4992","ReadFile","F:\CabGroup.cab","SUCCESS","Offset: 247, 
Length: 256, Priority: Normal"
"4:36:32.0332996 
PM","msiexec.exe","4992","WriteFile","C:\Config.Msi\b684f13.rbs","SUCCESS","Offset:
 4,955, Length: 92"
"4:36:32.2163116 PM","msiexec.exe","4992","WriteFile","C:\Program Files\Test 
Install\SimpleTest\TestCabGrp\TestFolder1\SubFolder11\Image4.bmp","SUCCESS","Offset:
 0, Length: 13,998, Priority: Normal"
"4:36:32.2165258 
PM","msiexec.exe","4992","ReadFile","F:\CabGroup.cab","SUCCESS","Offset: 
207,409, Length: 8, Priority: Normal"
"4:36:32.2165745 
PM","msiexec.exe","4992","ReadFile","F:\CabGroup.cab","SUCCESS","Offset: 
207,417, Length: 1,500, Priority: Normal"
"4:36:32.2167896 PM","msiex

Re: [WiX-users] Command LineParameterstoDeferred CustomAction on Vista

[Wilson, Phil]

More generally, you potentially won't be able to access that property at all in 
any way in the execute sequence unless it is in SecureCustomProperties. It's 
really nothing to do with whether you need it in a custom action or not. There 
seems to be an assumption that the only reason you need properties passed into 
the execute sequence is so that you can pass them to (deferred) custom actions.

Phil Wilson


-Original Message-
From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com]
Sent: Wednesday, September 22, 2010 12:41 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Command LineParameterstoDeferred CustomAction on Vista

I believe that is correct. I believe this is the sole purpose of the 
SecureCustomProperties property.

If you do not pass the data via CustomActionData *and* you do not add the 
property to SecureCustomProperties, then you will _not_ have access to that 
data in any way in the deferred custom action.

If you add the property to SecureCustomProperties, then you can access the data 
via the standard mechanisms for getting property values. The only properties 
you can access are the ones listed in SecureCustomProperties and a handful of 
others that are added by default by Windows Installer, check the SDK 
documentation for details.

If you add the data to CustomActionData, then you'll be able to access it via 
the CustomActionData mechanism in the deferred custom action.

If you do both, then you'll have access to the data via both mechanisms.

Edwin G. Castro
Software Developer - Staff
Electronic Banking Services
Fiserv
Office: 503-746-0643
Fax: 503-617-0291
www.fiserv.com
Please consider the environment before printing this e-mail


> -Original Message-
> From: Matt Walker [mailto:matt.wal...@synergis.com]
> Sent: Wednesday, September 22, 2010 12:16 PM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Command LineParameterstoDeferred
> CustomAction on Vista
>
> So adding the property to SecureCustomProperties also allows access to the
> property value directly at Deferred Action time (as opposed to passing it
> through CustomActionData)?
>
>
> Matt Walker
> Installation Development
> 200 Kelly Road | Quakertown, PA 18951
> Phone: +1 215.529.9900, x192 | 800.836.5440
> Fax: +1 215.536.9249
> http://www.synergissoftware.com/
> Adept Engineering Document Management & Workflow This message (and
> any associated files) is intended only for the use of the individual or 
> entity to
> which it is addressed and may contain information that is confidential,
> subject to copyright or constitutes a trade secret. If you are not the 
> intended
> recipient you are hereby notified that any dissemination, copying or
> distribution of this message, or files associated with this message, is 
> strictly
> prohibited. If you have received this message in error, please notify us
> immediately by replying to the message and deleting it from your computer.
> Messages sent to and from us may be monitored.
> Internet communications cannot be guaranteed to be secure or error-free as
> information could be intercepted, corrupted, lost, destroyed, arrive late or
> incomplete, or contain viruses. Therefore, we do not accept responsibility for
> any errors or omissions that are present in this message, or any attachment,
> that have arisen as a result of e-mail transmission. If verification is 
> required,
> please request a hard-copy version. Any views or opinions presented are
> solely those of the author and do not necessarily represent those of the
> company.
> -Original Message-
>
> From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com]
> Sent: Wednesday, September 22, 2010 3:03 PM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users]Command LineParameterstoDeferred CustomAction
> on Vista
>
> Imagine that you have table-driven custom action. This custom action would
> need to read the values out of a table to determine what work to do. In this
> scenario you need an immediate custom action which can read the
> appropriate tables and stuff the data into CustomActionData. Then a
> deferred custom action can read the data out of CustomActionData and
> perform the actual work. This two-stage approach is necessary because
> Windows Installer does not allow deferred custom actions to read many of
> the tables in the MSI database. If you written a table-driven custom action
> then you likely also have custom tables which are most definitely not
> available in the deferred custom action.
>
> For very simple deferred custom actions where you only need to pass in a
> very small number data to the deferred custom action, such as a single
> property value, then it would be appropriate to add the property to
> SecureCustomProperties.
>
> Edwin G. Castro
> Software Developer - Staff
> Electronic Banking Services
> Fiserv
> Office: 503-746-0643
> Fax: 503-617-0291

[WiX-users] FW: Embedded UI, custom action and WiX assembly

[Alexander Kozlenko]

Any suggestions?

-Original Message-
From: Alexander Kozlenko [mailto:alexander.kozle...@hotmail.com] 
Sent: Tuesday, September 21, 2010 11:58 PM
To: 'General discussion for Windows Installer XML toolset.'
Subject: [WiX-users] Embedded UI, custom action and WiX assembly

Hello. I have installer with embedded UI and managed custom action. Is there
any way to reuse Microsoft.Deployment.WindowsInstaller assembly instead of
duplicate it in both binary streams (for UI assembly and for CA assembly)?
Thanks.

Alexander Kozlenko 


--
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Error in Custom Action

[Alexander Kozlenko]

What is the best way to block installation on error in Custom Action? I used
ActionResult.Failure result value but installation continues to install.
Only throwing an exception of type InstallerException helps me to block
installation. Thanks.

 

Alexander Kozlenko

--
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Heat.exe

[David Amey]

Hi everyone!

I've been struggling with this problem for a while, if anyone can help I would 
really appreciate it.

Basically I'm using heat to harvest a folder, simples. However I'm using the 
"-var" property in the command line (to replace the "sourceDir" in the output 
component's source attribute), using a variable declared in the main.wxs. This 
replaces the "sourceDir" as expected, but when it comes to candle to compile , 
it flags an error as if the variable isn't populated. 

Sorry if this was hard to follow or understand (incredibly frustrated!), but if 
you think you can help I will try and explain a bit better. 

Thanks in advance!

David Amey
Technical Developer
--
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] XmlConfig not referencing other XmlConfig elements

[pcristini]

I'm trying to produce this output in my config file:




smarmyarmy





This is the code I'm attempting to use:











When I run it I get an error of:
Failed to find node: Config.DNS.Path in XML file: C:\Program Files
(x86)\Pareto Systems\CRM Admin Tool\CRMAdminTool.exe.config, system error:
-2147020584


Every example I've seen uses the ElementPath the same way I am... 
Also, what does this do if the element already exists? Will it create a new
one? Is it possible to make it so it updateorcreate kinda thing?


-- 
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/XmlConfig-not-referencing-other-XmlConfig-elements-tp5560885p5560885.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] License agreement dialog does not display the license agreement text

[Bruce Cran]

On Wed, 22 Sep 2010 12:52:57 -0700
Lena Vinogradov  wrote:

> When License agreement dialog is displayed the entire text of the
> license agreement rtf file is missing and it only appears after I
> touch the scroll bar on the right.

I think this happens if you have 'advanced' RTF content in the file.
When it happened to me I found opening it in WordPad and doing a "Save
As", overwriting the original file solved the problem.

-- 
Bruce Cran

--
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] License agreement dialog does not display the license agreement text

[Lena Vinogradov]

Hi,

When License agreement dialog is displayed the entire text of the license 
agreement rtf file is missing and it only appears after I touch the scroll bar 
on the right.

I used an example in the WIX tutorial and the only lines I added to my 
installer are:








Can anybody help please?

Thanks in advance,

Elena Vinogradov
Software developer - Spotlight on Messaging
Quest Software
www.quest.com

--
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Command LineParameterstoDeferred CustomAction on Vista

[Matt Walker]

Cool, thanks All!!


Matt Walker
Installation Development
200 Kelly Road | Quakertown, PA 18951
Phone: +1 215.529.9900, x192 | 800.836.5440 
Fax: +1 215.536.9249
http://www.synergissoftware.com/
Adept Engineering Document Management & Workflow
This message (and any associated files) is intended only for the use of the 
individual or entity to which it is addressed and may contain information that 
is confidential, subject to copyright or constitutes a trade secret. If you are 
not the intended recipient you are hereby notified that any dissemination, 
copying or distribution of this message, or files associated with this message, 
is strictly prohibited. If you have received this message in error, please 
notify us immediately by replying to the message and deleting it from your 
computer. Messages sent to and from us may be monitored.
Internet communications cannot be guaranteed to be secure or error-free as 
information could be intercepted, corrupted, lost, destroyed, arrive late or 
incomplete, or contain viruses. Therefore, we do not accept responsibility for 
any errors or omissions that are present in this message, or any attachment, 
that have arisen as a result of e-mail transmission. If verification is 
required, please request a hard-copy version. Any views or opinions presented 
are solely those of the author and do not necessarily represent those of the 
company.
-Original Message-

From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com] 
Sent: Wednesday, September 22, 2010 3:41 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users]Command LineParameterstoDeferred CustomAction on Vista

I believe that is correct. I believe this is the sole purpose of the 
SecureCustomProperties property.

If you do not pass the data via CustomActionData *and* you do not add the 
property to SecureCustomProperties, then you will _not_ have access to that 
data in any way in the deferred custom action.

If you add the property to SecureCustomProperties, then you can access the data 
via the standard mechanisms for getting property values. The only properties 
you can access are the ones listed in SecureCustomProperties and a handful of 
others that are added by default by Windows Installer, check the SDK 
documentation for details.

If you add the data to CustomActionData, then you'll be able to access it via 
the CustomActionData mechanism in the deferred custom action.

If you do both, then you'll have access to the data via both mechanisms.

Edwin G. Castro
Software Developer - Staff
Electronic Banking Services
Fiserv
Office: 503-746-0643
Fax: 503-617-0291
www.fiserv.com
Please consider the environment before printing this e-mail


> -Original Message-
> From: Matt Walker [mailto:matt.wal...@synergis.com]
> Sent: Wednesday, September 22, 2010 12:16 PM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Command LineParameterstoDeferred
> CustomAction on Vista
>
> So adding the property to SecureCustomProperties also allows access to the
> property value directly at Deferred Action time (as opposed to passing it
> through CustomActionData)?
>
>
> Matt Walker
> Installation Development
> 200 Kelly Road | Quakertown, PA 18951
> Phone: +1 215.529.9900, x192 | 800.836.5440
> Fax: +1 215.536.9249
> http://www.synergissoftware.com/
> Adept Engineering Document Management & Workflow This message (and
> any associated files) is intended only for the use of the individual or 
> entity to
> which it is addressed and may contain information that is confidential,
> subject to copyright or constitutes a trade secret. If you are not the 
> intended
> recipient you are hereby notified that any dissemination, copying or
> distribution of this message, or files associated with this message, is 
> strictly
> prohibited. If you have received this message in error, please notify us
> immediately by replying to the message and deleting it from your computer.
> Messages sent to and from us may be monitored.
> Internet communications cannot be guaranteed to be secure or error-free as
> information could be intercepted, corrupted, lost, destroyed, arrive late or
> incomplete, or contain viruses. Therefore, we do not accept responsibility for
> any errors or omissions that are present in this message, or any attachment,
> that have arisen as a result of e-mail transmission. If verification is 
> required,
> please request a hard-copy version. Any views or opinions presented are
> solely those of the author and do not necessarily represent those of the
> company.
> -Original Message-
>
> From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com]
> Sent: Wednesday, September 22, 2010 3:03 PM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users]Command LineParameterstoDeferred CustomAction
> on Vista
>
> Imagine that you have table-driven custom action. This custom action would
> need to read th

Re: [WiX-users] Command LineParameterstoDeferred CustomAction on Vista

[Castro, Edwin G. (Hillsboro)]

I believe that is correct. I believe this is the sole purpose of the 
SecureCustomProperties property.

If you do not pass the data via CustomActionData *and* you do not add the 
property to SecureCustomProperties, then you will _not_ have access to that 
data in any way in the deferred custom action.

If you add the property to SecureCustomProperties, then you can access the data 
via the standard mechanisms for getting property values. The only properties 
you can access are the ones listed in SecureCustomProperties and a handful of 
others that are added by default by Windows Installer, check the SDK 
documentation for details.

If you add the data to CustomActionData, then you'll be able to access it via 
the CustomActionData mechanism in the deferred custom action.

If you do both, then you'll have access to the data via both mechanisms.

Edwin G. Castro
Software Developer - Staff
Electronic Banking Services
Fiserv
Office: 503-746-0643
Fax: 503-617-0291
www.fiserv.com
Please consider the environment before printing this e-mail


> -Original Message-
> From: Matt Walker [mailto:matt.wal...@synergis.com]
> Sent: Wednesday, September 22, 2010 12:16 PM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Command LineParameterstoDeferred
> CustomAction on Vista
>
> So adding the property to SecureCustomProperties also allows access to the
> property value directly at Deferred Action time (as opposed to passing it
> through CustomActionData)?
>
>
> Matt Walker
> Installation Development
> 200 Kelly Road | Quakertown, PA 18951
> Phone: +1 215.529.9900, x192 | 800.836.5440
> Fax: +1 215.536.9249
> http://www.synergissoftware.com/
> Adept Engineering Document Management & Workflow This message (and
> any associated files) is intended only for the use of the individual or 
> entity to
> which it is addressed and may contain information that is confidential,
> subject to copyright or constitutes a trade secret. If you are not the 
> intended
> recipient you are hereby notified that any dissemination, copying or
> distribution of this message, or files associated with this message, is 
> strictly
> prohibited. If you have received this message in error, please notify us
> immediately by replying to the message and deleting it from your computer.
> Messages sent to and from us may be monitored.
> Internet communications cannot be guaranteed to be secure or error-free as
> information could be intercepted, corrupted, lost, destroyed, arrive late or
> incomplete, or contain viruses. Therefore, we do not accept responsibility for
> any errors or omissions that are present in this message, or any attachment,
> that have arisen as a result of e-mail transmission. If verification is 
> required,
> please request a hard-copy version. Any views or opinions presented are
> solely those of the author and do not necessarily represent those of the
> company.
> -Original Message-
>
> From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com]
> Sent: Wednesday, September 22, 2010 3:03 PM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users]Command LineParameterstoDeferred CustomAction
> on Vista
>
> Imagine that you have table-driven custom action. This custom action would
> need to read the values out of a table to determine what work to do. In this
> scenario you need an immediate custom action which can read the
> appropriate tables and stuff the data into CustomActionData. Then a
> deferred custom action can read the data out of CustomActionData and
> perform the actual work. This two-stage approach is necessary because
> Windows Installer does not allow deferred custom actions to read many of
> the tables in the MSI database. If you written a table-driven custom action
> then you likely also have custom tables which are most definitely not
> available in the deferred custom action.
>
> For very simple deferred custom actions where you only need to pass in a
> very small number data to the deferred custom action, such as a single
> property value, then it would be appropriate to add the property to
> SecureCustomProperties.
>
> Edwin G. Castro
> Software Developer - Staff
> Electronic Banking Services
> Fiserv
> Office: 503-746-0643
> Fax: 503-617-0291
> www.fiserv.com
> P Please consider the environment before printing this e-mail
>
>
> > -Original Message-
> > From: Matt Walker [mailto:matt.wal...@synergis.com]
> > Sent: Wednesday, September 22, 2010 10:48 AM
> > To: General discussion for Windows Installer XML toolset.
> > Subject: Re: [WiX-users] Command LineParameterstoDeferred
> CustomAction
> > on Vista
> >
> > I know how to get stuff to-out of Custom Action Data, but I guess I
> > really would like to know when it is absolutely necessary to use it.
> >
> > From you link with an emphasis on the first part...
> >
> > "Custom actions are run at the end of an installation and cannot
> > access information about the inst

Re: [WiX-users] Command LineParameterstoDeferred CustomAction on Vista

[Matt Walker]

So adding the property to SecureCustomProperties also allows access to the 
property value directly at Deferred Action time (as opposed to passing it 
through CustomActionData)?


Matt Walker
Installation Development
200 Kelly Road | Quakertown, PA 18951
Phone: +1 215.529.9900, x192 | 800.836.5440 
Fax: +1 215.536.9249
http://www.synergissoftware.com/
Adept Engineering Document Management & Workflow
This message (and any associated files) is intended only for the use of the 
individual or entity to which it is addressed and may contain information that 
is confidential, subject to copyright or constitutes a trade secret. If you are 
not the intended recipient you are hereby notified that any dissemination, 
copying or distribution of this message, or files associated with this message, 
is strictly prohibited. If you have received this message in error, please 
notify us immediately by replying to the message and deleting it from your 
computer. Messages sent to and from us may be monitored.
Internet communications cannot be guaranteed to be secure or error-free as 
information could be intercepted, corrupted, lost, destroyed, arrive late or 
incomplete, or contain viruses. Therefore, we do not accept responsibility for 
any errors or omissions that are present in this message, or any attachment, 
that have arisen as a result of e-mail transmission. If verification is 
required, please request a hard-copy version. Any views or opinions presented 
are solely those of the author and do not necessarily represent those of the 
company.
-Original Message-

From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com] 
Sent: Wednesday, September 22, 2010 3:03 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users]Command LineParameterstoDeferred CustomAction on Vista

Imagine that you have table-driven custom action. This custom action would need 
to read the values out of a table to determine what work to do. In this 
scenario you need an immediate custom action which can read the appropriate 
tables and stuff the data into CustomActionData. Then a deferred custom action 
can read the data out of CustomActionData and perform the actual work. This 
two-stage approach is necessary because Windows Installer does not allow 
deferred custom actions to read many of the tables in the MSI database. If you 
written a table-driven custom action then you likely also have custom tables 
which are most definitely not available in the deferred custom action.

For very simple deferred custom actions where you only need to pass in a very 
small number data to the deferred custom action, such as a single property 
value, then it would be appropriate to add the property to 
SecureCustomProperties.

Edwin G. Castro
Software Developer - Staff
Electronic Banking Services
Fiserv
Office: 503-746-0643
Fax: 503-617-0291
www.fiserv.com
Please consider the environment before printing this e-mail


> -Original Message-
> From: Matt Walker [mailto:matt.wal...@synergis.com]
> Sent: Wednesday, September 22, 2010 10:48 AM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Command LineParameterstoDeferred
> CustomAction on Vista
>
> I know how to get stuff to-out of Custom Action Data, but I guess I really
> would like to know when it is absolutely necessary to use it.
>
> From you link with an emphasis on the first part...
>
> "Custom actions are run at the end of an installation and cannot access
> information about the installation; the CustomActionData property allows
> you to store information about the installation that can be read by the
> custom action."
>
> I guess my question boils down to... why do I NOT have to store the value of
> my public property from the Property Table (and not set in any way via the
> UI) in CustomActionData?  I can access the original property and its value 
> fine
> with my Deferred action that is run in System Context.
>
>
>
>
> Matt Walker
> Installation Development
> 200 Kelly Road | Quakertown, PA 18951
> Phone: +1 215.529.9900, x192 | 800.836.5440
> Fax: +1 215.536.9249
> http://www.synergissoftware.com/
> Adept Engineering Document Management & Workflow This message (and
> any associated files) is intended only for the use of the individual or 
> entity to
> which it is addressed and may contain information that is confidential,
> subject to copyright or constitutes a trade secret. If you are not the 
> intended
> recipient you are hereby notified that any dissemination, copying or
> distribution of this message, or files associated with this message, is 
> strictly
> prohibited. If you have received this message in error, please notify us
> immediately by replying to the message and deleting it from your computer.
> Messages sent to and from us may be monitored.
> Internet communications cannot be guaranteed to be secure or error-free as
> information could be intercepted, corrupted, lost, destroyed, arrive late

Re: [WiX-users] Command LineParameterstoDeferred CustomAction on Vista

[Castro, Edwin G. (Hillsboro)]

Imagine that you have table-driven custom action. This custom action would need 
to read the values out of a table to determine what work to do. In this 
scenario you need an immediate custom action which can read the appropriate 
tables and stuff the data into CustomActionData. Then a deferred custom action 
can read the data out of CustomActionData and perform the actual work. This 
two-stage approach is necessary because Windows Installer does not allow 
deferred custom actions to read many of the tables in the MSI database. If you 
written a table-driven custom action then you likely also have custom tables 
which are most definitely not available in the deferred custom action.

For very simple deferred custom actions where you only need to pass in a very 
small number data to the deferred custom action, such as a single property 
value, then it would be appropriate to add the property to 
SecureCustomProperties.

Edwin G. Castro
Software Developer - Staff
Electronic Banking Services
Fiserv
Office: 503-746-0643
Fax: 503-617-0291
www.fiserv.com
Please consider the environment before printing this e-mail


> -Original Message-
> From: Matt Walker [mailto:matt.wal...@synergis.com]
> Sent: Wednesday, September 22, 2010 10:48 AM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Command LineParameterstoDeferred
> CustomAction on Vista
>
> I know how to get stuff to-out of Custom Action Data, but I guess I really
> would like to know when it is absolutely necessary to use it.
>
> From you link with an emphasis on the first part...
>
> "Custom actions are run at the end of an installation and cannot access
> information about the installation; the CustomActionData property allows
> you to store information about the installation that can be read by the
> custom action."
>
> I guess my question boils down to... why do I NOT have to store the value of
> my public property from the Property Table (and not set in any way via the
> UI) in CustomActionData?  I can access the original property and its value 
> fine
> with my Deferred action that is run in System Context.
>
>
>
>
> Matt Walker
> Installation Development
> 200 Kelly Road | Quakertown, PA 18951
> Phone: +1 215.529.9900, x192 | 800.836.5440
> Fax: +1 215.536.9249
> http://www.synergissoftware.com/
> Adept Engineering Document Management & Workflow This message (and
> any associated files) is intended only for the use of the individual or 
> entity to
> which it is addressed and may contain information that is confidential,
> subject to copyright or constitutes a trade secret. If you are not the 
> intended
> recipient you are hereby notified that any dissemination, copying or
> distribution of this message, or files associated with this message, is 
> strictly
> prohibited. If you have received this message in error, please notify us
> immediately by replying to the message and deleting it from your computer.
> Messages sent to and from us may be monitored.
> Internet communications cannot be guaranteed to be secure or error-free as
> information could be intercepted, corrupted, lost, destroyed, arrive late or
> incomplete, or contain viruses. Therefore, we do not accept responsibility for
> any errors or omissions that are present in this message, or any attachment,
> that have arisen as a result of e-mail transmission. If verification is 
> required,
> please request a hard-copy version. Any views or opinions presented are
> solely those of the author and do not necessarily represent those of the
> company.
> -Original Message-
>
> From: Chad Petersen [mailto:chad.peter...@harlandfs.com]
> Sent: Wednesday, September 22, 2010 1:27 PM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Command LineParameterstoDeferred
> CustomAction on Vista
>
> CustomActionData is that magical packet of information passed from the
> installer to your deferred CustomAction using the Value= attribute.
>
> Then, your .exe (or VBScript or Javascript) has to set a variable to the 
> value of
> Session.Property("CustomActionData"); so it gets a copy of this information
> to use.
>
> This info might help a little
>
> http://msdn.microsoft.com/en-us/library/2w2fhwzz(VS.71).aspx
>
>
>
> -Original Message-
> From: Matt Walker [mailto:matt.wal...@synergis.com]
> Sent: Wednesday, September 22, 2010 10:07 AM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Command Line ParameterstoDeferred
> CustomAction on Vista
>
> I guess I'm still a little foggy on it so I'll keep digging.  If 
> CustomActionData is
> needed to get values to Deferred Custom Actions, how then is my property
> value, populated in the Property Table, getting to my deferred action?  In
> addition to having the property pre-populated in the table, I also added it to
> SecureCustomProperties.  However I'm not using the Set Directory CA
> mechanism to get the value to CustomActionData.

Re: [WiX-users] Command LineParameterstoDeferred CustomAction on Vista

[Matt Walker]

I know how to get stuff to-out of Custom Action Data, but I guess I really 
would like to know when it is absolutely necessary to use it.

From you link with an emphasis on the first part...

"Custom actions are run at the end of an installation and cannot access 
information about the installation; the CustomActionData property allows you to 
store information about the installation that can be read by the custom action."

I guess my question boils down to... why do I NOT have to store the value of my 
public property from the Property Table (and not set in any way via the UI) in 
CustomActionData?  I can access the original property and its value fine with 
my Deferred action that is run in System Context.




Matt Walker
Installation Development
200 Kelly Road | Quakertown, PA 18951
Phone: +1 215.529.9900, x192 | 800.836.5440 
Fax: +1 215.536.9249
http://www.synergissoftware.com/
Adept Engineering Document Management & Workflow
This message (and any associated files) is intended only for the use of the 
individual or entity to which it is addressed and may contain information that 
is confidential, subject to copyright or constitutes a trade secret. If you are 
not the intended recipient you are hereby notified that any dissemination, 
copying or distribution of this message, or files associated with this message, 
is strictly prohibited. If you have received this message in error, please 
notify us immediately by replying to the message and deleting it from your 
computer. Messages sent to and from us may be monitored.
Internet communications cannot be guaranteed to be secure or error-free as 
information could be intercepted, corrupted, lost, destroyed, arrive late or 
incomplete, or contain viruses. Therefore, we do not accept responsibility for 
any errors or omissions that are present in this message, or any attachment, 
that have arisen as a result of e-mail transmission. If verification is 
required, please request a hard-copy version. Any views or opinions presented 
are solely those of the author and do not necessarily represent those of the 
company.
-Original Message-

From: Chad Petersen [mailto:chad.peter...@harlandfs.com] 
Sent: Wednesday, September 22, 2010 1:27 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Command LineParameterstoDeferred CustomAction on Vista

CustomActionData is that magical packet of information passed from the 
installer to your deferred CustomAction using the Value= attribute.

Then, your .exe (or VBScript or Javascript) has to set a variable to the value 
of Session.Property("CustomActionData"); so it gets a copy of this information 
to use.

This info might help a little

http://msdn.microsoft.com/en-us/library/2w2fhwzz(VS.71).aspx



-Original Message-
From: Matt Walker [mailto:matt.wal...@synergis.com] 
Sent: Wednesday, September 22, 2010 10:07 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Command Line ParameterstoDeferred CustomAction on Vista

I guess I'm still a little foggy on it so I'll keep digging.  If
CustomActionData is needed to get values to Deferred Custom Actions, how
then is my property value, populated in the Property Table, getting to
my deferred action?  In addition to having the property pre-populated in
the table, I also added it to SecureCustomProperties.  However I'm not
using the Set Directory CA mechanism to get the value to
CustomActionData.

I don't know if I mentioned this before, but my Deferred Custom Action
fires an .exe stored in the Binary Table with the following command line
parameters being passed [ProductCode] [OURVERSION], the later being the
pre-populated property.

I don't know why, but I can't seem to get a handle on this!  :(


Matt Walker
Installation Development
200 Kelly Road | Quakertown, PA 18951
Phone: +1 215.529.9900, x192 | 800.836.5440 
Fax: +1 215.536.9249
http://www.synergissoftware.com/
Adept Engineering Document Management & Workflow
This message (and any associated files) is intended only for the use of the 
individual or entity to which it is addressed and may contain information that 
is confidential, subject to copyright or constitutes a trade secret. If you are 
not the intended recipient you are hereby notified that any dissemination, 
copying or distribution of this message, or files associated with this message, 
is strictly prohibited. If you have received this message in error, please 
notify us immediately by replying to the message and deleting it from your 
computer. Messages sent to and from us may be monitored.
Internet communications cannot be guaranteed to be secure or error-free as 
information could be intercepted, corrupted, lost, destroyed, arrive late or 
incomplete, or contain viruses. Therefore, we do not accept responsibility for 
any errors or omissions that are present in this message, or any attachment, 
that have arisen as a result of e-mail transmission. If verification is 
required, pl

Re: [WiX-users] Command Line ParameterstoDeferred CustomAction on Vista

[Chad Petersen]

CustomActionData is that magical packet of information passed from the 
installer to your deferred CustomAction using the Value= attribute.

Then, your .exe (or VBScript or Javascript) has to set a variable to the value 
of Session.Property("CustomActionData"); so it gets a copy of this information 
to use.

This info might help a little

http://msdn.microsoft.com/en-us/library/2w2fhwzz(VS.71).aspx



-Original Message-
From: Matt Walker [mailto:matt.wal...@synergis.com] 
Sent: Wednesday, September 22, 2010 10:07 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Command Line ParameterstoDeferred CustomAction on Vista

I guess I'm still a little foggy on it so I'll keep digging.  If
CustomActionData is needed to get values to Deferred Custom Actions, how
then is my property value, populated in the Property Table, getting to
my deferred action?  In addition to having the property pre-populated in
the table, I also added it to SecureCustomProperties.  However I'm not
using the Set Directory CA mechanism to get the value to
CustomActionData.

I don't know if I mentioned this before, but my Deferred Custom Action
fires an .exe stored in the Binary Table with the following command line
parameters being passed [ProductCode] [OURVERSION], the later being the
pre-populated property.

I don't know why, but I can't seem to get a handle on this!  :(


Matt Walker
Installation Development
200 Kelly Road | Quakertown, PA 18951
Phone: +1 215.529.9900, x192 | 800.836.5440 
Fax: +1 215.536.9249
http://www.synergissoftware.com/
Adept Engineering Document Management & Workflow
This message (and any associated files) is intended only for the use of the 
individual or entity to which it is addressed and may contain information that 
is confidential, subject to copyright or constitutes a trade secret. If you are 
not the intended recipient you are hereby notified that any dissemination, 
copying or distribution of this message, or files associated with this message, 
is strictly prohibited. If you have received this message in error, please 
notify us immediately by replying to the message and deleting it from your 
computer. Messages sent to and from us may be monitored.
Internet communications cannot be guaranteed to be secure or error-free as 
information could be intercepted, corrupted, lost, destroyed, arrive late or 
incomplete, or contain viruses. Therefore, we do not accept responsibility for 
any errors or omissions that are present in this message, or any attachment, 
that have arisen as a result of e-mail transmission. If verification is 
required, please request a hard-copy version. Any views or opinions presented 
are solely those of the author and do not necessarily represent those of the 
company.
-Original Message-

From: Wilson, Phil [mailto:phil.wil...@invensys.com] 
Sent: Wednesday, September 22, 2010 12:52 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Command Line Parameters toDeferred CustomAction
on Vista

They are still two separate items. SecureCustomProperties is need if you
want to pass properties from the UI to the execute sequence, whether
they get passed to custom actions or not. If you pass them to a
immediate custom actions there's no need to use CustomActionData. So if
you wanted to collect a property value in the UI sequence AND pass it to
a deferred custom action then you'd need to use SCP to get it into the
execute sequence AND use CustomActionData to pass it to a deferred
custom action. 

You might be thinking that CustomActionData is a single property, but
it's not. Every deferred custom action can have its own CustomActionData
associated with it. Yes, it's used to pass property values into deferred
custom actions. You simply cannot directly get property values in
deferred custom actions, that's what CustomActionData is for. 

There'a a paragraph or two at the end here
http://msdn.microsoft.com/en-us/library/aa370543(VS.85).aspx 

Phil Wilson 


-Original Message-
From: Matt Walker [mailto:matt.wal...@synergis.com] 
Sent: Tuesday, September 21, 2010 6:45 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Command Line Parameters to Deferred
CustomAction on Vista

Since both worked in my scenario, I still, really don't know the
difference.

When you say SCPs is used to pass property values to the execute
sequence, does that include access during or for deferred custom
actions?  Or, is CAD used to pass information to the deferred actions?

Would there be a good example to illustrate the need for the use of
CustomActionData where simply adding a property to
SecureCustomProperties would not provide access during the deferred
sequence?

Any further help greatly appreciated.

-Original Message-
From: Wilson, Phil [mailto:phil.wil...@invensys.com] 
Sent: Tuesday, September 21, 2010 5:17 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re:

Re: [WiX-users] Command Line Parameters toDeferred CustomAction on Vista

[Matt Walker]

I guess I'm still a little foggy on it so I'll keep digging.  If
CustomActionData is needed to get values to Deferred Custom Actions, how
then is my property value, populated in the Property Table, getting to
my deferred action?  In addition to having the property pre-populated in
the table, I also added it to SecureCustomProperties.  However I'm not
using the Set Directory CA mechanism to get the value to
CustomActionData.

I don't know if I mentioned this before, but my Deferred Custom Action
fires an .exe stored in the Binary Table with the following command line
parameters being passed [ProductCode] [OURVERSION], the later being the
pre-populated property.

I don't know why, but I can't seem to get a handle on this!  :(


Matt Walker
Installation Development
200 Kelly Road | Quakertown, PA 18951
Phone: +1 215.529.9900, x192 | 800.836.5440 
Fax: +1 215.536.9249
http://www.synergissoftware.com/
Adept Engineering Document Management & Workflow
This message (and any associated files) is intended only for the use of the 
individual or entity to which it is addressed and may contain information that 
is confidential, subject to copyright or constitutes a trade secret. If you are 
not the intended recipient you are hereby notified that any dissemination, 
copying or distribution of this message, or files associated with this message, 
is strictly prohibited. If you have received this message in error, please 
notify us immediately by replying to the message and deleting it from your 
computer. Messages sent to and from us may be monitored.
Internet communications cannot be guaranteed to be secure or error-free as 
information could be intercepted, corrupted, lost, destroyed, arrive late or 
incomplete, or contain viruses. Therefore, we do not accept responsibility for 
any errors or omissions that are present in this message, or any attachment, 
that have arisen as a result of e-mail transmission. If verification is 
required, please request a hard-copy version. Any views or opinions presented 
are solely those of the author and do not necessarily represent those of the 
company.
-Original Message-

From: Wilson, Phil [mailto:phil.wil...@invensys.com] 
Sent: Wednesday, September 22, 2010 12:52 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Command Line Parameters toDeferred CustomAction
on Vista

They are still two separate items. SecureCustomProperties is need if you
want to pass properties from the UI to the execute sequence, whether
they get passed to custom actions or not. If you pass them to a
immediate custom actions there's no need to use CustomActionData. So if
you wanted to collect a property value in the UI sequence AND pass it to
a deferred custom action then you'd need to use SCP to get it into the
execute sequence AND use CustomActionData to pass it to a deferred
custom action. 

You might be thinking that CustomActionData is a single property, but
it's not. Every deferred custom action can have its own CustomActionData
associated with it. Yes, it's used to pass property values into deferred
custom actions. You simply cannot directly get property values in
deferred custom actions, that's what CustomActionData is for. 

There'a a paragraph or two at the end here
http://msdn.microsoft.com/en-us/library/aa370543(VS.85).aspx 

Phil Wilson 


-Original Message-
From: Matt Walker [mailto:matt.wal...@synergis.com] 
Sent: Tuesday, September 21, 2010 6:45 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Command Line Parameters to Deferred
CustomAction on Vista

Since both worked in my scenario, I still, really don't know the
difference.

When you say SCPs is used to pass property values to the execute
sequence, does that include access during or for deferred custom
actions?  Or, is CAD used to pass information to the deferred actions?

Would there be a good example to illustrate the need for the use of
CustomActionData where simply adding a property to
SecureCustomProperties would not provide access during the deferred
sequence?

Any further help greatly appreciated.

-Original Message-
From: Wilson, Phil [mailto:phil.wil...@invensys.com] 
Sent: Tuesday, September 21, 2010 5:17 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Command Line Parameters to Deferred
CustomAction on Vista

Briefly, CustomActionData is a parameter passing scheme to get property
values passed to a deferred custom action. SecureCustomProperties is a
list of properties that you want to pass from the UI sequence (where you
probably collected their values) across the context boundary into the
execute sequence. 

Phil Wilson 

-Original Message-
From: Superfreak3 [mailto:matt.wal...@synergis.com] 
Sent: Tuesday, September 21, 2010 11:59 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Command Line Parameters to Deferred Custom
Action on Vista


So what exactly is the difference

Re: [WiX-users] Command Line Parameters to Deferred CustomAction on Vista

[Wilson, Phil]

They are still two separate items. SecureCustomProperties is need if you want 
to pass properties from the UI to the execute sequence, whether they get passed 
to custom actions or not. If you pass them to a immediate custom actions 
there's no need to use CustomActionData. So if you wanted to collect a property 
value in the UI sequence AND pass it to a deferred custom action then you'd 
need to use SCP to get it into the execute sequence AND use CustomActionData to 
pass it to a deferred custom action. 

You might be thinking that CustomActionData is a single property, but it's not. 
Every deferred custom action can have its own CustomActionData associated with 
it. Yes, it's used to pass property values into deferred custom actions. You 
simply cannot directly get property values in deferred custom actions, that's 
what CustomActionData is for. 

There'a a paragraph or two at the end here 
http://msdn.microsoft.com/en-us/library/aa370543(VS.85).aspx 

Phil Wilson 


-Original Message-
From: Matt Walker [mailto:matt.wal...@synergis.com] 
Sent: Tuesday, September 21, 2010 6:45 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Command Line Parameters to Deferred CustomAction on 
Vista

Since both worked in my scenario, I still, really don't know the
difference.

When you say SCPs is used to pass property values to the execute
sequence, does that include access during or for deferred custom
actions?  Or, is CAD used to pass information to the deferred actions?

Would there be a good example to illustrate the need for the use of
CustomActionData where simply adding a property to
SecureCustomProperties would not provide access during the deferred
sequence?

Any further help greatly appreciated.

-Original Message-
From: Wilson, Phil [mailto:phil.wil...@invensys.com] 
Sent: Tuesday, September 21, 2010 5:17 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Command Line Parameters to Deferred
CustomAction on Vista

Briefly, CustomActionData is a parameter passing scheme to get property
values passed to a deferred custom action. SecureCustomProperties is a
list of properties that you want to pass from the UI sequence (where you
probably collected their values) across the context boundary into the
execute sequence. 

Phil Wilson 

-Original Message-
From: Superfreak3 [mailto:matt.wal...@synergis.com] 
Sent: Tuesday, September 21, 2010 11:59 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Command Line Parameters to Deferred Custom
Action on Vista


So what exactly is the difference between SecureCustomProperties and
CustomActionData?  I still do not fully understand this.

We have a public property that holds a string that we write to the
registry
in certain cases.  Is is held in the Property table.  Let's say it
contains
8.1.2.3 and is called OURVERSION.

I have a little widget that runs near the end of the install that tests
the
condition for the registry edit and edits accordingly.  I used a Set
Property custom action sequenced in the Immediate Sequence to set the
above
mentioned property to something like PASSDATAACTION.  

Then, in the Deferrec Sequence action, I reference CustomActionData that
now
holds the value I passed.  All seems to work OK here.

I then thought, lets add the original property, OURVERSION, to
SecureCustomProperties and just reference that directly as a parameter
in my
Deferred action, guess what.  This works too.

So, I'm unclear as to the true purpose of each.

I know this really is off WiX topic, but I've gotten great help here
before
so any now is greatly appreciated.  The scenario described above may not
be
exactly what is going on, but just to give an example.

Thanks in advance for any help!!
-- 
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Command-Li
ne-Parameters-to-Deferred-Custom-Action-on-Vista-tp2652448p733.html
Sent from the wix-users mailing list archive at Nabble.com.


--
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


*** Confidentiality Notice: This e-mail, including any associated or
attached files, is intended solely for the individual or entity to which
it is addressed. This e-mail is confidential and may well also be
legally privileged. If you have received it in error, you are on notice
of its status. Please notify the sender immediately by reply e-mail and
then delete this message from your system. Please do not copy it or use
it for any purposes, or disclose its contents to any other person. This
email comes from a division o

[WiX-users] Sub-feature in separate wxs file

[pcristini]

I have all my components separated out into multiple files and am trying to
achieve a structure like this:

Main app:
  - Plugins
 - Plugin 1
 - User Plugin
- User Sync Plugin (this one is not showing up)
 - Plugin 3

And I don't want the Plugin.Users.wxs file to have any reference to the
Plugin.UserSync.wxs
Is it possibly because I have multiple FeatureRefs to the same feature?

Plugins.wxs:











Plugin.Users.wxs:




Plugin.UsersSync.wxs:





-- 
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Sub-feature-in-separate-wxs-file-tp5559722p5559722.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Installing a file in to multiple folders

[Sean Farrow]

Hi:
Any pointers to the thread please?
Cheers
Sean.

-Original Message-
From: Pally Sandher [mailto:pally.sand...@iesve.com] 
Sent: 21 September 2010 12:21
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Installing a file in to multiple folders

If it's completely at the users discretion how many copy operations
you'll need to do then yes if you want the package to uninstall cleanly
(and support rollback properly). There was a very similar requirement on
this list in the last few months which should be able to point you in
the right direction.

Palbinder Sandher 
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500 
F: +44 (0) 141 945 8501 

http://www.iesve.com 
**Design, Simulate + Innovate with the **
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: Sean Farrow [mailto:sean.far...@seanfarrow.co.uk] 
Sent: 21 September 2010 11:25
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Installing a file in to multiple folders

Hi: 
Ok, given that I won't know the number of files that need copying before
the installation starts. Given this is the situation, is it better to
populate the DuplicateFile table from a custom action?
Any help appreciated.
Sean.

-Original Message-
From: Pally Sandher [mailto:pally.sand...@iesve.com]
Sent: 21 September 2010 10:23
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Installing a file in to multiple folders

Or do it the right way & use the CopyFile element ->
http://wix.sourceforge.net/manual-wix3/wix_xsd_copyfile.htm 

Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501 

http://www.iesve.com
**Design, Simulate + Innovate with the **
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: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com]
Sent: 21 September 2010 09:22
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Installing a file in to multiple folders

Even better, do nothing :)
http://robmensching.com/blog/posts/2007/6/1/quotSmart-cabbingquot-added-
to-WiX-toolset

That is, create multiple components with the same source file and Wix
handles the rest.

-Original Message-
From: Fabio Di Lorenzo [mailto:fa...@dilorenzo.ch]
Sent: 20 September 2010 18:13
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Installing a file in to multiple folders

You mean having this file only once in your cabinet but installing it to
several places?

Then the DuplicateFile table is your friend!

kind regards,
fabio

On Mon, Sep 20, 2010 at 7:08 PM, Sean Farrow
wrote:

> Hi:
> Is it possible when running a msi to install a file in to multiple
folders.
> If anyone has had any experience in doing this I'd be greatful for any
help.
> Regards
> Sean.
>
>

--
> Start uncovering the many advantages of virtual appliances and start 
> using them to simplify application deployment and accelerate your 
> shift to cloud computing.
> http://p.sf.net/sfu/novell-sfdev2dev
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>

--
Start uncovering the many advantages of virtual appliances and start
using them to simplify application deployment and accelerate your shift
to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


http://www.sdl.com";>http://www.sdl.com/images/email
logo_150dpi-01.png" alt="www.sdl.com" border="0"/>  http://www.sdl.com";
style="color:005740; font-weight: bold">www.sdl.com  
 SDL PLC confidential,
all rights reserved. If you are not the intended recipient of this
mail SDL requests and requires that you delete it without acting upon or
copying any of its contents, and we further request that you advise
us. SDL PLC is a public limited company registered in England and
Wales.  Registered number: 02675207. Registered address: Globe
House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, UK.





--
Start uncovering the many advantages of virtual appliances and start
using them to simplify application deployment and accelerate your shift
to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
___