Re: [WiX-users] util:filesearch only working with versioned

2015-02-12 Thread Tobias Erichsen
Hi again, no - definitely no typo. I have taken the path from the logfile and copied it into the explorer and it opened the test-file without problem... Tobias Von: Nir Bar [nir@panel-sw.co.il] Gesendet: Mittwoch, 11. Februar 2015 17:17 Bis:

[WiX-users] util:filesearch only working with versioned files?

2015-02-11 Thread Tobias Erichsen
Hi everyone, I currently have a small problem with some burn-topic. I want to see if a specific (text-)file exists and depending on the existance disable the options-button... util:FileSearch Id=ShowFrontendFile Path=[CommonAppDataFolder]TE-SYSTEMS\anynode frontend\showfrontend.xzconfig

[WiX-users] ICE60 during install of ttf file to private folder

2014-12-12 Thread Tobias Erichsen
Hi everyone, during installation, I just want to copy some true-type fonts into an application local directory for its own internal use. Unfortunately I always get an ICE60 warning: XXX is not a Font, and its version is not a companion file reference... Could anyone tell me if I can get rid

Re: [WiX-users] Disable logging in Burn

2014-10-27 Thread Tobias Erichsen
-users] Disable logging in Burn That sounds like a bug in Burn. _ Short replies here. Complete answers over there: http://www.firegiant.com/ -Original Message- From: Tobias Erichsen [mailto:i...@tobias-erichsen.de] Sent: Friday

Re: [WiX-users] Disable logging in Burn

2014-10-27 Thread Tobias Erichsen
. _ Short replies here. Complete answers over there: http://www.firegiant.com/ -Original Message- From: Tobias Erichsen [mailto:i...@tobias-erichsen.de] Sent: Friday, October 24, 2014 6:54 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Disable logging in Burn Hi

[WiX-users] Disable logging in Burn

2014-10-24 Thread Tobias Erichsen
Hi everyone, after Rob has been so kind to point me to the log element to disable burn-logging, I have added Log Disable=yes / and now the log of burn in the %temp% directory vanishes. This created some unwanted side-effect though: In the local directory where my bootstrapper was located, for

Re: [WiX-users] Burn - Checkbox on Modify Page

2014-10-22 Thread Tobias Erichsen
Hi everyone, has there been a feature-request for this topic yet? It seems that one can still not search the issue-database... Best regards, Tobias Von: Neil Sleightholm [n...@x2systems.com] Gesendet: Dienstag, 22. April 2014 08:11 Bis: General

Re: [WiX-users] Burn does not show close application warning during uninstall

2014-03-09 Thread Tobias Erichsen
Searching is supported, the text box is just missing. It'll show up eventually. Ah - that would be great ;-) -- Subversion Kills Productivity. Get off Subversion Make the Move to Perforce. With Perforce, you get

Re: [WiX-users] Burn does not show close application warning during uninstall

2014-03-07 Thread Tobias Erichsen
: Tobias Erichsen [mailto:i...@tobias-erichsen.de] Sent: Friday, March 07, 2014 1:41 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Burn does not show close application warning during uninstall Hi everyone, I got a small problem during uninstall of my application. If I install/uninstall

Re: [WiX-users] Burn LaunchTarget - possible to specify HTTP-URL?

2014-03-06 Thread Tobias Erichsen
); sw.WriteLine(Set wshShell = Nothing); } } Then in the bootstrapper I added: LaunchTarget=$(env.SystemDrive)\inetpub\wwwroot\addyourwebsitepath\LaunchWebSite.vbs -Original Message- From: Tobias Erichsen [mailto:i...@tobias-erichsen.de] Sent: March-05-14

[WiX-users] Burn does not show close application warning during uninstall

2014-03-06 Thread Tobias Erichsen
Hi everyone, I got a small problem during uninstall of my application. If I install/uninstall just with an MSI on W7 for example, I get the dialog that some applications must be closed before continuing install. When I use that MSI within my burn-bootstrapper, this dialog does not appear. Do I

[WiX-users] Burn LaunchTarget - possible to specify HTTP-URL?

2014-03-05 Thread Tobias Erichsen
Hi, I was wondering if I could specify an HTTP-URI as LaunchTarget in my burn boostrapper, as the user-interface for an application of mine is a local webserver... Best regards, Tobias -- Subversion Kills Productivity.

Re: [WiX-users] Little major/minor-update problem with burn / msi

2013-12-01 Thread Tobias Erichsen
msiOld: productIdA, upgradeIdA msiNew: productIdB (*), upgradeIdB msiBlock: productIdA, upgradeIdC The problem is that msiOld does not have any guard and that is why I want to install some kind of (invisible) blocking-installer. I cannot change the msiOld (because it is out in the open), but I

[WiX-users] Little major/minor-update problem with burn / msi

