Why are you preventing people from uninstalling your product? You're never
going to be able to
upgrade your installation or repair it.
Rob
Lian Jiang wrote:
This one worked for me:
Condition Message=Uninstall is not supportedREINSTALL or Not
Installed/Condition
Thanks
Lian
Hi Blair,
I found an article from MSDN, which is talking about multiple instance. I think
my requirement is similiar like multiple instance, although the software
version could be different.
The link is here
http://msdn.microsoft.com/en-us/library/aa369528(VS.85).aspx
It says:
The easiest
My moneys on it being this -
http://msmvps.com/blogs/installsite/archive/2009/09/12/microsoft-s-recen
t-security-updates-for-visual-studio-break-windows-installer-updates.asp
x
See also -
http://www.msigeek.com/microsofts-recent-security-updates-for-visual-stu
dio-break-windows-installer-updates/
hi all,
i've a product and i'm delivering the minor upgrades(patches), i've a
requirement like i need last upgrade(patch) information to use that info in
the current upgrade(patch).
can any one help me on how to get the last upgrade(patch) information like
product version? please help me.
Hi,
Could you help me, please, with the next issues related to minor upgrades:
1. What are the possibilities/recommendations for creating a minor upgrade with
Wix (or in general with the installer)? Until now I know that a Service Pack is
a possibility (is this correct?).
2. What are the
Hi Kalev,
I already set that element Vital=Yes, Still I get the message with ignore, ok
and cancel buttons. If I click ignore installer ignore the filter without
register. What I want is when error occurs I need to restrict buttons like ok
only button. Is it possible?
Thanks
Selva
1. The pages in this section of the MSDN discuss different update types
supported by Windows Installer and therefore by Wix too.
http://msdn.microsoft.com/en-us/library/aa370579(VS.85).aspx
2. This should help http://support.microsoft.com/kb/824684
3. Roughly speaking, there is a difference
Just a guess, but in seeing that the registry entry is in the Installer
area, I am wondering if in the IS install if these private assembly files
are marked as the KeyPath, which is why they are being recorded here?
As far as the crashing is concerned, have you confirmed if your private
assembly
Pally,
Thanks for pointing this out. I don't believe that this has anything whatsoever
to do with the behavior that I'm seeing. My problem is that there are way, way
too many files in the patch, not that anything is being changed from
installed to advertised. I'm not getting far enough to
Never mind. Looking at the PCP file in Orca, I can see that there is no listing
of the upgraded files there, as I would expect from any other MSI database. So
I suspect that you're right, Bob. I should be able to run the MS procedure for
building a patch, and get the same problem.
Thanks,
John
You are running the MS procedure for building a patch. All WiX is being
used for in this instance is to create the PCP file.
Sigh.
Palbinder Sandher
Software Deployment IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate
Add this, maybe it will help in your case...
Condition Message=You must be an administrator to install this
application
Privileged
/Condition
I believe you get the UAC prompt...
-Original Message-
From: Sachin Dubey [mailto:sachin.du...@live.com]
Sent: Tuesday, November
Just a guess, but in seeing that the registry entry is in the Installer
area, I am wondering if in the IS install if these private assembly files
are marked as the KeyPath, which is why they are being recorded here?
I couldn't say. The WiX version has them marked as keypath also.I'll do
John that doesn't necessarily generate a UAC prompt. It will simply
check if the user has the permissions necessary to generate a UAC prompt
before the MSI installs.
Sachin is your custom action running during the InstallUISequence or
InstallExecuteSequence? What is the Execute attribute of the
Hi,
I'm relatively new to WiX and am using WixUI_FeatureTree for the first time.
I have two small installations that I'm trying to combine into one script.
One for the Client and one for the Server. I'm trying to make both Features
in the FeatureTree to default to Entire Feature will be Disabled
I for one have never understood or really dug into why it would even matter.
.NET is supposed to be XCopy deployment so if I deploy a .NET assembly
privately, why would or should MSI even care that it happens to be a CLR
assembly? That said, I always select Properties Only in InstallShield
My suspicion is that you're right, and I think that's the area where each
assembly is recorded together with info for MsiProvideAssembly(), and it won't
be there if it's not the keypath.
Phil Wilson
-Original Message-
From: Andreas Mertens [mailto:andre...@nvisionideas.com]
Sent:
Christopher,
I appreciate your enthusiasm and advice.
.NET is supposed to be XCopy deployment
You are correct about this. If I take a clean machine (with .NET
installed) and then
1. Install the IS original,
2. Install my WiX-produced version,
3. Copy both directories to a new clean
... decompile the old one with dark.exe to see what's different.
Thanks for the suggestion, Bob. This allowed me to pinpoint where in my
WiX code the problem lie.
--
Let Crystal Reports handle the reporting -
On Tue, Nov 17, 2009 at 10:10 PM, JKLists jkli...@ifm-services.com wrote:
... decompile the old one with dark.exe to see what's different.
Thanks for the suggestion, Bob. This allowed me to pinpoint where in my
WiX code the problem lie.
Would you mind to share that? Don't want to mock you
I created an installer that contains 2 Upgrade sections for 2 different
products that are installed however when I run the installer it only locates
one of them. How do I go about debugging this to find out why the 2nd is not
detected by FindRelatedProducts? I did a small test app and this
I'd like to know how to force to launch the application in silent install mode.
I thought this would work:
msiexec /i myapp.msi WIXUI_EXITDIALOGOPTIONALCHECKBOX=1 /qr
But after installation, the application wasn't launched. By the way, we use the
'standard' way from Wix.chm(How To: Run the
In our code, we have this:
Property Id=WIXUI_EXITDIALOGOPTIONALCHECKBOX Value=1 /
So the checkbox is checked by default. I thought that means launch the
application by default. But the application was not launched in quite(silent)
mode:
msiexec /i myapp.msi /qr
I then tried to set property
Hi, All,
A: main installer
B: sub installer
1. A is installed.
2. When A is installed, B is copied onto a local disk together.
3. B install if necessary.
4. When A is uninstalled, B is automatically uninstalled.
Is it possible though I wants to make two installers of such a composition
Hi,
Q1, Set the Feature's attribute Level to 0, then it will be disabled.
Q2, Feature have some action states and install states, and you can use this
to force users to choose only one of them.
Prepending some special characters to the names will give them extra meaning:
%
In quite mode, the InstallUISequence is never executed, so the
checkbox doesn't even really exist (only the property related to the
checkbox)
The documentation shows how to tie in execution to when the user
clicks the Finish button - this button never exists and is never
pushed in a silent
hi,
how do i make sure that the Launch Condition only executes only on Installed
???
for now, my installer executes the Launch Condition on uninstall.
Anyone here with suggestions ?
--
View this message in context:
Thanks John and Pally for your responses on this. Greatly appreciated!
My custom actions is running in InstallUISequence for checking the prerequisite
software.
The execute attribute is 'immediate' as the action need to be executed before
the next dialog box appears.
Thanks
Sachin!
Add to the conditions your are check a NOT Installed to check them only if
the application isn't installed yet
Best regards,
Sebastian Brand
Deployment consultant
E-Mail: sebast...@instyler.com
Instyler Setup - Creating WiX-based MSI installations, elegantly.
http://www.instyler.com
On
When you cannot merge these two installers into one, it's recommended to use a
bootstrapper to check and run necessary installations. I'm not sure if WiX'
burn can handle this already..
Best regards,
Sebastian Brand
Deployment consultant
E-Mail: sebast...@instyler.com
Instyler Setup -
Doesn't the msi verbose log say anything?
Best regards,
Sebastian Brand
Deployment consultant
E-Mail: sebast...@instyler.com
Instyler Setup - Creating WiX-based MSI installations, elegantly.
http://www.instyler.com
On 17.11.2009, at 22:55, Tom Crozier wrote:
I created an installer that
31 matches
Mail list logo
