Hello,
I am having a small problem cleaning up the MSI that I am building through WIX.
Even though I have 'Name=' set to the proper name of the product in the XML
file the Title after building the MSI is the default "Installation Database."
I was hoping someone might have some suggestions.
;
;--- We will look for "UPX.EXE", if we find it we will configure MAKEMSI
;--- to compress the generated DLL...
;
Thank you just saw your reply :).. Sure would love to contribute :).. Will
check
with you offline in case of anyhelp
From: Rob Mensching
To: General discussion for Windows Installer XML toolset.
Sent: Mon, November 1, 2010 8:34:10 PM
Subject: Re: [WiX-
After trying out an example, I see the significance of the -var variable.
Regarding you example in using -var
How can I replace the value of "Source" to a physical path of the root
folder (like c:\temp\test) without having to use a wix variable
var.MySource? I am automating the generation of
How exactly do you get MakeMSI to do use LZMA compression?
I was intrigued by the question so I looked for and installed MakeMSI but I
can't find any references to LZMA compression.
Edwin G. Castro
Software Developer - Staff
Electronic Banking Services
Fiserv
Office: 503-746-0643
Fax: 503-617-02
Product element can be generated by giving " -template Product " in the
argument. If you type heat , you will see its syntax.
And I think -var is only used for the SourceDir and not to replace any
attribute in the file. This is my understanding, but please correct me if
this is not right.
Looks
Is that how MakeMSI does it?
I don't see why you can't implement upx into Burn...
On Thu, Dec 9, 2010 at 3:56 AM, Pally Sandher wrote:
> Been asked before (many many times, see nabble or mail-archive.com).
> Unless Windows Installer supports it, it's unlikely for WiX to support
> it. In this cas
I just saw the -template product parameter specified. That causes heat to
generate the element.
The -var parameter still works as shown previously in this case.
You could use the -t parameter to specify a XSLT transform to use to modify the
generated XML. You could author the XSLT transform to
Heat does not generate a element.
Heat /? shows the following documentation for -var:
-var substitute File/@Source="SourceDir" with a preprocessor
or a wix variable
(e.g. -var var.MySource will become File/@Source="$(var.MySource)\myfile.txt"
and
-var wix.MySource will become File/@Source
Hi Tobias,
Duplicating the RegistrySearch with Win64 "yes" and "no" seems to do the trick.
I can see two entries in the RegLocator table and when I run the MSI on x64
system it does read the right registry key. The two records in the RegLocator
table have different values in the "Type" column.
Hi all,
I am trying to generate a wxs source file using Heat.exe and wanted to
check if I can pass values for Manufacturer, Name, Title and version to
heat.exe? I tried using -var argument, but does nt seem to update it to the
source file
heat.exe dir c:\temp\Configuration\Files -ag -cg MyCom
will keep in mind...thanks.
On Wed, Dec 8, 2010 at 2:20 PM, Edwin G. Castro [via Windows Installer XML
(WiX) toolset]
> wrote:
> From http://msdn.microsoft.com/en-us/library/aa370568(VS.85).aspx
>
> "Nonidentical .msi files should not have the same package code. It is
> important to change the
@ Pally: Without trying I'd say when building with summary information
template = intel WiX also should build a package that ignores the
Win64="yes" parameter and therefore search also the wowtree on a x64
system? Had the issue sometimes before and the only solution was a
InstallScript InstallScrip
From http://msdn.microsoft.com/en-us/library/aa370568(VS.85).aspx
"Nonidentical .msi files should not have the same package code. It is important
to change the package code because it is the primary identifier used by the
installer to search for and validate the correct package for a given
inst
I have a fundamental question here:
I was considering retaining the PackageCode in the updated MSI. Can some one
advice if it is not advisable to have the same package code on the modified
MSI?
thanks,
sangeeta
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559
Hi Igor. Thanks for that. After reading your and Pally's message I
realized that the project had "warnings as errors" setting turned on,
which is why the build was failing with the ICE error. I think I will
use the Win64 attribute and suppress the warning for now.
@Tobias. Thanks for your suggesti
I have a requirement to update an existing MSI with new files and I am using
the DTP API to write to data base tables - Files, Components, Directory,
FeatureComponents, Media, etc.
I am doing a reinstall every time I have a new MSI to install
RREINSTALLMODE=VOMUS. This replaces all the files with
I think you'll need to describe your scenario in more detail. If you modify a
package by adding a new file and attempt to install it, then it won't work if
the previous version is already there - that ProductCode guid is already
installed. Are you doing an upgrade? Or is this a brand new fresh i
Sorry to bug you all with trivia, but I just wanted to take a moment and
tell everyone on the WiX team that you guys rock! I've been using it for
several years. I'm not a installer guru, but these tools and the support
you guys provide make this subtle science manageable for lay people like
myself.
Use the element is the WiX way to do it. Working very well for
me.
-Original Message-
From: Anu Dev [mailto:queryl...@yahoo.com]
Sent: Wednesday, December 08, 2010 9:01 AM
To: WIX
Subject: [WiX-users] Run DB Scripts
Hi
How can I run DBScripts during the installation process. I have se
I haven't had to use it myself but have you looked at WiX SQLExtension?
http://wix.sourceforge.net/manual-wix3/sql_xsd_index.htm It appears to have an
SQLScript Element which may or may not be what you're looking for.
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8
Hi
How can I run DBScripts during the installation process. I have seen an article
which looks for SQLCMD.exe and calls the respective .SQL files . Is this the
right way? Can anyone please point me to some pointers on the best practice to
run DB Scripts.
Regards
Anweshi
--
Been asked before (many many times, see nabble or mail-archive.com).
Unless Windows Installer supports it, it's unlikely for WiX to support
it. In this case you're limited by the Cabinet API if you want to ship
purely MSI's. Cabinets are either LZX or MSZIP algorithm compression.
If you want to im
Since there were no takers on this one the first time around, let me
simplify the question:
1. How can I override parts of a wixlib included by a Wix extension, or
do I have to rebuild the extension? Specifically, I want to use the
DIFxAppExtension and its difxapp*.wixlib, but I want to modify sev
Hi
I've been using MakeMSI for a while now, and it's great that it uses
LZMA [through http://upx.sourceforge.net/], as it offers an excellent
compressions ratio with a fast decompression.
Can the same be done with WiX? - If so, how?
Please tell me if this can be done
Thank you,
Alec Taylor
--
Hi all,
I have a wix generated installer that I am programmatically tweaking to
add new files.
I am having trouble removing files on uninstalling the modified installer. I
am using Windows installer
One option I have used is to write a .Net 4.0 DTF custom action that allows you
to open the 64 bit registry from a 32 bit CA using
"RegistryKey.OpenBaseKey(RegistryHive.LocalMachine, RegistryView.Registry64)".
No good if .Net 4.0 is not on your target but there are ways to do the same
thing in
You could simply duplicate the RegistrySearch into a second Property & set the
Win64 attribute accordingly on each? E.g.
The 2nd RegistrySearch will give you an ICE80 *warning* for using a 64-bit
RegistrySearch in a 32-bit package which you can suppress (or just ignor
Could you use the upgrade table to detect the product ?
-Original Message-
From: Tobias S [mailto:tobias.s1...@gmail.com]
Sent: 08 December 2010 10:14
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Can RegistrySearch read 64bit hive from 32bitpackage?
Hi,
No doesn't work. The only way is to create a Custom Action which runs
as 64bit CA and does the job for you. But this is not recommended as
heree packages for x86 and x64 would be the best approach. It's just
something to get the job done.
Tobias
2010/12/8 Sharad Patel :
> We are currently
Hi Sharad,
There was already discussion in Wix-users about Registry and 64-32 bit
redirection.
I think it is not supported (documented) scenario by Microsoft
Installer, but you can specify Win64="Yes" as you wrote already, but
also suppress validation of ICE.
It should search in 64 bit branch of r
We are currently using the v3.5 RC build.
We have a 32bit installer that detects AppFabric using the following bit
of WiX code:
This works fine on 32bit systems but we get an error when the installer
is run on x64 systems because AppFabric registry key only exists in th
Thanks for the explanation that makes sense, from this I guess there is no way
to detect that you have scheduled something after an action that is not
included. I'll raise a bug with this text so it is not lost. I guess it could
also happen with any event.
It was fairly easy to detect in the l
33 matches
Mail list logo
