Sorry for reviving a fairly old thread, but I'm working on localizing the
MSIs inside a bundle and the following made me a bit uneasy:
I use a single localized bootstrapper and separate localized msi(s). All of
> my UX GUI is in the mba, except for a few status and error messages in the
> MSI. I
Hi there,
Our WiX installer has the following action:
When our product is upgraded or uninstalled, the service is properly
stopped by the MSI. However, if the product is reinstalled, such as when
re-running the installer with the /qn flag, the product is reinstalled
without the service being sto
h the WIX bootstrapper UI to know for a fact
> that it does the MsiSetExternalRecordUI thing.
> ---
> Phil Wilson
>
>
> On Wed, May 14, 2014 at 11:09 AM, Soren Dreijer
> wrote:
> > Hi Phil,
> >
> > Correct me if I'm wrong, but as far as I'
work
> if you substitute a custom dialog. For better or worse it's what
> people use to report errors from deferred CAs, add them into the MSI
> log etc.
> ---
> Phil Wilson
>
>
> On Mon, May 12, 2014 at 8:57 AM, Soren Dreijer
> wrote:
> > Hey guys,
>
+ (int)MessageBoxButtons.OK,
> new Record { FormatString = "Setup could not back up the
> database: \nException: " + ex.Message });
> }
>
> return ActionResult.Failure;
> }
>
>if (session != null)
>{
> Session.Log(&
Thanks Phill!
I also found this:
http://msdn.microsoft.com/en-us/library/aa371247%28v=vs.85%29.aspx
http://msdn.microsoft.com/en-us/library/aa370573%28v=vs.85%29.aspx
However, I'm still not clear on how I go about handling that error code in
my bootstrapper. For instance, let's say two different
Hi all,
I've Googled and searched the WiX mailing list, but I haven't been able to
figure this one out yet.
One of the biggest problems I've always had with MSIs is that they rarely
return useful error messages. I'm using a custom bootstrapper and I'd like
to display a custom error message if one
ory in %USERS%/AppData/Local/AppName.
> Move the app.config file there til after the upgrade then use a CA, as
> you stated earlier to "merge" the 2 files, alleviating the need for a
> temporary name.
>
> Carter
>
> Quoting Soren Dreijer :
>
> > Carter,
>
ettings that don't
> change in the app.config. Then every major upgrade, have your app
> read the registry values... Takes a little bit of work and research,
> but will save you this headache.
>
> Carter
>
> Quoting Soren Dreijer :
>
> > The app.config is modified af
If
> a user manually modifies the file, then a major upgrade should not remove
> it. If it was modified with XmlFile CA's or the likes, were the original
> user choices persisted in the registry?
> >
> > -Original Message-
> > From: Soren Dreijer [mailto:drei
sisted in the registry?
>
> -Original Message-
> From: Soren Dreijer [mailto:dreijer+l...@echobit.net]
> Sent: Tuesday, March 11, 2014 12:12 PM
> To: General discussion about the WiX toolset.
> Subject: Re: [WiX-users] Generating a unique file name
>
> Hey Jacob,
>
> It'
; Taking a step back, I would have to ask why you are needing to make a copy
> of a file with a random name. If it's a user modified file, then an upgrade
> shouldn't touch it.
>
> -----Original Message-
> From: Soren Dreijer [mailto:dreijer+l...@echobit.net]
> Sent: Mond
lobal property, generate the name in a custom action,
> there you can use datetime.Tostring("HHmmss ") to format it any way you
> like, then put the value back into the session object where you can now use
> it any way you like.
>
> -----Original Message-
> From: Sore
wrote:
> What about using [Time]?
> ___
> FireGiant | Dedicated support for the WiX toolset |
> http://www.firegiant.com/
>
> -Original Message-
> From: Soren Dreijer [mailto:dreijer+l...@echobit.net]
> Sent: M
e attribute may not be
> specified. Also, if this value is a long file name, the
> DestinationShortName attribute may be omitted to allow WiX to attempt
> to generate a unique short file name. However, if this name collides
> with another file or you wish to manually specify the
10, 2014 at 11:28 AM, Carter Young wrote:
> I believe the SourceName Attribute is what you're looking for.
>
> http://wixtoolset.org/documentation/manual/v3/xsd/wix/copyfile.html
>
> Carter
>
> Quoting Soren Dreijer :
>
> > Hi there,
> >
> > I w
Hi there,
I want to make a backup of a file during a major upgrade. The CopyFIle
element is pretty much what I need, but I'd like to generate the
destination file name on the fly to prevent name clashing.
Is there a way to do this with WiX that doesn't require me to use a custom
action?
Cheers,
Thanks Phill.
You're right; WFP drivers are non-PNP drivers. I did try to use the legacy
flag, but then the installer was complaining that the .sys file was missing
even though it was copied properly to the target folder. I'll give it
another try. Otherwise, I'll have to make a custom app that ins
I'm attempting to install a WFP (Windows Filtering Platform) callout driver
via WiX. All the driver's .inf file does during installation is to copy the
.sys file to the Drivers folder and that's that.
The driver isn't a "typical" driver in the sense that its .inf file doesn't
have a SourceDisksN
(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
Hi,
We’ve built a custom DLL for our WiX-powered installer because our product
has a pretty complicated install sequence. Our custom DLL runs as a deferred
custom action since it modifies system files, etc.. The problem we’re facing
is that since our DLL does the heavy lifting of registering our
21 matches
Mail list logo