2013-11-30 Thread Tobias Erichsen
Hi everyone, I have a little problem with my burn / msi installer: My old MSI-installer has been replaced by a burn-package that includes multiple MSIs (as one of the components that was a merge-module the old MSI is now in use by 3rd parties as well). Unfortunately - due to my lack of

Re: [WiX-users] Burn installation with Aladdin eToken driver (msi) opens second burn's window.

2013-11-06 Thread Tobias Erichsen
Hi Blair, thanks for the input. I let the whole thing run while also using Process Monitor to log all processes being created and you were right: The last rtpMIDISetup.exe process (showing the erroneous dialog) is instantiated from runonce.exe, which itself is instantiated from MsiExec.exe...

Re: [WiX-users] Burn installation with Aladdin eToken driver (msi) opens second burn's window.

2013-11-06 Thread Tobias Erichsen
Hi, thanks for that input as well. My driver's inf-file does not contain any RunOnce entries. So I assume that burn is doing that somewhere... Could Rob or Bob possibly chime in on this? I'd gladly do some more digging/debugging, but as I still do not fully understand the overall

Re: [WiX-users] Burn installation with Aladdin eToken driver (msi) opens second burn's window.

2013-11-05 Thread Tobias Erichsen
Hi again everyone, I have tried to do a WinDbg session tonight to single-step through the burn-engine to find out where the problem is. But I must confess that I lost track somewhere in the creation of sub-processes and communication via pipes :-( One peculiar thing came up though. I had

Re: [WiX-users] Burn installation with Aladdin eToken driver (msi) opens second burn's window.

2013-10-30 Thread Tobias Erichsen
Hi everyone, I was wondering if I should open a ticket for this issue if noone has done that so far... Best regards, Tobias Von: Tobias Erichsen [i...@tobias-erichsen.de] Gesendet: Montag, 14. Oktober 2013 17:11 Bis: General discussion for Windows

Re: [WiX-users] Burn installation with Aladdin eToken driver (msi) opens second burn's window.

2013-10-14 Thread Tobias Erichsen
Hi again, I have prepared some logs of the exact same behaviour coming up in my installer on XP: http://www.tobias-erichsen.de/wp-content/uploads/2013/10/burn_xp_double_startup_logs.zip I'm pretty sure it has to do with my custom-action (which is implemented in a dll, but I have also tried

Re: [WiX-users] Burn installation with Aladdin eToken driver (msi) opens second burn's window.

2013-10-13 Thread Tobias Erichsen
Hi everyone, I do have the same problem with my burn-package which first installs an MSI with a driver (using custom-action DLL) and then the application MSI. This only happens on Windows XP, not on Windows 7 or 8. If I replace the driver-install CA in the first MSI by a special diagnosis

[WiX-users] Documentation on website...

2013-09-13 Thread Tobias Erichsen
Hi everyone, I just noticed that the burn-documentation on the website already includes many references to features that are only available with the 3.8 branch. Perhaps I have overlooked a hint clarifying that, but this might be a bit misleading if people try to use that with the released 3.7

[WiX-users] WIX 3.8 improvement suggestions...

2013-09-13 Thread Tobias Erichsen
Hi everyone, I would like to propose a couple of improvements for WIX 3.8: WIX-specific stuff: While developing a type 1 custom-action in standard C, I noticed that the include files wcautil.h and dutil.h had some definitions that prevented me from creating a dll using just C instead of C++:

[WiX-users] Usage of Merge Module for multiple projects (updates etc.)

2010-11-12 Thread Tobias Erichsen
Hi everyone, I have put a device-driver installation into a merge module to be used in several MSI-installers for multiple applications using that driver. The driver is always backwards-compatible (as is the installation), but a newer application might be depending on the feature of the newer

Re: [WiX-users] Usage of Merge Module for multiple projects(updates etc.)

2010-11-12 Thread Tobias Erichsen
tip, know a secret or read a really good thread that deserves attention? E-Mail Me - Original Message From: Tobias Erichsen t.erich...@gmx.de To: wix-users@lists.sourceforge.net Sent: Fri, November 12, 2010 5:55:28 AM Subject: [WiX-users] Usage of Merge Module for multiple

Re: [WiX-users] Usage of Merge Module for multiple projects(updatesetc.)

2010-11-12 Thread Tobias Erichsen
If Product A has files with an lessor version number then Product B  then Product B's higher versioned numbers will remain installed.   Thanks a lot for that information - I still have one problem: I have custom actions for the actual driver install / uninstall. I have to differentiate

Re: [WiX-users] Usage of Merge Module for multiple projects (updates etc.)

2010-11-12 Thread Tobias Erichsen
Hi Christopher It's hard for me to give an exact answer without being there and getting really close to the problem.  That said, I would suggest looking at the Component states ($comp=x and ?comp=x )  to figure out if a component is being installed for the first time, reinstalled