[WiX-users] Using transforms (regular) to install mulitple times per application

2013-03-12 Thread jeamis
What I am trying to do is to allow customer bootstrappers the ability to install my package for thier application. In some cases the customer has two applications (installed in one setup) that use my product. So how can I use a transform that will allow this customer to install my product twice?

Re: [WiX-users] Using transforms (regular) to install mulitple times per application

2013-03-12 Thread David Watson
Hi, Shared components can be managed several ways how you implement depends on your application. If your application is purely designed to be used by others you can ship a merge module or wixlib that they can include inside their MSI and install privately into their program folder, this puts them

Re: [WiX-users] Updating the License Agreement

2013-03-12 Thread Neil Sleightholm
How are you saving your rtf, I would advise using WordPad as that creates very simple rtf files (compared to Word). -Original Message- From: Chaitanya [mailto:chaita...@pointcross.com] Sent: 12 March 2013 05:27 To: 'General discussion for Windows Installer XML toolset.' Subject: Re:

Re: [WiX-users] Is using Powershell script as a Wix Custom Action a good idea?

2013-03-12 Thread Rob Mensching
My personal point of view: write custom actions in native code, statically link the CRT and have as few dependencies on the machine as possible. Actually, best option is to have no custom actions. smile/ On Mon, Mar 11, 2013 at 9:57 PM, Hoover, Jacob jacob.hoo...@greenheck.comwrote: Which is

Re: [WiX-users] Is using Powershell script as a Wix Custom Action a good idea?

2013-03-12 Thread Steven Ogilvie
Classification: Public I agree, however for simple installs, yes having no custom actions is best. But, for installs that require more work, i.e. web sites, databases not using custom actions is not easy... There are a lot of things that WIX can't handle. Steve -Original Message- From:

Re: [WiX-users] Is using Powershell script as a Wix Custom Action a good idea?

2013-03-12 Thread Christopher Painter
CA's can be built to target CLR 2.0 and beyond. The dependency / fragility concerns are overblown. .NET just offers too much to be ignored. For vendor extensions and performance sensitive (UI control event DoActions) then native is worth it. From:

Re: [WiX-users] Managed Bootstrapper - Second Patch does not supersede first Patch

2013-03-12 Thread Tomer Cohen
Got anywhere with this? I have the same problem I don't mind having both patches appear in the add remove - updates side by side, but the second patch doesn't replace the files at all... If I install it without the first patch already installed then that patch works great. Tomer. Thanks.

Re: [WiX-users] Is using Powershell script as a Wix Custom Action a good idea?

2013-03-12 Thread Rob Mensching
Before NETFX 4.0 came out it was not possible to build assemblies that targeted NETFX2.0 and beyond. That means, any packages with old managed custom actions in them that are not updated can fail to install by default on newer operating systems (where NETFX2.0 is not on by default). It is

Re: [WiX-users] Is using Powershell script as a Wix Custom Action a good idea?

2013-03-12 Thread Christopher Painter
Hence why I said native was well suited to vendor extensions. The take a dependency argument goes back a long ways. An example would be the Excel approach vs the VS/DevDiv approach. It would make a good blog provided that you cover the pro's and con's of each approach. FWIW, DTF custom

Re: [WiX-users] How to localize WiX bootstrapper

2013-03-12 Thread Tomas Köhn
Thanks, it worked out, the problem was to create the folder structure where WPF bootstrapper is searching for the resources. I updated the .wsx bundle file. From: Payload SourceFile=$(var.BootstrapperBuildPath)de\Application.resources.dll/ To: Payload Name= de\Application.resources.dll

Re: [WiX-users] Is using Powershell script as a Wix Custom Action a good idea?

