There isn't really and documentation on this I figured it out from the code so
it is possible my observations are wrong.
1. Yes.
2. The Name property of the control will be set as a variable of the same name
e.g.:
Checkbox titile
Will set the variable Check1. The options page only support te
Can you be more specific about what new NETFX technology you are using?
On Mon, Dec 17, 2012 at 11:57 PM, Thomas Tomiczek wrote:
> ...for .NET 4.5. Anyone has a more detailed walkthrough?
>
> I am trying to figure out the nw tracingmechanism for a windows service we
> distribute to various comp
The ComponentGuidGenerationSeed essentially allows you to treat
the Directory (and it's parents) as a well known folder. You are
responsbile for ensuring that the seed changes when the Directory's path
changes. Otherwise, you can start having your Component GUIDs overlap (or
not overlap) incorrectl
Yes. You can Condition the Publish actions to control the MSI UI wizard
flow.
On Wed, Dec 19, 2012 at 6:06 PM, Naim Kingston wrote:
> We have an installer that is going to have 2 main features, but one of
> them will be mainly for developers, so I'm disabling it by default by
> setting the inst
Hi,
I built a CustomAction.dll via the following command and then built it into the
installer.
cl.exe /LD /I PATH_TO_WIX_SDK_INC customAction.cpp /link AdvAPI32.Lib
Version.Lib User32.Lib Msi.Lib wcautil_2008.lib dutil_2008.lib
while, when running the installer, the error dialog poped up
*So if I understand this ...
1/ I have VS 2008 Standard Edition
2/ Wix 3 & Wix 2 versions have different issues with tools and WDK
DifxApp libraries ...
3/ Install Wix 3
4/ From command prompt:
>light -out MyMsi.msi Product.wixobj -ext WixDifxAppExtension
DIFxApp.wixlib
Windows Installer
I've spent the last hour or so looking around for documentation on how
to specify additional UI elements in the option screen of the standard
bootstrapper. I can't really find any documentation on how to do this,
although I see some examples of this being done in Neil's extended BA
with a (somewha
I really need help on this one... I am at a loss why it is taking two click
:(
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Takes-two-clicks-on-Next-button-to-move-forward-on-Custom-Dialog-tp7582481p7582515.html
Sent from the wix-users mailing l
Sorry used to InstallShield and other Front ends to MSI handling upgrades..
I like the MajorUpgrade one line of code instead of a dozen...
Thanks Neil
STeve
-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com]
Sent: December-20-12 5:13 PM
To: General discussion for Win
Not sure what you mean by extra code, this is what an upgrade looks like. Using
afterInstallValidate will uninstall and then install, using afterInstallExecute
will replace files (not a good explanation but see here for a real description
http://www.joyofsetup.com/2008/12/30/paying-for-upgrades/
I am not sure why you would need this, it is not something I have needed.
-Original Message-
From: Steven Ogilvie [mailto:steven.ogil...@titus.com]
Sent: 20 December 2012 21:39
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Upgrades NOT working on a new
Cool it worked... I don't like the fact that you need to do "extra" code to
make it look like an upgrade, it looks like a regular install except during the
progress it is uninstalling the previous version then installing the new one...
I did what you suggested down below :) less code for sure :)
What about the
CA: Setting REINSTALLMODE to
amus...
Is that required?
Steve
-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com]
Sent: December-20-12 4:08 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Upgrades N
Correction - use it will be
simpler.
-Original Message-
From: Neil Sleightholm
Sent: 20 December 2012 21:06
To: General discussion for Windows Installer XML toolset.
Subject: RE: [WiX-users] Upgrades NOT working on a new install
Use
- Product/@Id="*"
- Remove the Id from Package c
Use
- Product/@Id="*"
- Remove the Id from Package completely
- I would revert to the MajorUpgrade element and delete all the Upgrade
elements and RemoveExistingProducts, FindRelatedProducts and
So that would give something like this:
That authoring should be simpler to debug.
An upgrade would look like a fresh install unless you've specifically
authored UI to handle upgrades. How many entries for your application
are there in the Programs and Features panel? If there's 2, then you
know you have a problem.
On 20 December 2012 20:30, Steven Ogilvie wrote:
> No I only c
No I only change the ProductVersion to a higher number (minor.build) and that
was it
-Original Message-
From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com]
Sent: December-20-12 3:27 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Upgr
What do you mean by "When I run the second it's like the first one was not
installed, it was like running a fresh install"? Does the verbose log tell you
whether 4.0.1.25 was detected and uninstalled? I guess I should also ask the
obvious question, did you change UpgradeCode?
Edwin G. Castro
So
Okay I changed the ProductCode to be "*" as well as the Package Id="*"
First MSI had a version number of 4.0.1.25 second MSI has a version number of
4.1.2.55
When I run the second it's like the first one was not installed, it was like
running a fresh install... the newer MSI has a different vers
You need to change ProductCode *and* ProductVersion for a major upgrade to work
as you expect. When you change ProductVersion and leave ProductCode the same
you have a minor upgrade which requires a different style of install (I'm not
expert on installing minor upgrades). The reason it was sugge
Okay,
I now have:
Where: in an include file I include in
my product.wxs
NOT NEWERVERSIONDETECTED
I create one msi with productversion of 4.0.1.25 install it, then change
productversion to 4.0.2.30 and run it and I get the same err
You seem to have the MajorUpgrade element and also the Upgrade element,
MajorUpgrade replaces the need for manually authoring the upgrade table. Also,
I wouldn't hard code Product/@Id just use "*" and have WiX generate it for you,
likewise Package/@Id isn't required just let WiX do it.
Neil
--
Hi all,
I have implemented upgrades by doing the following (I have an include file
that has the product/package properties which I define and include the
include file :)...
then:
where I have the following defined:
and have a productcode and upgradecode that I don't change...
c
Here is an excellent tutorial on how to add new dialogs in Wix and other nifty
things:
http://wix.tramontana.co.hu/tutorial/user-interface/new-link-in-the-chain
-Original Message-
From: Jimmy Nilsson [mailto:jimmy.nils...@evry.com]
Sent: Thursday, December 20, 2012 14:04
To: wix-users@l
Take a look at this: http://www.rrreese.com/Article/Show/WiX%20SQL
-Original Message-
From: Chaitanya [mailto:chaita...@pointcross.com]
Sent: December-20-12 2:45 AM
To: WiX-users@lists.sourceforge.net
Subject: [WiX-users] Running Sql Files.
Hi,
I want to Run SQL querys through Wix.
I
Set the checkbox properties:
WIXUI_EXITDIALOGOPTIONALCHECKBOX = 1 and NOT
Installed
http://localhost:[WEB_SITE_PORT]/"; />
In your case if you want it launched AFTER uninstall have it:
>WIXUI_EXITDIALOGOPTIONALCHECKBOX = 1 and Installed<
That simple :)
Steve
-Original Message-
F
I had a similar issue recently and in my case it was because the MSI features
were controlled by conditions and these were changing between install and
uninstall so this left the MSI in a partially installed state.
Neil
-Original Message-
From: Amadeus [mailto:amadeus.h...@diadrom.se]
Hi,
I got the following Wix 3.6 solution in VS2012 :
http://schemas.microsoft.com/wix/2006/wi";
xmlns:util="http://schemas.microsoft.com/wix/UtilExtension";
xmlns:netfx="http://schemas.microsoft.com/wix/NetFxExtension";>
I've tested some more and during installation and upgrade I checked the
Installer/Dependencies location in the registry.
During installation, all packages are correctly put there as dependent to my
installer.
During upgrade, all packages - except one - are put there as dependent to my
installer.
Hello,
I have an odd problem. It's not /really/ related to Burn and I believe the
problem lies with the MSI - but I think (hope) you can help me out.
My scenario is this:
When I upgrade the Bootstrapper one of the MSI Packages is always detected
as *not* having a dependency to the old Bootstrappe
30 matches
Mail list logo
