Hi All,
I am using following code for installer creation. This installer does
not detect the existence of previous version of itself. Please help me
if somebody has to share something.
Product Name='!(loc.ApplicationName) $(var.EditionName)
$(var.version)' Id='*'
Hi All,
I am using following code for installer creation. It does not detect
the existence of previous version of itself. Please help me if somebody
has to share something.
Product Name='!(loc.ApplicationName) $(var.EditionName)
$(var.version)' Id='*' UpgradeCode='$(var.Upgradecode)'
Hi users
I have created a Custom Action to invoke a .exe
CreateWBCustomLog.exe.(This exe will create Event Log folder while
installation)
CustomAction Id=CreateCustomLogs
Directory='TARGETDIR'
ExeCommand='[MyInstallationRootPath]\CreateWBCustomLog.exe'
Return='check'
Am 03.04.2010 15:23, Bob Arnson wrote:
No, MSI doesn't offer that feature.
thanks Bob
Alex
--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively,
As usual, forgive me for shameless advertising.
dotNetInstaller 1.9 was released today, April 5th, 2010. Here're some
highlights.
Features include support for windows patch installers (.msp), many improvements
to uninstall support, improved registry checks and registry variable
substitutions,
I added another request: I got a report that the bug occurs most often
on Virtual PC virtual machines and it seems to be a common issue on
various blogs.
On 4/4/2010 2:50 PM, Bob Arnson wrote:
Please see http://www.joyofsetup.com/2010/04/04/bug-hunting/ for
details how you can help track
Good Morning!
I found the error.
In the path do file.pcp there was space and special character.
Path - C:\Dev\usr\carolina.amaral\Patch -PatchCreation\Patch\Patch.pcp
Thanks,
Carolina Zuqueto.
-Original Message-
From: Wilson, Phil [mailto:phil.wil...@invensys.com]
Sent: quinta-feira,
Yes, and this is what my project file has:
ItemGroup
BootstrapperFile Include=Microsoft.Windows.Installer.3.1
ProductNameWindows Installer 3.1/ProductName
/BootstrapperFile
BootstrapperFile
Hi,
When I run this commond:
candle.exe -dVersion=1.1
C:\Dev\usr\carolina.amaral\PatchCreation\Product\Product\Product.wxs -out
C:\Dev\usr\carolina.amaral\PatchCreation\1.1\Product.wixobj
The following error occurs:
error CNDL0200 : The Component element contains an unhandled extension
I have tracked down what's going on using Process Monitor. MsiExec is
shooting itself in the foot using RunOnce. Here's what happens ...
MsiExec creates a folder with a random 7-digit decimal number name ...
C:\Windows\WinSxS\InstallTemp\5755208
... adds a registry entry ...
Hi Sanjay,
Do you have RemoveExistingProducts scheduled?
Alex
-Original Message-
From: Sanjay Rao [mailto:s...@noida.interrasystems.com]
Sent: Monday, April 05, 2010 12:06 AM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] version upgrade problem
Hi
so you are saying
you did the following
Component Id=WebConfig Guid={4B1930CE-1331-4754-855E-77A5FAFFE18B}
Directory=INSTALLLOCATION
CreateFolder/
File/File --- YOU added this like that?
util:XmlConfig Id=WEBCONFIG_section
File=[NETFRAMEWORK40FULLINSTALLROOTDIR]config\web.config
so you are saying
you did the following
Component Id=WebConfig Guid={4B1930CE-1331-4754-855E-77A5FAFFE18B}
Directory=INSTALLLOCATION
CreateFolder/
File/File --- YOU added this like that?
util:XmlConfig Id=WEBCONFIG_section
File=[NETFRAMEWORK40FULLINSTALLROOTDIR]config\web.config
Hi Everyone,
I'm a newbie here, so thank you all in advance for your patience and
understanding. I'm investigating whether or not I want to use WiX to build my
setup/deployment project for my application. I have read through the tutorial
and explored the WiX sourceforge site already, but now
Hi everyone,
I posted the following question originally at Stack Overflow (here:
http://tinyurl.com/yb6n9qb) and it was suggested I bring it up here:
We are on the eve of product launch, and at the last minute I am being
bombarded with crash reports that appear to be related to our
Hi:
I have got this error when I was trying to compile my WiX Project. I looked
for solution online, but none of which seems to fix my problem.
Here is a snippet of the custom action
?xml version=1.0 encoding=UTF-8?
Wix xmlns=http://schemas.microsoft.com/wix/2006/wi;
In my case, I had to deal with two different locations of the bootstrapper
files. This is what works for us.
Just make sure that you have the bootstrapper files in the correct directory
(C:\Program Files\Microsoft SDKs\Windows\v6.0A\Bootstrapper for example).
There is a packages directory
Hi John
As you indicated the wxs file is not known until build time :( I've
managed to solve the problem with a touch of code generation though. I
moved all the wxs and wxi files into the solution but I don't
reference them anywhere (thus they won't be included in the final
msi). In order to
Hi All
One of the registry keys for our product consists of an XML string.
I've been trying to find out how to add this string to our WiX
installer but I haven't been very successful. I've noticed that CDATA
sections are not allowed and obviously normal XML isn't allowed
either. Unfortunately
19 matches
Mail list logo