2013-03-12 Thread Castro, Edwin G. (Hillsboro)
I have successfully executed PowerShell scripts as CustomActions in MSI packages. If you MUST use PowerShell, then all of the warnings concerning difficulty in debugging apply. You MUST fully understand the context under which the script is executing (user context, filesystem and registry

[WiX-users] TFS 2012 Build failing on HeatDirectory task

2013-03-12 Thread Stones
Hi, I am looking for some help. We have a Continuous Integration Build that is running a Wix project that I have created. It runs fine locally but when you run the build job it keeps failing. The error that I am getting is: Task HeatDirectory Command: C:\Program Files (x86)\WiX Toolset

Re: [WiX-users] Execute a custom action only on uninstall?

2013-03-12 Thread Vern Graner
Steve: Thanks for the reply. I hadn't had a chance to experiment with this till today. I was looking at the two InstallExecuteSequence sections you show below and I guess I'm just not getting what makes the script only execute the customaction only on *UNinstall*, and not on install? Also, is

Re: [WiX-users] Is using Powershell script as a Wix Custom Action a good idea?

2013-03-12 Thread Christopher Painter
Put another way, I think it's more important to fully, and I do mean fully, understand the MSI model including the declarative and transactional aspects. I've seen far too many installers that ignore all this and then do some crap in a .BAT or .VBS file. It's more important to focus on this

[WiX-users] calling a soap service during installation

2013-03-12 Thread Sean Farrow
Hi, I am writing an installation that needs to call a soap web service. I was wondering whether anybody has done this using c++ and therefore has any custom actions. I'm using wix 3.8 for reference. Regards Sean. --

[WiX-users] Burn: hang after Apply Complete on Vista

2013-03-12 Thread Bruce Cran
I have a bundle built using WiX 3.7.1224.0 that installs 2 MSI files. It works perfectly when run from the desktop on Server 2008 (R1) but when run (with /quiet /norestart) from a service which is logged on as Administrator it installs the last package, logs Apply Complete, result: 0x0,

[WiX-users] Using Update Element of the Bundle?

2013-03-12 Thread Wheeler, Blaine (DSHS/DCS)
I want to create a self updating setup.exe with Burn. I hope that using the Update element of the Bundle with Wix 3.7 will work. The Help says this piece wasn't working yet but it looks like you use it for Wix updates. True? Is there a reason you use a feed or was it just convenience? My

Re: [WiX-users] Burn: hang after Apply Complete on Vista

2013-03-12 Thread Rob Mensching
Is the task scheduler enabled and running? If not, try that and see if the problem goes away. On Tue, Mar 12, 2013 at 12:32 PM, Bruce Cran br...@cran.org.uk wrote: I have a bundle built using WiX 3.7.1224.0 that installs 2 MSI files. It works perfectly when run from the desktop on Server 2008

[WiX-users] Showing bootstrapped MSI UI during repair/change/uninstall

2013-03-12 Thread Jacob Baughman
I've been having a lot of trouble getting this to work the way I'd like and I was hoping someone could point me in the right direction. I've got a custom managed BA that is pretty bare bones and chains a .NET prerequisite and my product's MSI. I'm specifying MsiPackage/@DisplayInternalUI=yes

Re: [WiX-users] Burn: hang after Apply Complete on Vista

2013-03-12 Thread Bruce Cran
On 12/03/2013 20:49, Rob Mensching wrote: Is the task scheduler enabled and running? If not, try that and see if the problem goes away. Unfortunately it is already running. I'll do some more debugging to see what's going on. -- Bruce On Tue, Mar 12, 2013 at 12:32 PM, Bruce Cran

Re: [WiX-users] Showing bootstrapped MSI UI during repair/change/uninstall

2013-03-12 Thread Rob Mensching
MSI UI shows basic on uninstall. I thought there was a fix to allow Modify to show Full UI... haven't looked in a long while. On Tue, Mar 12, 2013 at 1:39 PM, Jacob Baughman jbaugh...@atlas-sys.comwrote: I've been having a lot of trouble getting this to work the way I'd like and I was hoping

[WiX-users] Project with merge modules defeating incremental build facility

2013-03-12 Thread Rennie Petersen
This was not a problem in WiX 3.5, but apparently as part of 3.6 support was added to the MSBuild targets for incremental builds by testing the timestamps on all input files to the link task to see if they were newer than the output files. I haven't been able to find any documentation - Bob Arnson

[WiX-users] issue with fragments in the same project

2013-03-12 Thread Sean Farrow
Hi, I'm currently creating an installer. In one file I have my folder structure: Fragment Directory Id=TARGETDIR Name=SourceDir Directory Id=ProgramFilesFolder Directory Id=CONPANYFOLDER Name=SalamanderSoft Directory Id=INSTALLFOLDER Name=Connector

Re: [WiX-users] Managed Bootstrapper - Second Patch does not supersede first Patch

2013-03-12 Thread Brian_Covington
Sorry, no.  We are weeks away from having to release and the plan for now is to not use cumulative patches. From: Tomer Cohen [via Windows Installer XML (WiX) toolset] ml-node+s687559n758426...@n2.nabble.com To: Brian_Covington briancoving...@yahoo.com

Re: [WiX-users] issue with fragments in the same project

2013-03-12 Thread Rob Mensching
Where is the ComponentRef to Salamander.Host.exeFile? On Tue, Mar 12, 2013 at 5:31 PM, Sean Farrow sean.far...@seanfarrow.co.ukwrote: Hi, I'm currently creating an installer. In one file I have my folder structure: Fragment Directory Id=TARGETDIR Name=SourceDir Directory