Re: [WiX-users] Custom action "System.IO.DirectoryNotFoundException" on second Installation

2015-02-04 Thread Sarvagya Pant
Hi Phil and Jacob. One approach I could do is create another function in Custom action that will attempt to remove the residual files during uninstall. ie: [CustomAction] public static ActionResult ClearLeftOvers(Session session) { session.Log("Call of ClearLeftOvers");

Re: [WiX-users] Custom action "System.IO.DirectoryNotFoundException" on second Installation

2015-02-04 Thread Phil Wilson
That looks like an immediate custom action, and that's: 1. Something you shouldn't do as an immediate custom action. If you really really need to do that, take heed of Jacob's advice, but make it deferred and add a rollback custom action to undo all that in case the install fails. 2. Immediate cus

[WiX-users] How to show custom error text on SetupCompleteError dialog when a deferred CA fails.

2015-02-04 Thread Kashif Md.
Hi, I have a deferred Custom action that fails in some scenarios. Since this custom action is responsible for installling some licensing libraries for my product hence I cannot continue installation if this CA fails. I want to show a custom error message to the user if this CA has failed the inst

Re: [WiX-users] Allow service start failure

2015-02-04 Thread Nir Bar
You can't ignore a service failure to log-in using the standard actions - See ServiceControl table. Instead you can create a custom action that will start the service (using SC.exe for example) and ignore its exit code. Nir

[WiX-users] WiX MSI or Bundle - calling Windows Explorer with a specified folder

2015-02-04 Thread Tall Tyke
Hi, I posted a question yesterday, which was a bit bizarre and didn't get any responses - so we have changed tack a bit and now want our installer ( either a WiX 3.9 MSI or our bundle ) to run "Windows Explorer" opening up at a folder path with give it - is that possible ? Cheers, Chris. -- V

Re: [WiX-users] Custom action "System.IO.DirectoryNotFoundException" on second Installation

2015-02-04 Thread Hoover, Jacob
Is the file/directory in use when the delete was attempted? Is there a reason you have to delete the file instead of just overwriting it? Have you pondered using a RemoveFile element to explicitly remove the files you are creating in your CA on uninstall? -Original Message- From: Sarv

Re: [WiX-users] [WIX]: Japanese MSI package creation

2015-02-04 Thread Tunney, Stephen
All, Just because you have that header at the top doesn't mean that your file is ENCODED in UTF-8. Open the wxs file in VS and go to File->Advanced Save Options. Ensure that the codepage you want is specified. -Original Message- From: Dileep S [mailto:dileep.sanamp...@gmail.com] Sent:

[WiX-users] Changing the Product Name at instal

2015-02-04 Thread Fyodor Koryazhkin
Hi, You cannot change the Product Name in through the command line. You can use Transform but it is not such dynamic as you want. Using transforms requires all transforms to be created before launcjing the installation. On Tue, Feb 3, 2015 at 11:43 PM, wrote: > Send WiX-users mailing list submis

[WiX-users] Allow service start failure

2015-02-04 Thread Eduard Ranghiuc
Hi everyone, I'm keeping the "Log On As" info on upgrade for the service I'm installing. NOT WIX_UPGRADE_DETECTED NOT UPGRADINGPRODUCTCODE However, the upgrade fails if the user/password are incorrect. How can I allow my service to fail to start? Thank you! -- Best regards, Eduard R

Re: [WiX-users] [WIX]: Japanese MSI package creation

2015-02-04 Thread Valdimar
dileep s wrote > I was not able to see this in my local system. File name appears like > ニ探ニ停€愴致ニ停€ケ_窶凖ィナ耽06.SFC. > How did you convert this filename before adding it to the script? > Do we need to specify any character code to read this? I changed the encoding settings of the browser to be able t

Re: [WiX-users] [WIX]: Japanese MSI package creation

2015-02-04 Thread Nir Bar
Actually the error is not about the file names. It is about the string elements - some of the characters are not in the code-page you stated. You should go over the strings you provided and make sure that all the characters you put there belong to the code-page you specified in the WixLocalization