Thanks Tomasz. I didn't mean to imply that Sharp Setup was unstable and
when I look back at my previous comment I see that there are a few things I
should have added. Specifically, I understand that some add-ins can cause
issues in other add-ins - in fact the product I'm working on is an add-in
f
On Wednesday 06 April 2011 14:39:14 Matt Siebert wrote:
> Thanks Pally, I did look at Sharp Setup earlier today. From memory it
> didn't use DTF (but maybe I'm wrong). I'm at home now and have just
> installed Sharp Setup here but it keeps crashing VS when it generates the
> solution.
>
Please h
Thanks Pally, I did look at Sharp Setup earlier today. From memory it
didn't use DTF (but maybe I'm wrong). I'm at home now and have just
installed Sharp Setup here but it keeps crashing VS when it generates the
solution.
My current plan is to use Burn from WiX 3.6 to chain .NET and then my
exte
Take a look at SharpSetup -> http://sharpsetup.eu/ . It may help point you in
the right direction.
Palbinder Sandher
Software Deployment Engineer
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the **
Integrated Environmental Solutions
Thanks, MsiSetExternalUIRecord is exactly what I needed.
-Andy
-Original Message-
From: Wilson, Phil [mailto:phil.wil...@invensys.com]
Sent: Wednesday, August 11, 2010 1:45 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] External UI Handling
I have only a couple of observations:
1. Using MsiSetExternalUIRecord works better because you get a number of
records that you can inspect rather than trying to decode message formats. Each
record contains process, file name I think etc. If you actually want a message
then MsiFormatRecord() w
I'm very pleased to see the progress.
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: Friday, June 11, 2010 2:07 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] External UI like MS Office 2007
Well, there's don
Thursday, June 10, 2010 7:42 AM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] External UI like MS Office 2007
>
> Nope. Until Burn is done you'll need to write your own to do that (I
> don't know if Burn will support that sort o
neral discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] External UI like MS Office 2007
Nope. Until Burn is done you'll need to write your own to do that (I
don't know if Burn will support that sort of scenario when it's
finished, just speculating since it's still in
age-
From: Sagar [mailto:sagarkavitak...@gmail.com]
Sent: 10 June 2010 15:29
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] External UI like MS Office 2007
Thanks Pally for suggestion.
I tried with dotNetInstaller, it is only helping me select/deselect and
launch my actual
Thanks Pally for suggestion.
I tried with dotNetInstaller, it is only helping me select/deselect and
launch my actual MSIs in proper sequence.
What i want is something like an UI which will ask user for which MSIs to
run and then launch the resective MSIs in background and show only the
progres
You're wrong about dotnetinstaller. You can chain together any
executables, MSI's, MSP's & MSU's using it. Doesn't need to specifically
be pre-requisites.
If you want an external UI and don't want to use dotnetinstaller or
something else already written, write your own. Good place to start
would b
x27;s possible to take an external UI a long way, so it's going
to be about how much you want to put into it!
Phil Wilson
-Original Message-
From: Christopher Painter [mailto:chr...@deploymentengineering.com]
Sent: Friday, January 29, 2010 1:42 PM
To: General discussion for Wind
wrote:
> From: Wilson, Phil
> Subject: RE: [WiX-users] External UI
> To: "chr...@deploymentengineering.com" ,
> "General discussion for Windows Installer XML toolset."
>
> Date: Friday, January 29, 2010, 11:31 AM
> Those actions are duplicated in the
&g
I just fired up my old project and it looks like it is working (of course I'm
not sure if this is the best way way of doing it). Here's a snippet of how I
did it:
Installer.SetInternalUI(InstallUIOptions.Silent);
session =
Installer.OpenPackage(Path.Combine(Environment.Cu
sey
> Subject: Re: [WiX-users] External UI
> To: wix-users@lists.sourceforge.net
> Date: Friday, January 29, 2010, 11:53 AM
>
> Awhile ago I started playing around with external ui and
> found that if the
> MSI doesn't actually have an appsearch table then I got the
> same e
Awhile ago I started playing around with external ui and found that if the
MSI doesn't actually have an appsearch table then I got the same exact
error. Try opening an MSI that you know for a fact has a search and see if
that works. Also, if you end up developing a good external ui it would be
gre
Those actions are duplicated in the Execute sequence anyway, but I'm sure you
know that so I must be missing something. What are you trying to do?
Phil Wilson
-Original Message-
From: Christopher Painter [mailto:chr...@deploymentengineering.com]
Sent: Thursday, January 28, 2010 7:57 P
Dnia czwartek 11 czerwiec 2009 o 18:45:40 Wilson, Phil napisał(a):
> The short answer is that you call MsiInstallProduct and when it returns
> you're finished. Does that mean you're not doing this?
>
I'm using MsiDoAction and I had an impression that it returns immediately and
is doing installatio
ussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] External UI and end of installation
Dnia czwartek 11 czerwiec 2009 o 07:19:37 Rob Mensching napisał(a):
> Rob Mensching wrote:
> > Same way. The MSI SDK has an example with a full external UI handler.
> > Might chec
Dnia czwartek 11 czerwiec 2009 o 07:19:37 Rob Mensching napisał(a):
> Rob Mensching wrote:
> > Same way. The MSI SDK has an example with a full external UI handler.
> > Might check that out.
> >
Yes, I've seen it. Even copied it adapting from C to C#. But it doesn't seem
to work as I expect it to
And I keep forgetting that the burn code is available. That's a full
external UI handler (and more) you can see in the WiX v3.5 code base.
Rob Mensching wrote:
> Same way. The MSI SDK has an example with a full external UI handler.
> Might check that out.
>
> Tomasz Grobelny wrote:
>
>> I inst
Same way. The MSI SDK has an example with a full external UI handler.
Might check that out.
Tomasz Grobelny wrote:
> I install external UI handler through MsiSetExternalUI. I get messages
> concerning progress just fine. But how do I get information about when the
> installation is finished?
> --
23 matches
Mail list logo
