Hi,
I already posted this question in the msbuild forum, but maybe there are WIX
developers still using the msbuild-GenerateBootstrapper approach who know an
answer to this...
I'm using the GenerateBootstrapper-task to create a bootstrapper for a WIX
setup project. Among other things this bootstr
Hello,
I have an installer that bundles multiple MSIs together, and the executable has
become very large (mostly due to the size of the Burn engine, I believe). Due
to its size, the app opens slowly and sometimes tricks people into thinking it
is 'hanging/frozen.' Is there any way to offload th
Defect #3191 raised with updated documentation attached.
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: 14 January 2013 23:10
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Urgent: How to check for .net framework 4.5 in the
Greetings,
I just wanted to share something interesting that I recently found. If one
wishes to add a Condition element to a Control that is of a type
RadioButtonGroup that Condition Element needs to be at the bottom or the last
child element of the Control. If it is placed before the RadioButt
This MSKB article discusses how to do it:
http://support.microsoft.com/kb/259697
> -Original Message-
> From: Shane Corbin [mailto:shane_cor...@selinc.com]
> Sent: Friday, January 11, 2013 22:49
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] DIFxApp and upgrades
>
> I'm
The msi referenced in your download url has the ProductVersion= 14.0.4763.1150
- I think this is what you need.
Neil
-Original Message-
From: Karl Werner [mailto:karl.wer...@gmail.com]
Sent: 16 January 2013 16:17
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Remote Payloa
NOTE: The MsiPackage I posted contains my dummy version number. This was
originally not included to generate the first error. It was added to
generate the second error. Sorry for any confusion.
On Wed, Jan 16, 2013 at 9:48 AM, Karl Werner wrote:
> I'm trying to set up a remote payload for the
Very cool, thanks! Here's what I think I've settled on (including the
Office 2010 product codes in case anyone stumbles across this conversation
later):
These will contain the location of the installed components, but I use them
as Install Conditions in the chain like so:
Than
I'm trying to set up a remote payload for the Office 2010 PIAs.
Heat generated this:
Which I took and made this:
http://go.microsoft.com/fwlink/?LinkId=187780"; DisplayInternalUI="yes"
Permanent="yes" Visible="yes"
InstallCondition="Office14Installed AND NOT
Office14PIAInstal
You should be fine if you wrote your code in a typical way. A
patch is basically a repair operation. As long as the Components with the
updated executables also contain the NativeImage elements then the Windows
Installer will know to update the Component and the NativeImage custom
action will know
My favorite way to debug this is:
1. Install the MSI with full UI.
2. When the "You do not have privileges" error pops up when installing the
service, leave it there.
3. Use sc.exe to dig around/create the service/etc using the files that are
installed.
4. Usually I find that a dll is not installe
I suspect keyfiles are your problem also but I'd also point out that you
are using Microsoft.Deployment.WindowsInstaller.Linq not
Microsoft.Deployment.WindowsInstaller. Those classes, according to the SDK
doco, are not fully tested. Try using Installer.OpenProduct and
product.Components[] t
Phil,
Thank you for the quick response I have pasted a more thorough example
of the components below. Basically what I think I need to do is make sure every
is in their own component with a keypath?
Hello,
I have successfully built my first WiX installer and it's going well for the
most part. I only have one issue now in implementing my launch dialog.
However, every time I compile, I get the error:
Error 9 ICE82: This action FinishDialog has duplicate
sequence number -1
I guess the windows installer service has no rights on the domain as it is run
as a local only service (local system account).
I think you need some form of impersonification to use a domain user or another
option might be to run the windows installer service on an account which has
domain acces
No problem.
The serviceaccount property should be in the format
domain\user
Check the value in the property dump at the end of the verbose log. If the
format is wrong, it will issue that error.
If you set start="demand", the service won't run at install time.
-Original Message-
From: Ch
Hi Perter, yes I had to remove some sensitive information,
If you install the service as local system and network service it works like
peanut butter and jelly on toast :) just when using any existing Windows
account it moans.
-Original Message-
From: Peter Shirtcliffe [mailto:pshirtcli
I'm assuming your installer is per-machine so it's not an elevation problem ?
You have "servicename" in your error but "service1" in the code - is that
just you editing before you post ?
Have you tried installing using the default service account (by omitting any
account details) ?
-Original
I did try to install the service without starting it after install, but could
not figure out how the ServiceInstaller's properties should work?
-Original Message-
From: Christoffel le Roux [mailto:christoffe...@tech.flowcentric.com]
Sent: 16 January 2013 01:44 PM
To: General discussion fo
Hi,
Iam installing some prerequest softwares through wix.
It is going well.but,if my client don't want that software he can say cancel
to software.
But what happened if he says cancel to that software entire my insatlation
is rolling back.
To avoid dat I want to keep a "condition" to install th
Hello,
I am creating an installation for a piece of software i have written and
part of the installation process is setting the default search engine to a
custom search engine. I wondered if anyone knew how to do this or might
point me in the right direction.
Thanks in advance
Dave
--
The only (not) usefull thing in the log file is
Error 1923. Service 'ServiceName' (ServiceName) could not be installed. Verify
that you have sufficient privileges to install system services.
MSI (s) (AC:BC) [12:39:28:321]: Product: ProductName -- Error 1923. Service
'ServiceName' (ServiceName)
Result from installing using sc
D:\>sc create TestService binPath= "Service1.exe" type= own start= auto error=
normal obj= * DisplayName= Jannie password= *
[SC] CreateService SUCCESS
-Original Message-
From: Christoffel le Roux [mailto:christoffe...@tech.flowcentric.com]
Sent: 1
Are there any clues in a verbose log ?
-Original Message-
From: Christoffel le Roux [mailto:christoffe...@tech.flowcentric.com]
Sent: 16 January 2013 11:30
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Installing service using domain account
I just ad
I just added a custom installer class to test if the service will install using
InstallUtil, I't doesn't do anything special like custom actions.
-Original Message-
From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com]
Sent: 16 January 2013 01:26 PM
To: General discussion for Windows Inst
What is installutil doing ? The installer won't run any install class code.
-Original Message-
From: Christoffel le Roux [mailto:christoffe...@tech.flowcentric.com]
Sent: 16 January 2013 11:17
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Installing se
Hi Peter, the service installs perfectly using InstallUtil, an sc.exe, I have
no Idea why it's doing what it is.
-Original Message-
From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com]
Sent: 16 January 2013 01:13 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [
It's usually a missing dependency dll. A useful troubleshooting step can be
to take the set of files and use sc.exe and the services control panel to try
and install and configure the service manually on the same machine.
-Original Message-
From: Christoffel le Roux [mailto:christoffe...@t
Hi, I'm trying to install a service using the following WIX fragment and using
an existing domain account as the service account.
After googling allot I have the following.
The serive is marked as non-interactive according to the service's table on MSDN
The domain account is
On 16/01/2013 09:26, Rob Hamflett wrote:
> Doesn't this just bring back DLL Hell? It seems that we have to
> completely abandon using merge modules for runtime deployment. How is a
> user performing a command line installation or repair supposed to know
> whether or not it's safe to use the 'a' o
>"Normally, the higher minor version have compatibility with the lower
one."
So not always, then. "Normally" is a world away from "there's a
specific policy in place to make sure all versions are backwards
compatible".
Doesn't this just bring back DLL Hell? It seems that we have to
complete
31 matches
Mail list logo
