My application will wind up shipping with a ton of loose resource files on
disk*. We will have several items with the following well-defined structure:
MyFile1.foo
MyFile1_files
\ 0
\ somefile.txt
\ 1
\ somefile.txt
...
\ 9
\ somefile.txt
This is how the files live
Thanks Rob, I'll take a look at 3.
Sorry to go on about it but why would making -fv the default be a problem? If
you are doing the right thing then it wouldn't matter as the versions would
match and if you need it the assembly will be installed using the normal
versioning rules. I must be
Neil
Have you considered using a variant of Heat to generate the WiX code
dynamically? I have done this sort of think in v2 using a tool called mallow
(it is a variant of tallow) I think you should find it on the web if you search
but if not let me know and I send you a copy. It can scan a
Hi John,
Thank you for the idea!
Out of total curiosity though, if the user is upgrading to the application
that shouldn't contain the JRE, why does the JRE need to hang around?
(Especially since, if you uninstall the installation w/JRE through ARP you
expect the JRE to be uninstalled?)
The thing that seems obvious is that it is probably using .Net 3.0 or 3.5 as
the upgrade wizard will select these for you. Check the target framework
version as you might not have it on the system you are installing to.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
You're supposed to use publisher (publishing?) assemblies to accomplish what
you're doing.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Neil Sleightholm
Sent: Friday, July 11, 2008 00:22
To: General discussion for Windows Installer XML toolset.;
Ryan O'Neill wrote:
The thing that seems obvious is that it is probably using .Net 3.0 or 3.5 as
the upgrade wizard will select these for you. Check the target framework
version as you might not have it on the system you are installing to.
Also make sure you're compiling with the static
There is a HeatTask provided by the WiX toolset already. Getting the GUIDs
right is the hardest part of autogenerating .wxs files. The Windows
Installer is brutally unforgiving for messing up your Component/@Guids.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
The project is a driver that supports x86 and amd64 platforms.
Do I need to create new wxs-file with its own unique GUIDs for Product Id,
Product UpgradeCode and Component GUID, or can I use the same wxs-file
for all platforms?
In the latter case msi-packages will be different by Package Id
I am already using publisher policy files but they don't work in a daily build
environment. We have publisher files for going from v1.00 to v1.01 etc but they
don't make it easy to update daily builds or fix live releases with hotfixes.
They are also limited in the range of versions they will
Here is a recent blog that has links to some previous blogs ( including mine )
on this topic.
http://blog.genom-e.com/PermaLink,guid,8044083d-8153-4046-8601-ec3556f7adaf.aspx
Christopher Painter, Author of Deployment Engineering Blog
Have a hot tip, know a secret or read a really good thread
I'd also consider using DTF if you can, instead of your own custom
wrappers. It handles all the grunt work for you.
Chris
On Fri, Jul 11, 2008 at 4:46 AM, Markus Ewald [EMAIL PROTECTED] wrote:
Ryan O'Neill wrote:
The thing that seems obvious is that it is probably using .Net 3.0 or 3.5
as
Hi,
I am new to WIX (and Votive of course). I am trying to install WIX3
(Wix-3.0.2925.0.msi from Sourceforge), but every time I do the installer
tells me that Votive, the WiX project and editor package for Visual Studio,
cannot be installed because Visual Studio Standard Edition or higher is not
You may want to look at Paraffin
(http://www.wintellect.com/CS/blogs/jrobbins/archive/2007/10/21/wix-a-better-tallow-paraffin.aspx).
This tool was designed for WiX 2.0, so you have to WiXCop the resulting file
if you use WiX 3.0. Paraffin handles much of the GUID generation and updating
for
Hi Mohith,
You can grab the latest build of Wix v3 from the following location (2925 is
a little old):
http://wix.sourceforge.net/releases/
The sourceforge list of releases is not currently update - though this
should be changing soon!!
2008/7/11 Mohith Manoj [EMAIL PROTECTED]:
Hi,
I am
Howdy.
After using candle and light to create my english msi, I am creating
transforms for 8 foreign languages with msitan.exe.
This works fine for non-asian languages. Asian languages have mst's with all
characters being question marks...
Poking around, I've found many threads about msi 3 not
Thanks for all the suggestions everyone, lots for me to go and look at.
Neil
From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Jason Swager [EMAIL
PROTECTED]
Sent: Friday, July 11, 2008 6:05 AM
To: General discussion for Windows Installer XML toolset.
Rob,
Any pointers on tips for getting the GUIDs right? Will HeatTask take care of
this for me? If not, what rules do I need to follow?
Neil
From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Rob Mensching [EMAIL
PROTECTED]
Sent: Friday, July 11, 2008 1:48
Rob,
Any pointers on tips for getting the GUIDs right? Will HeatTask take care of
this for me? If not, what rules do I need to follow?
If I understand how Windows Installer works (which may or may not be
the case) ... if you never intend to do patches or minor upgrades you
can always
Hi,
Below I have written the code but I am getting the error if anyone knows
please let me know
Error 4 The Component element contains an unhandled extension element
'WebSite'. Please ensure that the extension for elements in the
'http://schemas.microsoft.com/wix/IIsExtension'
In this case, you might want to consider authoring a patch which targets both
product's MSIs? (instead of trying to use a single MSI to update [what are
essentially] multiple SKUs)
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Thomas Singer
Sent:
It depends on where RemoveExistingProducts is scheduled. If you schedule it
early enough you can. If you schedule it later, you'll have all sorts of
costing issues because of broken component rules.
Even if you take the MSI issues out of the discussion, dynamic file linking
concerns me
InstallShield applies some business rules to look at previous packages to make
sure there is consistency across builds.
Christopher Painter, Author of Deployment Engineering Blog
Have a hot tip, know a secret or read a really good thread that deserves
attention? E-Mail Me
--- On Fri, 7/11/08,
Thanks for the clarification.
Any idea regarding the other questions?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Brian
Rogers
Sent: Thursday, July 10, 2008 5:16 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] New
WebSite isn't a native MSI thing so it is in an extension. To access an
extension, you must reference it's namespace. You are already doing this for
the UtilExtension, so you need to do the same for the IisExtension. The
WiX.chm talks about how to use extensions in more detail.
Here's some example code (this was WiX v2) for configurable merge modules:
In the merge module (foo.msm) = module GUID =
03A6BA5C-D324-4BB6-9109-35DCAFA943FE:
!-- MODULE INTERFACE PROPERTIES --
Configuration
Hello all.
I have what I guess is a typical installation dialog box sequence...
WelcomeDlg-LicenseAgreementDlg-CollectUserInformationDlg-InstallDirDlg-
How would I skip the CollectUserInformationDlg and go directly from
LicenseAgreementDlg to InstallDirDlg, based on the value of a
*and* if the Components you generate *never* overlap with any other products
(including your own). There are enough caveats in the just use major
upgrades statement that it makes it very hard to say, Oh, sure, just go ahead
and ignore the Component Rules... they don't matter. for every
You need to change the codepage of the MSI as well because MSI files are not
UTF-anything. smile/
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of A. Brooks Hollar
Sent: Friday, July 11, 2008 06:31
To: wix-users@lists.sourceforge.net
Subject: [WiX-users]
Yes, it appears the bug that was preventing many people from upgrading from an
older Votive to newer Votive has been tracked down. Solution isn't available
yet but I expect as soon as that is in, Martin will be pushing a release...
well, that's what he hinted he would probably do... it's his
After looking into this some more, I have discovered that it is the msi's
being built with candle and light that have the missing asian characters...
The locale files we are using display properly and all the files are
specified as UTF-8...
I'm pretty stumpted here. There is a lot of confusing
Again, I agree with you. IMHO, the design of Fusion wasn't well informed about
the harsh reality of the real world.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Neil Sleightholm
Sent: Friday, July 11, 2008 04:26
To: General discussion for Windows
Your .wxs files can be UTF-8 but the final MSI does not support it. You need
to provide a Product/@Codepage that handles the character set you are pushing
into it. Otherwise, the MSI will have little square boxes in it.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL
Answering the questions backwards:
1. The rules are called the Component Rules. They are documented in the MSI
SDK and I added a bunch of color commentary here:
http://blogs.msdn.com/robmen/archive/2003/10/18/56497.aspx
2. It appears that HeatTask does have the support the heat
You might take a look at the setup for the WiX toolset. We build 32-bit and
64-bit from one set of source code so it might be instructive.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
?
Sent: Friday, July 11, 2008 03:42
To:
Thanks Rob. I'm currently exploring another approach, although if I wind up
going the HeatTask route I'll keep all the below in mind.
Neil
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rob Mensching
Sent: Friday, July 11, 2008 9:01 AM
To: General
Hey Amir,
I believe you will need to run that as a deferred action in order to access
the file system.
--
Brian Rogers
Intelligence removes complexity. - Me
http://www.codeplex.com/wixml/
On Fri, Jul 11, 2008 at 7:56 AM, Amir Kolsky [EMAIL PROTECTED]
wrote:
Thanks for the clarification.
Any
I'm messing around with trying to get my installer's ProductVersion to be based
off our main application's assemblyVersion. I thought this would be as simple
as putting !(bind.assemblyVersion.MyApplicationId) in the right places, but
this doesn't work unless I put Assembly=.net on my main
Thanks!
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Christopher
Painter
Sent: Friday, July 11, 2008 9:44 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Why do binder variables require GAC installation?
And one day (probably not in WiX v3 at this point) we'll try to get those
variables for any assembly, not just the ones going to the GAC.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Neil Enns
Sent: Friday, July 11, 2008 09:46
To: [EMAIL PROTECTED];
We want to only offer all-in-one (with and without the JRE) packages, no
patches which *require* a previous installation.
Tom
John Nannenga wrote:
In this case, you might want to consider authoring a patch which targets both
product's MSIs? (instead of trying to use a single MSI to update
OK, I'm trying to build a Wix extension to handle some tasks for me. First
I tried basing mine off of the code in SqlExtension from the Wix source, but
that did not work at all.
Then I tried the dumbest simple sample:
3. You should be able to get the behavior you want by manually adding
the AssemblyName element and refer to the !(wix. FileVersion.FileId).
Do you have any pointers to samples to get me started?
Neil
-
Sponsored by:
Do you have a compiler class specified? It is going to be a bit difficult to
troubleshoot this without some additional information. Have you also
specified an XSD? Are you adding the project to the CVS checkout or are you
building as a stand-alone?
--
Brian Rogers
Intelligence removes complexity.
Christopher,
Last night in my aborted attempt to automate including files in my installer, I
got a basic extension up and running and working. If you can wait, I can zip it
up and send it to you tonight as a starting point.
Neil
-Original Message-
From: [EMAIL PROTECTED]
In my simplistic test extension, I do not have a compiler, decompiler, or
even source code for that matter.
I will now include my extension in it's entirety:
--
using System;
using System.Collections.Generic;
using System.Text;
using
That would be excellent. I can't really wait, but I fear I will not make
substantial progress today, so it would probably be wonderful to have this
anyway. :-)
Chris
On Fri, Jul 11, 2008 at 1:17 PM, Neil Enns [EMAIL PROTECTED] wrote:
Christopher,
Last night in my aborted attempt to
It's a repair of some kind, or an install of missing components. The event log
(I forget which) will have MsiInstaller entries naming the component that
triggered the repair.
Phil Wilson
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of andywhitt
Sent:
For what it's worth I got going simply by duplicating what the WixUtilExtension
does. Similar to your SqlExtension approach I think. I trimmed it down to just
implementing a stub compiler object and extension object.
My biggest problem was figuring out the appropriate string to pass in to load
Yeah, I tried doing that, and it compiled fine, I just got this loading
error every single time, so I figured I was messing something up in my
complication.
But, even my simple one seems to fail, and I don't understand it. The
assembly is valid, I can look at it in .NET Reflector, and it has all
What error is it throwing? I read back through the thread but couldn't
find the wording of the error it is throwing. I think that based off of
this latest code below it would be trying to find the xmlconfig.bat in
the same location as CMD.EXE, rather than in the root of C:\. If that's
the case it
Thanks for your reply..
Can you please let me know how to run Batch files directly without
command prompt.
Thanks..
Regards,
SivaKrishna Kalvagadda,
201-671-5552.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Chad
Petersen
Sent: Friday, July 11,
In Explorer you can simply double-click on the batch file. Or go to
Start | Run and type in the full path to the batch file. Or, from within
WiX code, ExeCommand=C:\xmlconfig.bat. Like I say, you don't have to
explicitly open a CMD prompt to run a Batch file, a CMD process will
automatically spawn
Well, it should be able to load, since the methods exist in WixExtension, I
just didn't override any of them to do actual work. Good thought though.
I'm setting up to debug through Candle now so I can find where the issue is.
Chris
On Fri, Jul 11, 2008 at 3:05 PM, Rob Mensching [EMAIL
Apparently, I was having a version issue. It's not reported nicely, but
something, somewhere was mismatched. I downloaded the new source and
binary drop, and bango, everything starts working.
Sheesh. Thanks everyone for the help!
Chris
On Fri, Jul 11, 2008 at 3:11 PM, Christopher Karper
Hi All!
How do I condition a custom action (basically for NOT installed)?
I tried to put it in a fragment but then it stops the uninstall dead.
The level=0 is only accepted inside Features, but this is and install
sequence thing...
This must be trivial, what am I missing?
Thanks,
See the text of the Custom element in the WiX.chm.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Amir Kolsky
Sent: Friday, July 11, 2008 15:03
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Another newbie question: condition on custom action
Are you referring to this?
*Inner Text (xs:string)*
Text node specifies the condition of the action.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Rob
Mensching
Sent: Friday, July 11, 2008 5:04 PM
To: General discussion for Windows Installer XML
I'm trying to use
PropertyRef Id='VS2005_SCHEMAS_DIR'/
PropertyRef Id='VS2005_PROJECTTEMPLATES_DIR'/
PropertyRef Id='VS2005_ITEMTEMPLATES_DIR'/
PropertyRef Id='VS90_SCHEMAS_DIR'/
PropertyRef Id='VS90_PROJECTTEMPLATES_DIR'/
PropertyRef Id='VS90_ITEMTEMPLATES_DIR'/
For
59 matches
Mail list logo
