Re: [WiX-users] SqlExpress Exepackage InstallCommand ConfigurationFile

2014-04-08 Thread Adkins, Christopher
On Tue, Apr 8, 2014 at 2:14 PM, Adkins, Christopher < christopher.adk...@docuware.com> wrote: > How about setting an MSIProperty? > > Persisted="yes"/> > > > > > > Using this method you can also change the path from within

Re: [WiX-users] SqlExpress Exepackage InstallCommand ConfigurationFile

2014-04-08 Thread Adkins, Christopher
How about setting an MSIProperty? Using this method you can also change the path from within your bootstrapper application, if you have one, and the user can also set it when calling the bootstrapper. Hope this helps! Best regards, Chris Adkins -Original Message--

[WiX-users] One chainer to rule them all.

2014-04-08 Thread Adkins, Christopher
Here is the short version of what I am trying to accomplish with Burn. I have a chainer that is responsible for installing up to 12 different products, plus prerequisites. If there is a hotfix available for one of those products, then there will be a new msi for that product and it will be handl

[WiX-users] DetectRelatedMsiPackageEventArgs Constructor

2014-04-08 Thread Adkins, Christopher
Hi everyone, I have looked at the constructor for DetectRelatedMsiPackageEventArgs and I noticed that it requires a Long for the version number. If I try to create a new instance of DetectRelatedMsiPackageEventArgs in order to change the Operation I cannot do this because args.Version is not va

Re: [WiX-users] Debugging Managed Bootstrapper Application

2014-03-25 Thread Adkins, Christopher
That is exactly how I do it. I put a sleep at the beginning to give me a chance to attach it to the process and then I can proceed with debugging. Chris Adkins DocuWare GmbH -Original Message- From: Daniel Madill [mailto:dan.mad...@quanser.com] Sent: Dienstag, 25. März 2014 14:20 To: Ge

[WiX-users] Burn UI Intranet problem

2013-08-08 Thread Adkins, Christopher
Hi everybody! I was wondering if anyone has any experience with issues using a Custom BA on a closed Intranet. When I do this in tests I get the following at the end of my log: [1704:11DC][2013-08-06T15:29:16]: Error 0x800b010a: Failed authenticode verification of payload: C:\ProgramData\Packa

Re: [WiX-users] Burn log location

2013-06-17 Thread Adkins, Christopher
Cheers Jakob On Mon, Jun 17, 2013 at 2:13 PM, Adkins, Christopher < christopher.adk...@docuware.com> wrote: > Hi everyone, > > I am sure that I am missing something, but I can't seem to figure out > how to configure where the installation logs land. The installation >

[WiX-users] Burn log location

2013-06-17 Thread Adkins, Christopher
Hi everyone, I am sure that I am missing something, but I can't seem to figure out how to configure where the installation logs land. The installation that I am putting together is going to contain 30+ MSIs and the support technicians that I work with have requested that all the logs are in one

Re: [WiX-users] Uninstall badly formed bundle

2013-01-09 Thread Adkins, Christopher
enter to the command I get "No product/patch data was found". I suspect it's because I want to remove five bootstrappers, and not msi files. There is one hidden msi file that all five installations are dependent upon, but this one cannot be uninstalled as well. Need some stronger m

Re: [WiX-users] Uninstall badly formed bundle

2013-01-09 Thread Adkins, Christopher
Try using MSIZap to get rid of the entries. The files will all be left on the file system, but it should help to start cleaning up your system. All you need is the product code from each instance of the installed product and you are good to go. msizap.exe TW! {PLACE-GUID-HERE} I should also me

Re: [WiX-users] Burn custom managed UI not starting

2012-08-23 Thread Adkins, Christopher
. Make sure you have your file references in the bundle correct. You can also use Sysinternals ProcMon to see where the bundle tries to locate your bootstrapper. Kind regards, Henning > -Original Message----- > From: Adkins, Christopher [mailto:christopher.adk...@docuware.com] > Sent

Re: [WiX-users] Burn custom managed UI not starting

2012-08-23 Thread Adkins, Christopher
ation, any delay in its receipt or that the mail is virus-free. -Original Message- From: Adkins, Christopher [mailto:christopher.adk...@docuware.com] Sent: Thursday, August 23, 2012 12:11 PM To: General discussion for Windows Installer XML toolset. (wix-users@lists.sourceforge.net) Su

[WiX-users] Burn custom managed UI not starting

2012-08-23 Thread Adkins, Christopher
Hi everyone, I am trying to get a custom burn UI working, but I can't even get it to start. I have looked at the WiXUX project as an example, but I am stuck on what I am doing wrong. The log tells me: [0428:0BC8][2012-08-23T12:04:17]: Burn v3.6.2928.0, Windows v6.1 (Build 7600: Service Pack 0)

Re: [WiX-users] Should you install 32-bit and 64-bit versions os the same application?

2012-06-14 Thread Adkins Christopher
This option is, theoretically, possible and readily available to you. This depends on the needs of your program though. Doing this just so you can have it is not the right reason, but if there is an actual need for it the go ahead. Some things that you will have to watch out for, however, would

Re: [WiX-users] Windows Installer 3.1 or 4.5 for XP?

2012-06-12 Thread Adkins Christopher
Hi Don, The main feature of WI 4.5 that I found to be the most useful was Transactions, but this is only really an issue if you have a multi package installation. The best option that I am aware of would be to give the customer the chance to take care of the deficiency beforehand. Document it s

Re: [WiX-users] LaunchFile is a standard custom action?

2011-05-23 Thread Adkins Christopher
Hi William, The ID in that custom action is just a name to identify it. In this case LaunchFile was used to make it very clear what it was doing. You could name it whatever you want to make it clearer for yourself. To further answer your question it is not a predefined custom action, but rathe

[WiX-users] Migration from 3.0 to 3.5

2011-05-13 Thread Adkins Christopher
Hi all, I am working on switching my product over to WiX 3.5 while at the same time changing over to Visual Studio 2010 and .NET 4.0. As part of the migration I have been looking over new features and have come upon a question that I haven't found the question to. In WiX 3.5 I have seen that