From the MSI SDK "SQL Syntax":
The Windows Installer* SQL syntax does not support the escaping of
single-quotes (ASCII value 39) in a string literal*. However, you can fetch
or create the record, set the field with the *StringData* or
*IntegerData*property, and then call the
*Modify* method. Alter
The value must be evaluating to blank because it would be failing if the
variable was not defined at all.
On Tue, Jun 8, 2010 at 3:22 PM, Adam Langley wrote:
> Argh!
>
> We had a fully functional build server (TFS 2008), creating our installers,
> then on Friday the builds just started turning r
WiX v2.0 source code is on CodePlex in the wix20 branch. The WiX 2.0 MSI is
at http://wix.codeplex.com/releases/view/44406, Look at the right.
On Tue, Jun 8, 2010 at 5:30 PM, Pratapa Reddy Sanaga <
pratap.san...@gmail.com> wrote:
> Hi,
>
> I'm trying to download the source code for Wix V2.0, but
I'll repeat it again, in case it got missed earlier.
I'd recommend looking at the output of sxstrace to see why it's not
locating the assemblies you expect. That should be enlightening. I'd
expect it to tell you exactly where it looked and why it didn't find what
it was looking for (including
Hi,
I was trying to launch a browser and I’ve used these codes:
Not
Installed
But it doesn’t do anything. It can find default browser but nothing
happened.
I didn’t find anything like error in log file. Can anyone give me a hint
to figure out what is wron
Hi,
I'm trying to download the source code for Wix V2.0, but I'm getting
redirected from http://wix.sourceforge.net/downloadv2.html to this link for
V3.0 download - http://wix.codeplex.com/. Can someone give me a pointer to
V2.0 pointer?
Thanks,
Pratap.
--
Vote for loksatta = vote for a bette
It's really a bit worse than that! What's in the manifest in the program is
useful, but if there's a policy manifest in WinSxS that redirects it, beware of
that. I believe that the VC Redists will install policy manifests that redirect
callers up to the latest. If you install using merge modules
Argh!
We had a fully functional build server (TFS 2008), creating our installers,
then on Friday the builds just started turning red.
The problem seems to be, we pass variables to candle, which defines the root
folder for all content file locations:
e.g. (truncated)
C:\Program Files\Windows Ins
I think this:
Installed AND
Preselected
fixed my problem, but I'm still curious about how MaintenanceWelcomeDlg is
included. Anyone know?
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-to-schedule-MaintenanceWelcomeDlg-tp5155582p51557
We've found that if we've already installed our MSI, but then try to install
it again (from the command line) and supply the ADDLOCAL property, it takes
us to the ResumeDlg (this seems to happen for any MSI using a WiX dialog
set). What we really want is for it to take us to the MaintenanceWelcome
Hi,
I am trying to execute the following SQL statement on my msi database:
cscript WiRunSQL.vbs
MySetup.msi
"UPDATE `ActionText` SET `ActionText`.`Description` ='Configuration de
[ProductName]... L'opération peut prendre plusieurs minutes.' WHERE
`ActionText`.`Description`= 'Configuring [Prod
I am using the new Wix patching process to create my MSPs. I am having trouble
with my patches working on multiple instances of my product. The patch
complains that the product is not installed. Using the patchwiz process
patching multiple instances worked. The patch runs against the default in
Did you include a reference to the IIS Extension lib? You may also need to use
a before you can use these properties.
--
John M. Cooper
-Original Message-
From: Andres Juarez [mailto:andresj_...@hotmail.com]
Sent: Tuesday, June 08, 2010 11:30 AM
To: wix-users@lists.sourceforge.net
Subj
Hi All,
By searching in this list, it seems that the best way of gettign the IIS
version is by using:IISMAJORVERSION and IISMINORVERSION.
I am conditioning the installation of a component upon having IIS7.5 installed
by using the below:
But when I run it
I think you need to run msiexec and get a log file, that should show you
what the problem is.
Neil
-Original Message-
From: MaheshGuru Pawar [mailto:maheshgu...@hotmail.com]
Sent: 08 June 2010 18:02
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Creating a scheduled task us
I would only add dependencies in the manifest for immediate dependencies only .
Don't add dependencies for B to A. For the mixed mode C++ dlls, they'l
depend on their .NET assemblies they consume along with the version of the
C/C++ runtime that their flavor of Visual Studio depends on.
For
If you have a recent version from http://www.dependencywalker.com (at least
version 2.2, I think) it handles SxS.
Phil Wilson
-Original Message-
From: Christopher Painter [mailto:chr...@deploymentengineering.com]
Sent: Tuesday, June 08, 2010 5:17 AM
To: General discussion for Windo
Hey Neil,
I did try what you told but no luck so far. These are my
changes as per ur advice
Please tell if this is alright.
I also added
May be there is a problem in my execute sequence. I tried InstallFinalize but
it gives error.
NOTInstalled
Instal
Ugh. I uninstalled/reinstalled wix 30 and still same problem. I eventually
figured out that I had to do a "devenv /resetskippkgs" at the command line,
and it all works again now.
Thanks for your help everyone!
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2
It sort of is defined because it is child or TARGETDIR (usually) and
that defaults to the ROOTDIR which is the drive with the most space.
Rob blogged a bit about this:
http://robmensching.com/blog/posts/2010/1/26/StackOverflow-what-does-Nam
eSourceDir-refer-to
Neil
-Original Message-
Fro
I am attempting to build a project which contains a couple of rtf files
outside the msi. I have built a small Project.wxs that displays the issue.
In the project I have two components, each with a single file. One is
embedded, the other may not be. When the Package is set to Compressed="yes"
the e
That worked. It feels like using an un-defined variable, but... ok. :)
A
On Mon, Jun 7, 2010 at 7:20 PM, Rob Mensching wrote:
> Don't put anything in the Property table. If you're always going to pass it
> in, you don't need it in the Property table.
>
> On Mon, Jun 7, 2010 at 5:49 PM, Andrew H
Personally I use XP 32-bit with SP3 & all "high priority" updates from Windows
Update as the baseline (no .NET of any flavour even though our app requires
Framework 2.0) for my own & my QA teams virtual machines (same for XP 64-bit
with SP2, Vista x64 with SP2 & Windows 7 x64). I figure if you c
I agree with you. I worked here before some 5 years ago and I had a huge
battle with a coworker where he wanted to use the sxs\system32 msm's provided
my Microsoft and I wanted to add the vcredist packages to our bootstrapper. I
finally relented because I was sick of fighting and they have be
I asked this on this list because I know the WiX community has a lot of members
who are strong in the ways of C++. I'm afraid that if I asked in another group
or StackOverflow type site I'll get answers of low quality since most
developers (sadly) don't take deployment serious. I think the qua
Windows Installer limitation
http://msdn.microsoft.com/en-us/library/aa370859%28v=VS.85%29.aspx
-Original Message-
From: Thomas Mathis [mailto:t...@bica.ch]
Sent: 08 June 2010 14:07
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] error CNDL0242
hello together,
Does anyone k
I assume you've installed both crt redist EXE's from 8 and 9. That is the only
"correct" way of deploying these.
Generally two runtime dependencies is a crapshoot. There's magical code in the
CRT that deals (unsuccessfully) with this kinds of scenarios and depending in
which order they load it
Hi,
I've noticed this exact thing with the C++ runtimes in dependency
walker, I just assumed that it was slightly wrong as the application worked.
It can find direct dependencies in WinSxS but not dependencies of dependiencies.
Dave
-Original Message-
From: Christopher Painter [
hello together,
Does anyone know anything about this error?
...\Setup.wxs(6) : error CNDL0242 : Invalid product version
'1...'. Product version must have a major version less than 256,
a minor version less than 256, and a build version less than 65536.
I have to build a msi package
Hmm, think I just stumbled into the depends / winsxs that you are talking
about. I noticed that I had depends 2.1 so I upgraded to 2.2 and suddenly the
findings were different.
For 2.1, when I loaded B.dll it resolved everything. Now in 2.2 it finds
MSVCR80.dll and MSVCP80.dll but then says M
As I suspected, I brought up a clean machine and put the vcredist_x86.exe on
it. I then had the same behavior where loading B.DLL in depends resolved the
sxs dll's but loading A.DLL which then loaded B.DLL failed to resolve the sxs
dll's unless I created a manifest for A.dll telling it that it
Hmmm, I've not experienced depends / sxs issues in the past so I love to fill
in the knowledge gap possibly exposed by that question. And no, all my CA's
are written in C# using DTF.
I'm told the application is broken. I did create a manifest for A.DLL telling
it had dependencies of the ve
You can't do it in Windows Installer so you can't do it with WiX. WiX
only makes Windows Installer packages (MSI's & MSP's), it's not some
magical voodoo that allows you to do stuff you're not supposed to be
able to for very good reasons.
Use a bootstrapper to chain the .NET Framework 3.5 installe
As far as I can see, the standard texts are all marked with
Overridable="yes" attribute. If you override a particular string, you
usually omit this attribute, and your value will replace the one defined
in the standard extension.
By the way, I just noticed you say "we reference ... and
WixUI_en-us
Maybe, just uninstall WiX toolset and install it back? It must be quick and
clean...
-- Yan
-Original Message-
From: Michael He [mailto:michael...@gmail.com]
Sent: Tuesday, 08 June, 2010 10:08
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] I broke my
I don't think gapearce can create a new wixproj since it sees that the
wixproj is no longer registered with VS2008.
Try to use the VSPackage Load Failure Analyzer
(http://msdn.microsoft.com/en-us/library/bb491684.aspx) to analysis
the problem.
Thanks,
Michael
On Tue, Jun 8, 2010 at 2:42 PM, Neil
36 matches
Mail list logo
