I've been running a couple of tests with the Windows 7 logo kit, and one
warning that's coming up in the report looks like this:
Test case: Remove all non-shared files and folders.: PASS WITH WARNINGS
WARNING: This application failed to remove the following files during uninstall:
File
.msp' differs in size with the
certificate authored in the package
-Original Message-
From: Chris Bardon [mailto:cbar...@computer-talk.com]
Sent: Thursday, July 02, 2009 5:48 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Patching a product without
I've been experimenting with creating msp files for all updates, and I've run
into a strange problem. I read about having to create uncompressed cabs for a
patch, so I created two different installers that upgrade a single text file,
and actually managed to create the msp file, but then I
My goal for getting patching to work is to be able to deploy an application
that can be patched by a non-admin user, but I'm running into a problem. I've
created the patching sample in the documentation, and the patch works when it's
elevated, but whether or not it's signed, the patch is still
I did run signtool against the packages, with the command lines in the first
part of the post.
I also forgot to point out a couple of other changes to the demo code. I
changed the installer version to 300, and I set ALLUSERS to 1 to make sure that
I installed per-machine to start with.
file
'C:\Users\STANDA~1\AppData\Local\Temp\13f7987.msp' differs in size with the
certificate authored in the package
How did you generate your .cer?
- Rafael
Chris Bardon wrote:
I did run signtool against the packages, with the command lines in the first
part of the post.
I also forgot
that was actually being executed. Ultimately, I don't
think this change did anything.
-Original Message-
From: Chris Bardon [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 13, 2008 12:43
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Certificate install to local
, November 04, 2008 2:01 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Certificate install tolocal
machinefailswithcode 26352
Yes, but I didn't make the 4624 build. If you look in CVS then you'll
see the change.
-Original Message-
From: Chris Bardon
I checked out the latest weekly build, and it looks like the problem is
still there. The source for the build is also identical to what was
there before-Rob, did you change anything?
-Original Message-
From: Chris Bardon [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 21, 2008 1:13
I just tried upgrading to build 3.0.4624.0 from 3.0.4014.0, and I
noticed that my setup projects won't build anymore. VS 2005 compains
about the wix.targets file. The compiler reports back that 'The target
link does not exist in the project in the error list, but there don't
appear to be any
-platfor
m-configurations.aspx
On Mon, Nov 3, 2008 at 3:37 PM, Chris Bardon [EMAIL PROTECTED]
wrote:
I just tried upgrading to build 3.0.4624.0 from 3.0.4014.0, and I
noticed that my setup projects won't build anymore. VS 2005 compains
about the wix.targets file. The compiler reports back
have more information about that error?
-Jason-
-Original Message-
From: Chris Bardon [mailto:[EMAIL PROTECTED]
Sent: Monday, November 03, 2008 6:51 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] wix.targets problem in latest weekly build
Right, I
?
-Original Message-
From: Chris Bardon [mailto:[EMAIL PROTECTED]
Sent: Monday, October 20, 2008 1:53 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Certificate install to local machine fails
withcode 26352
I've dug a little deeper into this, written some test
26352
Wow, nice analysis. Is there a bug open on this issue right now? If
not, can you open one and I'll try to get this change in Thursday night
for Friday's build.
-Original Message-
From: Chris Bardon [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 21, 2008 07:47
To: General discussion
the old one?
Any experts in the crypto API here? If not, does anyone have any
thoughts on where else I could look for answers?
-Original Message-
From: Chris Bardon [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 14, 2008 2:51 PM
To: General discussion for Windows Installer XML toolset
:
if (!::CertAddCertificateContextToStore(hStore, pCertContext,
CERT_STORE_ADD_REPLACE_EXISTING, NULL))
{
MessageExitOnLastError(hr, msierrCERTFailedAdd, Failed to add
certificate to the store.);
}
Seems like it *should* replace the certificate if possible.
-Original Message-
From: Chris Bardon [mailto:[EMAIL
26352
I doubt overwrite will help. Can you get a log file from a failure?
That will go a long way to diagnosing the problem.
-Original Message-
From: Chris Bardon [mailto:[EMAIL PROTECTED]
Sent: Friday, September 26, 2008 07:22
To: General discussion for Windows Installer XML toolset.
Subject
I've had some users complain about a problem with an installer that
attempts to add a certificate to the trusted root cert store. I added a
component to my setup that looks like this:
Component Id=RootCA Guid=A1106EC4-9546-4a4f-AE6D-4F94DE066C0E
Permanent=yes
ConditionCERTPATH/Condition
I've built my own auto update mechanism to recognize when new versions
are available based on a web service, but I'm curious to know what
solutions others have come up with. Basically, my app just phones home
to a predefined location on startup, and if there's a new version,
downloads and runs
I'm trying to push out a root CA cert in Wix v3 for an app that needs to
form TLS connections. I found the iis:certificate element, so I'm
trying to define a feature that looks like this:
Component Id=RootCA
Guid=EFA9E69C-32E5-4e54-AF4E-9166902E1F9B Permanent=yes
You're right-a relative path will work if you hand edit the wixproj, but
the UI will still show the absolute path. Thanks for the help.
From: Justin Rockwood [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 29, 2008 2:47 PM
To: Chris Bardon; WiX Users
Subject: RE: [WiX-users] Votive
Does anyone know if there's a way to have an installer create a shortcut
on Vista that always runs as an administrator? I have a legacy app that
needs to create ODBC DSNs on startup, which doesn't appear to work if
it's running in a non-elevated context.
Thanks,
Chris
-
From: Justin Rockwood [mailto:[EMAIL PROTECTED]
Sent: Friday, December 07, 2007 3:45 PM
To: Chris Bardon; WiX Users
Subject: RE: [WiX-users] Votive on VS 2008?
Yes, it works side by side just fine (or at least it's supposed to :-).
You
should see an option on whether you want to install
] On Behalf Of
Richard
Sent: Thursday, December 06, 2007 7:24 PM
To: Chris Bardon
Subject: Re: [WiX-users] Votive on VS 2008?
In article
[EMAIL PROTECTED]
,
Chris Bardon [EMAIL PROTECTED] writes:
I'm using 3.0. [...]
On Rob Mensching's blog, he stated that the community technology
preview
.
-Original Message-
From: Justin Rockwood [mailto:[EMAIL PROTECTED]
Sent: Friday, December 07, 2007 3:02 PM
To: Chris Bardon; WiX Users
Subject: RE: [WiX-users] Votive on VS 2008?
Have you picked up the most recent version on
http://wix.sourceforge.net/releases (Votive 3, not 2)? Aaron has already
Just out of curiosity, has anyone done a rebuild for the Votive plugin
to work with VS 2008? I just installed the RTM this week, and I'm
looking to try moving some of my VS2005 projects up. So far, anything
that includes a setup won't build.
: Thursday, December 06, 2007 12:30 PM
To: WiX Users
Subject: Re: [WiX-users] Votive on VS 2008?
In article
[EMAIL PROTECTED]
,
Chris Bardon [EMAIL PROTECTED] writes:
Just out of curiosity, has anyone done a rebuild for the Votive plugin
to work with VS 2008? I just installed the RTM this week
Ben, I've created an installer for a C# COM addin using Wix, and I ran
into some of the same problems. The best way to get the necessary COM
settings for a registration seems to be to use a registry sniffer that
can compare snapshots. I took a registry snapshot, registered the
assembly, and then
Sorry if this has been covered already, but I couldn't find anything in the
archives. I was looking for a French Translation of WixUI, and found an almost
complete one at http://www.tramontana.co.hu/wix/loc/index.php. The only
problem I ran into is that anything that had an accented character
Does it fail even if you run your setup elevated? If you’re able to run your
MSI non-elevated, it’s probably using the compatibility features to write to a
mirror program files directory under the user profile, not the real one. If
you run your msi, does Windows ask if you want to elevate?
I've been trying to figure out how to install a CA certificate for a
while now without a whole lot of luck. I found the IIS extension
listing for the certificate element, and I've run into a couple of
different errors with it. I've tried inserting this markup:
iis:Certificate Id='CACERT'
Did you set your main feature up with the
ConfigurableDirectory=INSTALLDIR attribute?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of JCWrs
Sent: Thursday, April 12, 2007 1:56 PM
To: [EMAIL PROTECTED]
Subject: [WiX-users] Changing the value of
To: Chris Bardon; [EMAIL PROTECTED]
Subject: RE: [WiX-users] Changing the value of TargetDir?
Is something like this what you mean?
Feature Id='RDPath' Title='ReferenceData' Description='Descrip of
ReferenceDataCAB' Display='expand' Level='1'
ConfigurableDirectory=INSTALLDIR
I'm really at a loss here,
My
Hope this helps!
Julie Campbell
[EMAIL PROTECTED]
(440) 498-3081
-Original Message-
--
Message: 3
Date: Mon, 9 Apr 2007 13:55:59 -0400
From: Chris Bardon [EMAIL PROTECTED]
Subject: [WiX-users] Create MSBuild boostrap event to install Office
PIAs
To: wix
So is it possible to write to these variables as well? I'd like to be
able to pass in a property on the command line (or from a custom action)
that will set the state of the feature tree for a custom install. The
goal is to make it simple for admins to script installations that deploy
components
, 2007 11:41 AM
To: Chris Bardon
Cc: David Roberts; wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Setting a property, conditionally on selection
of a feature in Custom install
Chris Bardon wrote:
So is it possible to write to these variables as well?
No, they're read-only. To mark
Have you checked out the tutorial at
http://www.tramontana.co.hu/wix/lesson2.php? There's a section in there
about UI that uses the stock Mondo set, and that has a feature tree
built in. If you want to tweak it, you can just use the source for the
stock dialog as a basis for a new version.
This should be how a major upgrade works, especially if you position the
removal logic in the right place. I have this in my wxs:
Upgrade Id=9E9EAAF1-4AF9-46D4-89AA-AD26AE05208A
UpgradeVersion OnlyDetect=no Property=PREVIOUSVERSIONFOUND
IncludeMinimum=yes Minimum=1.0.0.0
I was looking at the wiki article here
(http://www.wixwiki.com/index.php?title=Deploying_Additional_Components)
on bootstrapping, and I need to be able to extend the bootstrapper with
my own component for the Office 2003 and 2007 PIAs. I checked out the
tool from gotdotnet to generate the XML,
I've run into a strange problem with a custom action DLL that works just
fine on one system, but not on the clean test system that I've been
working with (a fresh XP install in virtual server). On my dev machine,
and my second not so clean XP machine (has VS installed), the msi
works fine, and
Yeah, I haven't had any luck with Heat either, but the reverse
engineering isn't all that tricky actually. Grab the trial version of
RegSnap from http://lastbit.com/regsnap/ and try unregistering your
control, taking a snapshot, registering, taking a snapshot, and
comparing the two. There'll be
PROTECTED] On Behalf Of Chris
Bardon
Sent: Thursday, March 29, 2007 10:48 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Conditional Install of the Office 2003 PIAs
I have an installer for a product with an optional Office 2003 Addin
that requires the Office 2003 PIAs, and I'm trying
I'm guessing you want to avoid passing the REINSTALLMODE to the
bootstrapper, correct? My solution to the same problem (thanks to the
help of others on this list) was to use * as the product code, and
define every upgrade to be a major one. There is a way to distribute a
bootstrapper with
Try setting the condition to NOT INSTALLED
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Some user
Sent: Friday, March 30, 2007 12:40 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] install uninstall run conditions
I have an MSI where I
I have an installer for a product with an optional Office 2003 Addin
that requires the Office 2003 PIAs, and I'm trying to figure out how I
can install the assemblies only if the component is selected in the
feature tree. A bootstrapper will launch the PIA MSI beforehand,
wouldn't it?
I'm
Yes, it sounds like those warnings are normal for the merge modules and
Wix. The modules seem to work though, so I've just ignored the warning
for now.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Anthony
Wieser
Sent: Thursday, March 29, 2007 12:51
11:48 PM
To: Chris Bardon
Cc: Wilson, Phil; wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Another version of this product is already
installed
Chris Bardon wrote:
-Force all upgrades to be major-Other than performance, is there any
reason that this is a bad idea? Our apps
I have an application that creates some config files that I'd like to
conditionally uninstall with the application. It looks like I can just
use RemoveFile to get rid of these on uninstall, but I'd like to give
the user the option of keeping them in case they reinstall later. I've
seen several
I'm trying to make sure that I have a Wix installer that upgrades
distributions authored with the previous Installshield version we used,
but for some reason not all of the files work correctly. I've defined
my Wix file with the same upgrade code, but with a new product and
package codes, a new
-users] Why isn't my upgrade being detected?
Make sure that the AllUsers value is the same in both products.
Phil Wilson
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Chris
Bardon
Sent: Wednesday, March 28, 2007 9:31 AM
To: wix-users
So far, I've been using the Votive 3.0 build without any problems. I
think the only thing unstable about the build is that there could be
breaking changes in future releases that mean you'll have to change your
code. Other than the environment variable macros (being able to refer
to project
Since it doesn't look like there's any way to refer to properties in a
ScrollableText control (i.e. the [PROPERTY] references won't be
resolved), is there any other way that anyone's figured out to
dynamically generate the contents of one of these controls? I thought
about setting the contents to
And the command line reinstall is where there's a major problem from an
end user perspective. There's no way that I can convince users to run
with a command line, so there needs to be some way to force the msi
engine to run with those parameters. So far, I see a couple of options:
-I'm already
Check out the tutorial here
(http://www.tramontana.co.hu/wix/lesson4.php)
Basically, you can't just run the MSI for small/minor upgrades-you have
to pass in the command line msiexec /i install.msi REINSTALL=ALL
REINSTALLMODE=vomus . Not sure why-can anyone here shed some light on
the subject?
I'm trying to change the dialog sequence conditionally on properties
being passed in on the command line, and I can't find a reference for
what a not equals operator is. I can use PROPERTY= as a condition,
but I tried PROPERTY!= and PROPERTY NOT , but those don't seem to
work. I'm sure there's a
OK, that was it. I knew it was something dumb that I forgot. Didn't
know you could define multiple namespaces for an XML file like that :)
Thanks guys!
From: Simon Dahlbacka [mailto:[EMAIL PROTECTED]
Sent: Monday, March 26, 2007 9:45 AM
To: Chris Bardon
Cc
I'm using the latest 3.0 build from the website. The version of the
WixUtilExtension.dll is 3.0.2420.0.
Sounds like it might be a Votive issue then?
-Original Message-
From: Bob Arnson [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 22, 2007 11:03 AM
To: Chris Bardon
Cc: wix-users
properties to set.
From: Ricardo Lopes [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 20, 2007 11:04 AM
To: Chris Bardon
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Bootstrapping to install .net 2.0-sample and
best practices?
Hi, i use
I'm trying to create a custom DLL that sets an installer property that
the user can then modify, so I tried starting with a simple example:
extern C UINT __stdcall TestFn(MSIHANDLE hInstall)
{
MsiSetProperty(hInstall,TEXT(AGENTID),TEXT(AgentID from
DLL));
return ERROR_SUCCESS;
}
Have you tried something like this:
InstallExecuteSequence
Custom Action=CA2.uninstall.SetProperty
After=MsiUnpublishAssembliesINSTALLED/Custom
/InstallExecuteSequence
This should execute the action only if the product is installed.
From: [EMAIL PROTECTED]
installing, and I was thinking about putting the custom
action before AppSearch. Are there any reasons not to do this?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Chris
Bardon
Sent: Thursday, March 22, 2007 10:52 AM
To: Rob Hamflett; wix-users
I'm working on replacing an existing setup procedure with a Wix
installer, and I think I have almost all of the components I need. The
one thing I'm missing however, is a piece of functionality we have in
Installshield that's pretty important to how our applications are
delivered. We have a
I'm trying to put a final summary dialog in my installer that
reconfirms all the details before completing installation, and I ran
into something interesting when trying to use a ScrollableText control.
If I make a control just text, I can put references to properties (e.g.
[USERID]) in there that
Quick question-is there a way to convert a .reg file to wxs format? I
was able to get a COM exe server's registry changes using a registry
diff tool that generated a .reg file, which I proceeded to convert by
hand to wix markup. Just wondering if there's an easier way to do the
conversion that I
to get everything by using RegSnap to take a snapshot of the
registry, run server.exe /regserver, take a new snapshot, and check
the diffs.
-Original Message-
From: Stefan Pavlik [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 20, 2007 9:01 AM
To: Chris Bardon
Cc: wix-users
I have some applications that depend on .net 2.0 being installed, and I
have an idea of how I'd like to have things work. A setup file,
deployed from an intranet site will check for the prerequisites, and
then once they are installed/verified, download and run my MSI with the
command line
I tried making some XML file changes in a Votive project, and as
expected got Error CNDL0005: The Component element contains an
unexpected child element 'XmlFile'.. For the UI wixlib, I had to
reference a DLL in the votive install directory-is there another DLL
that I can reference for the XML
directory,
shouldn't it?
From: Rob Mensching [mailto:[EMAIL PROTECTED]
Sent: Monday, March 19, 2007 8:44 AM
To: Mike Dimmick; Chris Bardon; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Consensus about CRT/MCF merge modules?
Agreed. However, based
Looking through the archives, there appear to be a couple of ways to
include things like the CRT and MFC redistributables in an installer.
Some have advocated including the DLLs directly, which seems to go
against the concept of having a redistributable MSM to link against. I
tried building with
On to an upgrade question-I have an installer that just installs a
single EXE right now, and I'd like to be able to create an upgrade path
for it. The trick is, I'd like to be able to have a package that will
upgrade within the same file version. If I change only the package code
(small
From: Justin Rockwood [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 13, 2007 4:04 PM
To: Chris Bardon; Ashman, Jared; Levi Wilson; Simon Dahlbacka
Cc: wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Votive v3 and UI
Good points. I don't necessarily like defaulting to en-US
I've been going through the tuorial at http://www.tramontana.co.hu/wix/
and adapting to some of the v3 changes as I go, and I've run across a
problem with adding UI elements. If I put in the UIRef elements UIRef
Id=WixUI_Mondo / and UIRef Id=WixUI_ErrorProgressText / I get an
unresolved symbol
my own UI lib based off of
Mondo, but I'd like to be able to customize it with different graphics
when referenced in different setups.
From: Levi Wilson [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 13, 2007 11:50 AM
To: Chris Bardon
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX
[mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 13, 2007 12:35 PM
To: Simon Dahlbacka
Cc: Chris Bardon; wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Votive v3 and UI
Maybe that's what it was...that it was TOO easy :-) I usually miss
those.
On 3/13/07, Simon Dahlbacka [EMAIL PROTECTED
questions).
Chris
From: Ashman, Jared [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 13, 2007 1:28 PM
To: Chris Bardon; Levi Wilson; Simon Dahlbacka
Cc: wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Votive v3 and UI
Chris,
If you add the en-US to the field, then open
?
Chris Bardon
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Patrick
Schmid
Sent: Sunday, February 25, 2007 7:31 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] wix for Office 2007 .net 2.0 shared add-in
I would like to use wix2 or wix3
Hi all, I'm just getting started with Wix, and I started working through
the tutorial (at http://www.tramontana.co.hu/wix) and trying out the
system. I grabbed the Votive v2 install as well, since we use VS quite
extensively, and I want something for setup that will integrate with the
existing
I decided to try out Votive v3 to see if it fixed the problem I was
having with v2 and building an installer with a UI, and I found that as
soon as I imported my wxs file into the new project, I got errors on the
environment variables (e.g. src=$(var.testDLL1.TargetPath)) saying
that the symbols
78 matches
Mail list logo
