Hi all!
Need help. Some msi's have been distribured in Windows domain over GPO as
per-user installations.
Now I need to upgrade them, upgrades are per-machine (this is better for my
purposes).
What is proper way to uninstall old applications?
Seemed like I can't to upgrade them via Wix code
Great ... thanks !!
On Tue, Jun 19, 2012 at 11:12 AM, Hoover, Jacob
jacob.hoo...@greenheck.comwrote:
Given the contents, you appear to be referring to the example either at
http://blogs.msdn.com/b/pmarcu/archive/2007/06/28/sample-patch.aspx or
Hi,
I downloaded the sample and compiled it from the command line as :
Candle.exe SampleFirst.exe
Light.exe SampleFirst.exe -o SampleFirts.msi
and i install the msi however it only showed me a single dialog as setup is
configuring the foobar setup and exit without prompting for any dialog
ltes
Hi,
I'm using wix iis extention for creating web application, installing
certificate and configure webapplication to requier ssl
Is there a way to do a http redirection via wix?
Thanks
--
Live Security Virtual
There is a complete list of properties at
http://msdn.microsoft.com/en-us/library/windows/desktop/aa370905%28v=vs.85%29
.aspx
UPGRADINGPRODUCTCODE is probably what you're after.
-Original Message-
From: Ravi Raj [mailto:raviraj.callin...@gmail.com]
Sent: 19 June 2012 06:10
To: General
I was trying to use UPGRADINGPRODUCTCODE but none of the features are not
working so I decided to go with OLD_VERSION_FOUND and things are going
pretty smooth. But will it be nice. I am not sure why former was nor
working?
On Tue, Jun 19, 2012 at 2:35 PM, Peter Shirtcliffe
Hi all,
I have such a situation that we want to keep the registry keys we add at the
installation (so that when the software is installed again it can find the
relative information), I think this can be achieved by setting the Permanent
property to yes of the component which includes target
I have authored an installer using Wix 3.6 RC. I have a checkbox in the
dialog UI which is disabled and unchecked initially. There is a Verify
button next to it. When I press this button a custom action gets executed
(immediate) and sets a value of parameter which decides whether check box
gets
I would recommend looking through that entire tutorial, as it's very useful
and informative for a new WiX user. In general, the underlying Windows
Installer framework that WiX uses does not provide any type of UI for the
installer, short of the configuring dialog that you witnessed. If you're
raviraj87 wrote
I am using
session.Message(InstallMessage.Error | (InstallMessage)(icon) |
(InstallMessage)MessageBoxButtons.OK,
new Record { FormatString = message });
to display any messages during deferred CA and everything works great.
The message box
For info it is working for me, I can open an existing project which then
upgrades and create a new one.
Neil
-Original Message-
From: Naim Kingston [mailto:naim.kings...@ancamotion.com]
Sent: 19 June 2012 03:14
To: General discussion for Windows Installer XML toolset.
Subject: Re:
I have created WiX installer package for the new project I am working on and
have a little unresolved issue related to proper registering the web
application into IIS7.
The problem is that my web application is registered with incorrect Physical
Path credentials property value (this property
Generally, your User element authoring should look something like this:
util:User Id=AppPoolUser CreateUser=no FailIfExists=no
LogonAsService=yes RemoveOnUninstall=no UpdateIfExists=yes
Name=[ACCOUNT_NAME] Password=[ACCOUNT_PASSWORD] /
The key difference is that your authoring is missing
I'm working on an Installer to setup a website, add backend apps
(these are for datamining and written in VB6) along with a database.
In using WiX 3.6 along with Visual Studio 2010 I have been able to
complete the following:
- Backend Files placed in correct directories under Program Files
-
OLD_VERSION_FOUND is not standard property, so my guess is that it's set via a
search or the Upgrade table in the new MSI that you are installing.
UPGRADINGPRODUCTCODE is set in an uninstall when it is being upgraded by a new
product.
Phil W
-Original Message-
From: Ravi Raj
As you found, the Windows Installer does not support cross scope upgrades.
You need to remove the per-user MSIs via some other mechanism first. Not
sure GPO has a way to remove it all.
On Mon, Jun 18, 2012 at 11:37 PM, Роман М. Кудрявцев
kudryavce...@vnipigaz.gazprom.ru wrote:
Hi all!
Need
hi -
this morning i tried installing my msi without using a full UI and noticed
that the logfile output by the installer shows the dll getting hit.
it seems that InstallExecuteSequence (or the way i am using it) only
happens during non-UI installs. i am currently reading docs about
This really smells like
71 CustomAction Id=CheckingSecurityToken
BinaryKey=libprovisionmeter DllEntry=provision_meter_msi /
Is actually
CustomAction Id=CheckingSecurityToken BinaryKey=libprovisionmeter
DllEntry=provision_meter_msi Execute=firstSequence /
In non UI installs, only the
Can someone please explain the process of chaining msi's? I assume that I
have to create a Bundle then a Chain tag, but how do I continue from there?
I have the two msi's finished, and one must be completed before the other.
Thank you in advance for any help,
Dan
--
View this message in
I was aware that The mba (Managed Bootstrapper Application) can install the
.NET
Framework *before* your managed BA comes up. That's actually howthe WiX
toolset works. Install it on a machine with out .NET Framework and it will
first install .NET Framework then launch the custom BA. There is
Thanks in advance for any help!
I have a 32 bit installer that needs to run on both 32bit and 64 bit machines.
The problem occurs when installing the current (security-fix) VS 2005 merge
modules provided by Microsoft (dated 5/14/2011).
-- The problem does not occur if I remove the merge
I also like to add an AssertSz(FALSE, Debug here); from the wcautil.h.
That pops up a dialog box with all the information what process to attach
to (since there will be multiple msiexec's). If the assert doesn't fire,
then I know the problem is with the CustomAction scheduling.
Of course,
Random guess, mark the Merge/FileCompression=yes. It is very possible the
VS2005 merge module incorrectly marked all of it's Files as explicitly
compressed or uncompressed and you need to force it. I'm assuming you have
a compressed MSI.
On Tue, Jun 19, 2012 at 1:33 PM, Carl Tietjen
0. If your product does not need the .NET Framework then by all means do
not install it just to write a managed BA. You can just as easily (assuming
you are already writing native code smile/) write a native BA, just like
wixstdba.
1. I don't necessarily agree. We added support for creating
Documentation of the basics is here:
http://wix.sourceforge.net/manual-wix3/authoring_bundle_intro.htm
Was that not at all helpful?
On Tue, Jun 19, 2012 at 11:37 AM, Dan Muller dmuller...@comcast.net wrote:
Can someone please explain the process of chaining msi's? I assume that I
have to
Hello,
I was reading the property reference
http://msdn.microsoft.com/en-us/library/windows/desktop/aa370905%28v=vs.85%29
page for UPGRADINGPRODUCTCODE and it says UPGRADINGPRODUCTCODE is set when
RemoveExistingProducts is executed. How can I base my dialogs then, if
RemoveExistingProducts is
Hello,
How can I continue logging if during the install I force a reboot, then the
installer resumes after reboot? Also, after the reboot, how can I resume
the installer to the last position before reboot instead of running the
installer from the beginning again? I don't want to have to
UPGRADINGPRODUCTCODE is set in the product being *uninstalled*, the target of
the RemoveExistingProducts, not in your code that is calling it. If you want to
have a dialog because your setup has detected that it is upgrading an older
existing product, then base that dialog on the property being
Out of interest, what OS are you running? Do you have Service Pack 1 for VS
2005?
-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com]
Sent: Tuesday, 19 June 2012 10:43 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Wix fails to
On 19-Jun-12 17:45, victorwhiskey wrote:
How can I continue logging if during the install I force a reboot, then the
installer resumes after reboot?
There's no way native to MSI to do that (though it is supported with
Burn). With MSI 4.0 and later, you can use the MsiLogging property but
it
On 14-Jun-12 19:11, john.burak wrote:
The docs for the ServiceDependency Element say:
Id: The value of this attribute should be one of the following:
1. The name (not the display name) of a previously installed service.
*2. A foreign key referring to another ServiceInstall/@Id.*
Not sure what
On 14-Jun-12 12:12, Bob Uva wrote:
I'm trying to use the FeaturesDlg in WixUI_Advanced but I cannot get the
Wix tools (called through Visual Studio) to recognize FeaturesDlg, the xml
tag. I've tried adding a UIRef tag with the Id=WixUI_Advanced as
suggested in the help file, but it still is
I want to store a textbox value in registry but my situation is little
different.
I am doing a registry search for a particular key value and populate this
value into the textbox and again storing this value to my custom registry
key.
Everything is working great until now, but I found if I change
I was able to do that when I used the Upgrade element, but now I'm using the
MajorUpgrade element and there is no where to set a variable like the
Upgrade element. How do I do that with MajorUpgrade?
Thanks
--
View this message in context:
Sorry Bob, can you give me an example of using the AFTERREBOOT property and
how to skip to the last position before reboot?
Thanks
--
View this message in context:
Great thanks.
--
Sincerely yours,
mr. Roman M. Kudryavcev
Support specialist, programmer
JSC VNIPIgazdobycha
mailto:kudryavce...@vnipigaz.gazprom.ru
JSC VNIPIgazdobycha official e-mail is
b...@vnipigaz.gazprom.ru
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
36 matches
Mail list logo