Hi All,
I have 2 msi of the same product(on with version 2.0.0.0 and other with
version 2.0.2)
Both msi have the same ProductID,UpgradeID
I have created 2 small patch (msp) on version 2.0.0.0 to upgrade to 2.0.2
Now i want to create a small patch with version 2.0.3 which should work
on both the
Hi All,
I have previously released 2 versions of an application (lets call them
Version A and Version B) and are about to release a third version
(Version C). I would like to release a patch that will patch version A
to C or version B to C but cannot find any documentation to cover it.
I can
Hi,
I got a requirement to disable/bypass UAC prompt. Is it possible do that for
an MSI which will copy files to program files, adds a registry entry, create
apppool and website???
I dont want to do anything in OS level to disable UAC.
Let me know if you need more info regarding this.
Thanks
2014-08-12 11:53 GMT+02:00 kpanilkumarmca kpanilkumar@gmail.com:
Hi,
I got a requirement to disable/bypass UAC prompt. Is it possible do that for
an MSI which will copy files to program files, adds a registry entry, create
apppool and website???
I dont want to do anything in OS level to
Hi,
We have 3 flavours of our product and thus 3 separate msi's - ProductA.msi,
ProductB.msi ProductC.msi and a bootstrapper exe that installs various
common pre-requisites for all the flavours of the product. At the moment, we
ship a copy of the bootstrapper and one of the msi to our customers
ok so I can achieve this by using a BAFunctions.dll, which I believe is in
C++? is there any documentation on how to setup BAFunctions.dll for my
HyperlinkTheme or would it be better to create my own managed ba?
--
View this message in context:
The only way to disable UAC is to do in the system parameters which requires a
reboot of the system to take effect.
The best way to deal with this is to use a bootstrap EXE that handles the
prompt upfront and then launches the MSI.
Any changes to IIS that touch the master control file require
Hi!
I'm developing a managed bootstrapper application, and have run into a peculiar
problem. I'm testing the following scenario for a simple single-package bundle:
* Install version 1.0
* Upgrade to version 1.1
* Run the version 1.1 installer again
When doing this, the package is detected as
I'm sure there is a way to make PreBuildEvent or BeforeBuild work, but I
gave up trying to figure it out. I ended up making a couple of empty
build sync projects that have post build steps that do the same as my old
prebuild steps. The wix projects reference one or more of the sync
projects.
It
You can make a patch to update both A - C and B - C but I don't think you can
selectively make it also update A to B.
C is the what you specific in the UpgradeImage section of your Patch Family
(the 'destination').
A B should be specified as TargetImages (the 'source').
e.g.
Family
Something doesn't compute there. Can you be a bit more specific about what
upgrade in step 2 means? Also, does OnDetectRelatedPackage provide useful info?
___
FireGiant | Dedicated support for the WiX toolset |
I have a WIX installer custom BA. In it I have 2 buttons. In the click event
handlers I set some variables so I can only determine which features of the
product I need to install. When I execute the InstallCommand it doesn't
start the install, instead the log says canceling...
My code is...
Hi,
What I mean is that I have a newer version of the bundle, which installs the
new version and removes the old version. Does that answer the question?
It seems DetectRelatedPackage does not fire, and neither does
DetectRelatedBundle (The log covered the entire detect phase). I'll do some
The engine runs asynchronously on a separate thread. Try removing the
this.Close and see if it works.
-Original Message-
From: garymonk [mailto:g...@gurudental.com]
Sent: Tuesday, August 12, 2014 10:21 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Cannot execute the
Hm, I noticed I there were warnings when compiling the msi file, the
Product/@Id was not set to *, and the Package/@Id was set. When I set product
id to * and removed package id, this behaviour seems to go away.
Could this be the actual cause, or is this an unrelated bad thing, and it
just
If Product/@Id was not changing you were not major upgrading your packages.
___
FireGiant | Dedicated support for the WiX toolset |
http://www.firegiant.com/
-Original Message-
From: Carl Pettersson
In the wix toolset source download, at src\tools\WixTasks\wix200x.targets ,
in browsing through that file (and other similar .targets files) it lists
the various MSBuild Targets which can be redefined. So when I was trying
to understand the wix build process I created a simple
Thanks for the response Jacob. I commented out the close and it didn't still
install.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Cannot-execute-the-ICommand-InstallCommand-in-C-code-behind-tp7596330p7596336.html
Sent from the wix-users
I have a burn bundle that uses the built-in WiX Bootstrappre UI. Is it possible
to silence this UI on uninstall and only display the UI of one the MSI packages?
--
___
I have a method OnDetectPackageComplete in my Wix Bootstrapper application
that gets launch when the detectpackagecomplete event is fired. Within that
method, I would like to retrieve status whether BA application is running
for installing or an uninstalling a package.
For example, if the user
20 matches
Mail list logo
