Hi Gabriel!
Unfortunately your link
http://blogs.technet.com/b/alexshev/archive/2008/02/21/from-msi-to-w
ix-part-5-custom-actions.aspx has not opened, but the message is clear.
Thanks!
--
View this message in context:
I change my mind.
Hardcored oemsetup.inf in global wxs with difxapp:driver.
Then, heat harvest driver's file and exclude oemsetup.inf.
Obvious.
Le %:Date:, Gabriel Ivanes [1]g...@fastmail.net a écrit:
Hi there,
I want to automat heat with difxapp. I use heat this way :
heat
Hi,
i'm not sure if i'm posting this at the right place.
I'm actually working on the automation of setup files by building wix project
using a tfs server. The thing is I don't want to perform a full install of
Visual Studio on the build server to build my .wixproj files. I didn't find
anywhere
You can build wixproj files without installing VS, just install WiX (and
.NET).
Neil
Hi,
i'm not sure if i'm posting this at the right place.
I'm actually working on the automation of setup files by building wix
project using a tfs server. The thing is I don't want to perform a full
install of
This topic in the manual may be helpful as well:
http://wix.sourceforge.net/manual-wix3/daily_builds.htm
On Wed, Mar 27, 2013 at 6:28 AM, Neil Sleightholm n...@x2systems.comwrote:
You can build wixproj files without installing VS, just install WiX (and
.NET).
Neil
Hi,
i'm not sure if
Hi all,
I am wondering if anyone has added a new page to the bootstrapper?
What I want to do is have the Welcome page (my welcome page has two radio
buttons to select the install they want to launch), click Next, which goes
to a 2nd page that describes what pre-requisites will be installed if
It's not a problem to install wix on our build server, but when trying to
generate the msi files an error came out about a missing reference to an
assembly whose name makes me think it is related to Visual studio. The assembly
is VSLangProj.dll.I can find it on VS install directory when
What command did you run that caused the error? Can you share out all the
error details? That doesn't sound familiar.
On Wed, Mar 27, 2013 at 7:35 AM, C L clemobil_l...@hotmail.com wrote:
It's not a problem to install wix on our build server, but when trying to
generate the msi files an error
Unfortunately, wixstdba doesn't support that today.
On Wed, Mar 27, 2013 at 7:23 AM, StevenOgilvie sogil...@msn.com wrote:
Hi all,
I am wondering if anyone has added a new page to the bootstrapper?
What I want to do is have the Welcome page (my welcome page has two radio
buttons to select
C L,
We don't use a build server, but I created a front end to WiX for our
developers on one of our Server 2003 boxes and learned a bit about its
prerequisites that way. Unfortunately I don't remember what prereqs per se were
needed (I think SP1 for .NET 3.5 was one odd one, and WIC - but this
Once you have candle and light running there isn't anything else necessary
on the build side.
On Wed, Mar 27, 2013 at 7:45 AM, keith.doug...@statcan.gc.ca wrote:
C L,
We don't use a build server, but I created a front end to WiX for our
developers on one of our Server 2003 boxes and learned
Hi,
Is it possible to skip the license agreement dialog in the WixUI_Minimal
install set? Or do I have to define my own UI set. How would this be done??
Thanks for your help
Graham Allwood
--
Own the Future-Intelreg;
My mistake, i thought my error was coming from a wix component but in fact, the
reference to the VS2010 assembly was defined in the business code i was trying
to build in order to generate the msi. Sorry for wasting your time and thanks
anyway for your reactivity :)
C L
From:
OK, I have got a bit further.
I am using this in my wxs...
UI Id=WixUI_SkipLicenseAgreement
UIRef Id=WixUI_InstallDir /
Publish Dialog=InstallDirDlg Control=Back Event=NewDialog
Value=WelcomeDlg1/Publish
Publish Dialog=WelcomeDlg Control=Next Event=NewDialog
Graham,
Try this:
UI Id=WixUI_InstallDir
TextStyle Id=WixUI_Font_Normal FaceName=Tahoma Size=8 /
TextStyle Id=WixUI_Font_Bigger FaceName=Tahoma Size=12 /
TextStyle Id=WixUI_Font_Title FaceName=Tahoma Size=9 Bold=yes /
Property Id=DefaultUIFont Value=WixUI_Font_Normal /
This should help
http://neilsleightholm.blogspot.co.uk/2008/08/customised-uis-for-wix.html.
This is a very common request one day I'll get around to submitting a change to
make it optional.
Neil
-Original Message-
From: Graham Allwood [mailto:gallw...@sdasoftware.net]
Sent: 27 March
Does WIX offer any inbuilt support for activation keys?
If I want a setup to prompt and verify an activation key, ensuring it is not
being reused and so on and so forth - what does WIX offer and what
additional tools/services should I consider?
Thanks
Hugh Moran
President
Morantex
Activation should be done inside your application. Any checks you put into a
MSI can easily be subverted.
-Original Message-
From: Hugh Moran [mailto:hugh.mo...@morantex.com]
Sent: Wednesday, March 27, 2013 5:01 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Activation
+1
On Wed, Mar 27, 2013 at 3:25 PM, Hoover, Jacob
jacob.hoo...@greenheck.comwrote:
Activation should be done inside your application. Any checks you put
into a MSI can easily be subverted.
-Original Message-
From: Hugh Moran [mailto:hugh.mo...@morantex.com]
Sent: Wednesday, March
+1
Also, please be sure to provide an easy offline experience. Those of us
who have worked inside buildings that are black holes know how damn
painful this is. (I'm looking at you InstallShield!)
From: Rob Mensching r...@robmensching.com
Sent:
When I use this command it uninstalls the whole app:
msiexec /package my.msi /uninstall my.msp
This also does the same thing:
msiexec /package my.msi MSIPATCHREMOVE=my.msp
but this just uninstalls the patch:
msiexec /package my.msi /uninstall my.msp /qb
Why might a quiet execution not uninstall
And how do you add a condition to RemoveExistingProducts?
-
warm regards
Rob Goodridge
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Running-Patch-Uninstall-from-command-line-uninstalls-whole-app-tp7584691p7584692.html
Sent from the
22 matches
Mail list logo
