I want to display a dialog when uninstalling a patch from the command line.
I can do that using the following commands, but it uninstalls the whole
app. I just want the patch uninstalled:
When I use this command it uninstalls the whole app:
msiexec /package my.msi /uninstall my.msp
This also does
But they are listed there! I just haven't used /passive because I need a
dialog to be displayed. The dialog gets displayed its just that the whole
app gets removed rather than just the patch.
warm regards
Rob Goodridge
On Fri, Mar 29, 2013 at 3:24 AM, Phil Wilson-2 [via Windows Installer XML
(W
On Windows 7+ yes. No way to disable inside MSI pre-Win7.
On Thu, Mar 28, 2013 at 4:04 PM, Alain Forget wrote:
> This makes a lot of sense, frankly. I'm leaning towards opting out of the
> system restore altogether. I take it adding this will be
> sufficient to do so?
>
>
>
> Source:
> http://
This makes a lot of sense, frankly. I'm leaning towards opting out of the
system restore altogether. I take it adding this will be
sufficient to do so?
Source:
http://msdn.microsoft.com/en-us/library/windows/desktop/dd408005%28v=vs.85%29.aspx
Alain
-Original Message-
From: Neil Sleig
>> Rob's personal preference matches mine which is system restore is more of a
>> pain and disk hog than it's worth so we disable it on our machines.
+1 for that, I disable it in my burn releases as I find my users don't
understand it, rarely use it and by the time it would be useful have instal
Ah, gotcha! The UI ProgressText works does just as we want! Thank you. :-)
Alain
-Original Message-
From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com]
Sent: March 28, 2013 15:45
To: afor...@cmu.edu; General discussion for Windows Installer XML toolset.
Subject: RE: [WiX-users] No us
If I had to guess, Rob's personal preference matches mine which is system
restore is more of a pain and disk hog than it's worth so we disable it on our
machines.
1) You don't need to integrate the controls, those are the ones that exist
within the UI set you are using.
2) That will only set t
Alright, good to know that if at some point we start using burn, we may need to
change tactics. Interesting that Rob always turns of
system restore...do you mean on your own machines, or in the installers you
make?
As far as Jacob's advice, it seems currently beyond my understanding of
WiX/MSIs
*and* Burn will take one system restore up front before installing all the
MSIs with system restore point creation disabled. Don't want people
thinking system restore is completely ignored (although I always turn it
off since I don't trust it to be able to actually succeed ).
PS: Set your initial
Oh snap, all my responses were under the impression that he was using Burn. I
now re-read it and realized this was WixUI_Minimal... Different problem domain,
different solutions.
The controls in question are one of these
Thanks for the feedback.
Marc
-Original Message-
From: Daniel Madill [mailto:dan.mad...@quanser.com]
Sent: March-28-2013 2:06 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] VS Building using Different platforms
Hello Marc,
It is probably just pers
Hello Marc,
It is probably just personal preference. I like having one solution and one
project with one set of source files that can build both the 32-bit and 64-bit
installers because it's easy to maintain. For one product we build both on the
same 64-bit build server using a simple scheduled
Interesting; it seems your experience differs from ours.
For us, this is happening on up-to-date Windows 7 Enterprise machines. We
currently don't use burn; just candle and light. Finally,
I think our MSI needs the minimal interface just so the user knows the
installation is working and is succe
Thanks for the reply.
I implemented both to see how each works, both methods work very well.
Personally I prefer using the define method, because it is part of my
sources without having to play in the project files.
Except for personal preferences are both methods equally acceptable, does
not ha
Hm, I see now how it's a more difficult problem than I first thought. Logging
it as a feature request would be good. I'm not sure
where/how that can be done, so it'd be great if you add it. Thanks.
Alain
-Original Message-
From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com]
Sent: Ma
Chad,
Thanks for your reply.
I am keeping the UpgradeCode="$(var.UpgradeCode)" the same.
Version="$(var.VersionNumber)" does change. On my initial package this
was 2.1, on my new package it was 2.2.1
I have not changed this variable:
Id="$(var.ProductCode)"
The tutorial states that if you do c
Hello Marc,
I do this all the time, building both a 32-bit MSI and a 64-bit MSI from the
same source simply based on the platform selected. I have a WiX include file
containing the following:
Sadly, the API call to create a restore point is blocking and doesn't provide a
callback for status updates. If simply displaying a message on the UI that the
installer is creating a restore point would provide value, a change to WixStdBA
and the engine inside of OnApplyInitialize would have to
Thanks for the reply... I'll implement it like this too.
-Original Message-
From: Steven Ogilvie [mailto:steven.ogil...@titus.com]
Sent: March-28-2013 12:23 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] VS Building using Different platforms
I am
In the same way you add conditions to any action such as a custom action -
there's nothing different.
As a rule, there's no need to add a condition to REP because it does its
thing only if an upgrade has been detected. What problem are you trying to
solve?
Phil
-Original Message-
From:
These are not command line choices I've seen or used. Why not those listed
here?
http://msdn.microsoft.com/en-us/library/windows/desktop/aa372104(v=vs.85).as
px
Phil
-Original Message-
From: robe070 [mailto:goodridge@gmail.com]
Sent: Wednesday, March 27, 2013 5:38 PM
To: wix-users
Just an FYI...
We ran into a different manifestation of this problem on a couple of HP
computers. In this case the Uninstall\@InstallLocation was
\Hewlett-Packard\ and caused the installation to fail very early with a
"Can't find network location \Hewlett-Packard\" (or something like
that) erro
I am doing the same thing, you need to have 2 MSI's one for 32 and 64 bit:
I modify the project file:
32 bit solution file:
GlobalSection(SolutionConfigurationPlatforms) = preSolution
DebugX86|Mixed Platforms = DebugX86|Mixed Platforms
ReleaseX86|Mixed Platforms =
I've only seen this on Windows XP where the computer wasn't up-to-date with
Windows updates and in that case it took so long because the restore point
failed.
I use burn and have no GUI in my MSIs.
-Original Message-
From: Alain Forget [mailto:afor...@cmu.edu]
Sent: March-28-13 12:57 P
I don't believe this is anything to do with WiX.
The underlying API (SRSetRestorePoint) has no callback to show progress, so
if this code is in WiX there's nothing it can do. If it's being done by
Windows as part of the MSI install there's likewise very little you can do
about feedback other than
Hello
I searched and can't find anything on the subject, my guess is my search is
inaccurate since I am not sure how to explain this.
I have an MS VisualStudio 2012 wix project that when I compile my solution
it I output an MSI using the newly built binaries.
That being said I would lik
I can't be the only one with this or a similar problem of the installer hanging
for a long period of time without any useful
information for the user.
Surely someone has some idea for solving this? Or should this be filed as some
kind of WiX bug report?
-Original Message-
From: Alain F
Hiya Jacob,
Yeah, I went with number one in the end, two was too dangerous, three sounded
like a maintenance nightmare (seeing as the 3rd party dll is likely to change
again in the future) and I couldn't get four to work.
Cheers,
Jack
-Original Message-
From: Hoover, Jacob [mailto:jac
I don't like any of these per say, but just throwing some ideas out for you to
ponder/try.
1) Rename the file and have it in a different component
2) messing around with REINSTALLMODE to force overwrites. (Would be very bad
if your MSI installed any shared components)
3) I see a hackish appro
I failed to mention that I am using WiX Toolset v3.7
Tim Hawes
Programmer
haw...@anx.com
On 03/28/2013 10:24 AM, Tim Hawes wrote:
> I have been wracking my brain on this for a day and a half. I am trying
> to make an installer that will uninstall the older version of the
> software and install th
I'd bet you haven't changed this variable.
Id="$(var.ProductCode)"
While in there make sure this is set to what you want also.
Version="$(var.VersionNumber)"
Make sure you do keep this one the same (it is if you get the message you
mentioned)
UpgradeCode="$(var.UpgradeCode)"
-Original
I have been wracking my brain on this for a day and a half. I am trying
to make an installer that will uninstall the older version of the
software and install the new. The old version is in the registry as 2.1
and the new one I am trying to install is 2.2.1
For the life of me, I cannot create a
Hiya Jacob,
It's currently the default, which is afterInstallValidate which is even earlier
I think.
Cheers,
Jack
-Original Message-
From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com]
Sent: 28 March 2013 14:24
To: General discussion for Windows Installer XML toolset.
Subject: Re:
You could try scheduling remove existing products earlier, after
InstallInitialize.
-Original Message-
From: Jackson Pope [mailto:jackson.p...@nonlinear.com]
Sent: Thursday, March 28, 2013 3:28 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Upgrading an Install fails to dow
It's been my experience that EXE Packages need detect conditions. Also, if you
need the Sentinel package to be there, why not mark it as Vital?
-Original Message-
From: Monitor Vlecad [mailto:monitor.vle...@gmail.com]
Sent: Thursday, March 28, 2013 3:20 AM
To: wix-users@lists.sourceforg
I tried reproducing the error but couldn't. Only way I could get it to fail
was to encrypt the MSI after it was placed in the cache as I mentioned
previously.
Looks like when burn places a MSI file in the cache it prevents encryption or
unencrypts the file, not sure. It doesn't unencrypt
Hi Ravi,
I can at least solve your installing SQL Server Express...
I would use burn (bootstrapper) to chain the SQL Server Express installs and
your MSI
I do this to install SQL Server Express 2012
In Burn:
-Original
Hi Rob,
Please find below my requirement and am new to WiX...
The installer should perform the below activities
1.Install MS SQL Server 2005 Express
2.Create Database and attach a *.mdf file
3.present installer files are developed in VB 6, so the installation
should create the necesary folder st
Yes, a SqlString can do that. Connect to the "master" database then use the
SQL string to attach the file. Sorry,I don't have time to write up a full
example.
On Thu, Mar 28, 2013 at 1:33 AM, Ravishankar <
ravishankar.krishnasw...@idsnext.com> wrote:
> Hi,
> Is it possible to attach the SQL Serv
Hi Paul,
Please find below my requirement and am new to WiX...
The installer should perform the below activities
1.Install MS SQL Server 2005 Express
2.Create Database and attach a *.mdf file
3.present installer files are developed in VB 6, so the installation
should create the necesary folder s
The bug is fixed. It was related to anchor top and bottom. The behavior seemed
to vary between the old and new release. The original was simply anchor top.
I've changed to anchor top and bottom and extended the fields across the page.
Sent from my iPhone
On Mar 28, 2013, at 4:33 AM, Ravishan
On 28/03/2013 07:21, Karkare,Aparna wrote:
> Can someone tell me how to sign the WiX msi generating project with a key
> (.snk) file?
> I do not see 'Signing' tab under project properties unlike other VS projects.
You can't use a strong name keypair to sign .msi files since they're not
.NET asse
Hi,
Is it possible to attach the SQL Server mdf to the database instance?
Please send me a sample code.
Thanks and Regards
Ravi Shankar
--
Own the Future-Intel® Level Up Game Demo Contest 2013
Rise to greatness in Intel
Perfect. Thanks.
-Original Message-
From: Steven Ogilvie [mailto:steven.ogil...@titus.com]
Sent: 27 March 2013 17:47
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] WixUI_Minimal, removing license agreement dialog
Graham,
Try this:
Hiya all,
Similar to this question on StackOverflow
(http://stackoverflow.com/questions/4227456/windows-installer-deletes-versioned-file-during-product-upgrade-instead-of-down)
I've got a new version of an install that accesses an old version of a 3rd
party library.
Previous version (1.0) refe
hello,
I am using Wix for making a chain of installations : (.net framework
2.1, own-program1.msi, own-program2.msi, FirebirdODBC.exe,
Sentinel_SafeNet_Drivers.exe, VisualStudio_Redistributale_9.exe,
VisualStudio_Redistributale_10.exe)
When This chain runs, all goes fine, except on Windows XP.
Hi,
In general you cannot access/set any MSI properties in deffered custom
action. Change the script execution to immediate and you can use MessageBox
but this does not solve focus problem.
We use other (a bit ugly method): to use the same action/function in two
sequences we make action immediate a
Hello,
Can someone tell me how to sign the WiX msi generating project with a key
(.snk) file?
I do not see 'Signing' tab under project properties unlike other VS projects.
Regards,
Aparna Karkare
(O) +91-80 6624 3681
This communication, including attachments, is
48 matches
Mail list logo
