Sounds to me like you only need to schedule RemoveExistingProducts in your
InstallExecuteSequnce.
From: Robert Lee [mailto:genrobert...@gmail.com]
Sent: Wed 11/30/2011 3:12 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Is major update supposed
Did you schedule RemoveExistingProducts and include an Upgrade table?
Ex:
...
...
and
Jacob
-Original Message-
From: Robert Lee [mailto:genrobert...@gmail.com]
Sent: We
I would like to develop an installer so that it would NOT force the user to
uninstall the application manually prior to installing new version. Just
running the new msi should update everything automatically.
As far as I understood the wix book, in order to achieve that, I should set
product ID in
Is there a list of possible error responses when using the -layout command
with the burn app? I tried digging through the source without much success
and hope someone can point me in the right direction.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.co
The actual case-sensitive property name is SourceDir:
http://msdn.microsoft.com/en-us/library/windows/desktop/aa371857(v=vs.85).aspx
SOURCEDIR is likely to be something internal that you should not be using.
Phil Wilson
-Original Message-
From: Parkes, Kevin [mailto:kevin.par...@wac
Scan the verbose log for VerifyUserInformation. The WcaInitialize call
should log the invocation of the custom action.
>From there, you should see the remaining lines of the log file (assuming
you hit next, but then didn't continue any further in the installer).
Also, I have had times where the r
I ran the above. Didn't find any of my logs in the output log.
Anything in particular I should be looking for?
--
All the data continuously generated in your IT infrastructure
contains a definitive record of customers,
On 30/11/11 16:26, Hoover, Jacob wrote:
> Use the logging functionality of Windows Installer. This allows you to
> specify the log file name at the time you invoke the installer, and will
> put the CA messages in context with the rest of the installation
> messages.
>
> msiexec /i foo.msi /l*v C:\T
Use the logging functionality of Windows Installer. This allows you to
specify the log file name at the time you invoke the installer, and will
put the CA messages in context with the rest of the installation
messages.
msiexec /i foo.msi /l*v C:\Temp\MyLog.log
The above command turns on verbose l
Hi
I know this is older mail but found one solution and I also need another
one :)
So I managed to get error code by creating embedded UI handler DLL.
Everything what I do there is that I catching INSTALLMESSAGE_ERROR and
reading value from first field of input record.
INT WINAPI EmbeddedUIHandle
Seems I was mistaken about RegistrySearch and it is working correctly (sorry
for wasting anyone's time on that).
DirectorySearch is, however, still failing on silent install. It seems to be
because the search is relative to [SOURCEDIR] but, in silent mode, [SOURCEDIR]
is not being set until aft
On 30/11/2011 11:00, Albert van Peppen wrote:
> If someone of the wix team can provide me with the weekly set I am more than
> happy to put it on my WiX mirror.
> But as said, there are currently no weekly releases, to my knowledge, so I
> can't update my mirror. :(
You could always create your
If someone of the wix team can provide me with the weekly set I am more than
happy to put it on my WiX mirror.
But as said, there are currently no weekly releases, to my knowledge, so I
can't update my mirror. :(
Albert van Peppen
WiX Mirror: http://madbutcher.dyndns.org/snippets/WiX/
-
On 30/11/2011 09:07, Sean Farrow wrote:
> Hi:
> Havv3.6.2221.0?
> I don't see any and wondered whether updats had moved.
> Regards
> Sean.e there been any weekly updates later than
That's an impressively mangled email! I believe there's a plan being
worked out since the bandwidth quota was being
Blair,
I am a complete novice to this. The person who originally wrote our XML is
no longer at the company.
How do I get complete logging information out of the MSI when it is run?
Incidentally the directory structure is correct.
The ProgramFiles folder is for the DAM itself which is a service. (
Solved by adding BinaryRef elements for the WIXUI_Bmp_Banner and
WixUI_Bmp_Dialog to the PatchFamily.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/MaintenanceWelcomeDlg-bitmaps-tp5180966p7046235.html
Sent from the wix-users mailing list archive at
DTF custom actions can extract additional files to work with when they run.
See this thread and others on the list
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Extract-Binarie
s-at-Install-Time-td2301189.html#a2314132
-Original Message-
From: Lluís Batlle i Rossell [mailto
Yes that's expected. Remove the RemoveExistingProducts element from the
installexecutesequence and control its scheduling with the Schedule attribute
of the MajorUpgrade element instead. You can even omit the Schedule attribute
since its default value will give you the same result as you have there
I have a WiX setup project in Visual Studio, and I'm having problems
referencing an extension dll. If the dll is located on my local machine, there
is no problem adding the reference, but if I try to reference the same dll on a
network share, I get the following error message:
"A reference to [
Hi:
Havv3.6.2221.0?
I don't see any and wondered whether updats had moved.
Regards
Sean.e there been any weekly updates later than
--
All the data continuously generated in your IT infrastructure
contains a definitive reco
On 29/11/11 19:23, Chad Petersen wrote:
> That does seem overly complex right out of the gate. Have you taken a
> good look at the Binary element? This is how I make my files
> available to my custom actions without having to copy anything to the
> local computer. Might not be what you are after, b
I had a problem like this recently, I used a trial of revo uninstaller.
On 29/11/2011 21:27, Neil Sleightholm wrote:
> I believe this is the replacement for MSI-Zap
> http://support.microsoft.com/mats/program_install_and_uninstall/
>
> Neil
>
> -Original Message-
> From: Chad Petersen [ma
22 matches
Mail list logo
