It is a waste and no one seems to have an answer that works well. One
question, why do you need to put the file in two places? If it's in the GAC
everyone can get to it, right? Why double place it?
_
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Darren Green
Sent:
Just author a Directory element below the INSTALLDIR directory element whose
Id is not in uppercase.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Chris
Sutcliffe
Sent: Saturday, June 03, 2006 9:08 AM
To: wix-users@lists.sourceforge.net
Subject:
Possibly. If your install ever ends up on a short name system (and you
don't have complete control over that) then you're going to be seriously
hosed.
_
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Simon Burgess
Sent: Monday, June 05, 2006 1:49 PM
To:
?define? is a preprocessor directive. It doesn't get evaluated at run
time. I think you want the Condition element.
_
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Kalappa Pattar
Sent: Monday, June 05, 2006 10:29 AM
To: Brian Simoneau;
The PID_REVNUMBER thing
sounds like a bug in dark.
If you have a valid
MSI/MSM file I do expect dark.exe to be able to decompile it. However, candle
appears to be far more exact about what it allows one to put into an MSI/MSM
than some of the other authoring tools out there (I know this
More generally Components are small and Features are things users can
turn on and off. So, typically a Feature contains many Components.
Also, Components install everything to a single directory. So if you need
to install to different Directories you need different Components.
Does that help?
FYI, WiX v3 has an called
CloseApplications that does just that.
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Watkins, Jon
Sent: Friday, June 16, 2006 6:42
AM
To: '???';
wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Uninstall
a system tray program
Title: [WiX-users] wix3: history.txt
I'll see what I can
do.
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Frederik Carlier
Sent: Monday, June 19, 2006 1:29
AM
To: Thomas Hecker;
wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] wix3:
history.txt
I recently had some people ask me if it would be okay for them to send out
job requests to this mailing list. I thought about it and I was conflicted.
On one hand, this is place to talk about the WiX toolset, how to use it, and
how to improve it. Job postings don't belong here. On the other
On 6/20/06, Rob Mensching [EMAIL PROTECTED] wrote:
I recently had some people ask me if it would be okay for them to send out
job requests to this mailing list. I thought about it and I was
conflicted.
On one hand, this is place to talk about the WiX toolset, how to use it,
and
how to improve
sigh/
Believe it or not,
this is my fault. LocalCache is failing on your machine. I wrote
the LocalCache feature for Office 2003. There were two or three subtle
bugs that didn't show up until some serious patches were sent out. You
can read about it more here:
Read about the ALLUSERS
Property.
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Don Tasanasanta
Sent: Friday, June 23, 2006 11:59
AM
To:
wix-users@lists.sourceforge.net
Subject: [WiX-users] using HKMU
registry attribute
From what Ive read the Root=HKMU
1. RemoveFolder shouldn't be necessary. Usually the reason directories are
left behind some files were left.
2. The problem with your registry keys is that you're saying to create the
parent key but never to delete it. Instead of defining two Registry
entries, try just using one to define
All Directory elements must be rooted in TARGETDIR/SourceDir.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: Monday, June 26, 2006 12:05 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Registry element causes error
What is that key for?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of jdrake
Sent: Thursday, June 29, 2006 8:56 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] pca:ComPlusAssembly DLL Registration
Maybe I am reading something very wrong
Documentation is lacking in WiX v3 for this kind of stuff. Extensions are
much easier to use in WiX v3. Just use -ext WixUtilExtension. None of
that other stuff is necessary any more. Feel free to open a bug to fix up
the light -? documentation and WiX.chm.
-Original Message-
From:
You can't rerun *only* the CustomAction without Conditionalizing practically
everything in the sequence tables. I wouldn't recommend doing that.
Instead, I'd suggest just using Maintenance Mode UI to allow the user to
change the values and set the REINSTALLMODE to something very simple so the
In WiX v2, the only way to condition out the ConfigureIIs action (the one
you want) in the .wixlib is to modify the .wxs file for the sca.wixlib and
rebuild it. In WiX v3, it is possible to override the condition on actions
without rebuilding (the feature you need).
From: [EMAIL PROTECTED]
: Wednesday, July 05, 2006 1:33 PM
To: wix-users@lists.sourceforge.net
Cc: Darren Kulp
Subject: [WiX-users] XmlFile - specification misimplementation
A
conversation between Michael Cline and Rob Mensching has clarified the state of
XmlFile, but in case this information can help anyone else
Ahh, the COM+ MSI Creation Wizard... you know, I've spent years (on and off)
trying to track down who owns that silly thing. I was hoping to get them to
help do the right thing with COM+ in MSI. I never found them and nobody
seems to understand what that Wizard thing does or how it works. I've
To answer your question about building the WiX toolset. You
cant do it by just downloading VS. We designed the build process
to work from freely available tools. There was some early criticism of the
WiX project being a way to force people to buy Visual Studio.
So, now you just need to
Yeah, I dont think enough functionality is provided
currently to make this work. You do need something like a GroupSearch
element. If youd like you could take a look at the code (start in
wix\src\ca\serverca\scasched\scauser.cpp) and help extend it. I would
also encourage you to open a
I like dropping the month out of there. It isnt likely
were going to change the schema multiple times in a year and not like well
release a WiX v4 in 2006. smile/
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Derek
Cicerone
Sent: Thursday, July 06, 2006 11:57 AM
First, if you have a patch to the code, please start the discussion on the
wix-devs mailing list about that patch. There should be no confusion about
that. We talk about the code on wix-devs.
Now, Pedrum is still waiting for an answer for his last patch... but I'll
get to that (hopefully,
Looks like I saved up all the legal questions for the same day. Again, I'm
not a lawyer so if you want real answers to these questions you need to talk
to your lawyer. I'm just passing on what I've heard about the topic.
1. As far as I know, if you make a change to any of the files in the WiX
I'd love to be able to contribute to WiX (in particular
MSBuild support and Votive) but the hoop-jumping
required to complete the assignment agreement totally
put me off.
I know what you are saying here. The assignment agreement has been
something I've been arguing against since the
-Papers.html#Copyright-Papers.
It also seems that they use a similar snail mail process...
Rob Mensching wrote:
I'd love to be able to contribute to WiX (in particular MSBuild support and Votive) but the hoop-jumpingrequired to complete the assignment agreement totallyput me off.
I know what you
I just want to pull of the 'No' button without disablling it for any/all
error dialogs.
I believe the decision of what buttons to show is in the CustomAction code
directly.
-
Using Tomcat but need to do more? Need to
Your Merge Module's directory tree is not rooted in TARGETDIR/SourceDir.
That will create all kinds of whacky behavior.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Juanito
Sent: Monday, July 17, 2006 10:49 AM
To: wix-users@lists.sourceforge.net
Merge Modules can have their TARGETDIR retargeted. So you can have your
Shortcut point at the directory nested just under TARGETDIR then inform the
consumers of your Merge Module that they can put the Merge element under
different Directory elements to get the Shortcut installed in different
I know that I had trouble with Component
referenceing because you can't reference a single component from multiple
features... at least, I couldn't get it to work...
[DerekC] You should absolutely be able to
reference a single component from multiple features using multiple ComponentRef
Only if we lean on them. I've found (even inside Microsoft) most platform
teams never think about the setup implications their new technology
introduces. IIS is my favorite example (I have the hardest time even
getting them to look toward the installation problem of web sites and
virtual
Derek is having problems with his mail.
From: Derek Cicerone
Sent: Wednesday, July 26, 2006 4:03 PM
To: Rob Mensching
Subject: rfc: break WiX 3.0 backwards-compatibility with WiX 2.0 library
(wixlib) files
WiX
3.0 currently has the ability to read library (.wixlib) files
To be perfectly clear, you are trying to bypass a feature that was put in
place to protect users. I don't work with drivers and don't really know a
whole lot about them, in general, but I don't think you'll get a lot of
support trying to hack around the protection. The whole thing sounds pretty
Yeah, that scenario just doesnt work right. The problem is that Assemblies
going to the GAC arent committed until the very end of the install. That
means your InstallUtil calls (assuming InstallUtil can reach into the GAC,
Ive never tried) have to come after InstallFinalize. That means that
configured.
As an aside, you should look at MsiHiddenProperties as a way of not
exposing
passwords in a log!
Phil Wilson
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Rob
Mensching
Sent: Friday, July 07, 2006 6:00 PM
To: 'Chandra Rentachintala'; wix
This is good, except for the part about not creating an Extension. smile/
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of John Vottero
Sent: Wednesday, July 26, 2006 5:32 AM
To: Bob Arnson
Cc: wix-users@lists.sourceforge.net; [EMAIL PROTECTED]
Subject:
http://gotdotnet.com/Community/UserSamples/Details.aspx?SampleGuid=e14336d7-
1b7b-4287-8e20-51fe07cb12aa
It uses installutil.
I looked into the MSM a bit. If I understand the code correct, it appears
that I was wrong and you can call InstallUtil on GAC'd assemblies (although
reaching into
This is a pretty neat looking GUI editor for WiX.
Yeah, I looked at it over a year ago (kinda' chagrined that the thing used
ClickOnce to deploy, heh). Unfortunately, it doesn't look like it has been
developed since then. The editor still doesn't support adding Components or
Files. I'm not
Product/@Id is a
kinda' scary thing to make optional. What if someone just accidentally
forgets to add one? Or what if someone copies an example that didn't add
it? The developer will end up with a product that is very difficult to
track.
I appreciate the
consistency proposed but I'm
0. It is less about
preferable and more about .wixlibs actually are designed to
solve the problems it appears you are working on. Merge Modules are not
intended to be used the way you are trying to use them.
1. Not much. But in
WiX v2, there really isn't much to .wixlibs. They are
Judging from the release.txt file, the July, 27th releases of WiX 2.0
and 3.0 (1926/4326) contain a fair amount of enhancements.
That's why I'm thinking about pushing this version to SourceForge.
That back log is mostly my fault. The password for the user account used to
push the bits up to
I'd be okay with that.
From: Derek Cicerone [mailto:[EMAIL PROTECTED]
Sent: Monday, July 31, 2006 10:47
To: [EMAIL PROTECTED]; [EMAIL PROTECTED];
wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] rfc: Package element changes
That is an excellent
I have no opinion on that. Anybody else care?
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bob Arnson
Sent: Monday, July 31, 2006 3:39 PM
To: [EMAIL PROTECTED]
Cc: wix-users@lists.sourceforge.net; [EMAIL PROTECTED]
Subject: Re: [WiX-users] rfc: Package element
Condition the Component (or Feature) installing the Shortcut.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Magus
Sent: Tuesday, August 01, 2006 10:59 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Shortcuts
I've been trying to create a
But won't that condition effect both the File and the shortcut?
Yes. You'd have to put the Shortcut in its own Component.
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and
You're probably crashing. The Windows Installer has an exception handler to
ensure that poorly written CustomActions don't hose the transaction.
You should look at other places in the code where WcaGetProperty() is used.
You'll find the WiX code has very, very few hard code buffer sizes.
Rob is right. Permanent is better than absent GUID because you can still
patch the files. However, be very careful about what you leave behind. It
would be very, very bad to leave behind files that could have security
exploits in them. Nobody would know to patch them.
-Original
Title: Performance issues
When you say youve replaced InstallShield with the WiX
toolset, what version of InstallShield did you replace? I ask because the
non-MSI versions of InstallShield used a scripting engine to do the
install. That engine (as Ive been told) doesnt do nearly
the same
Title: Performance issues
Now that you have these comparisons, I suggest generating a
verbose log file and seeing where your time is spent in the Windows Installer.
Each action has a start and stop so that should be pretty easy. You may
find something surprising (like a CustomAction taking
http://blogs.msdn.com/robmen/archive/2006/05/30/610950.aspx
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bob Arnson
Sent: Thursday, August 03, 2006 4:19 PM
To: Magus
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] ScrollableText Control type
I am still wondering why MSI does not support unicode database in
the current version, if even MSI 3.0 or later does not support
non-unicode based operating systems - Windows 9x.
File format changes are never cheap... especially, when you have over 7
years of files that you have to maintain
So why don't you go send a comment from the Windows Installer team's blog
and tell them to document the feature or quit using it themselves?
Complaining to the volunteers that work on the WiX toolset won't do you
nearly as much good as commenting directly. It might make you feel better
but it
http://wix.sourceforge.net/releases/
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Mark Weaver
Sent: Tuesday, August 08, 2006 8:06 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] COM+ extension in Wix3
I seem to be having trouble finding
Sorry, I thought you were just looking for the release point. It does
appear that pcaext.dll is gone. Bob and/or Fredrik should be able to
explain why pcaext.dll has gone missing.
-
Using Tomcat but need to do more? Need
It can be worse than that. If any of those Files are shared across
different Products that can be installed on the user's machine, you can get
into scenarios where the Files are incorrectly reference counted. I tried
to capture much of the trickiness here:
believe, requires storing data in ways that are rather unnatural in a build
environment).
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Rob Mensching
Sent: Wednesday, August 09, 2006 10:03 AM
To: 'Dave Williamson'; 'Eric Fesh'; wix-users
Standard directories are a little bit different. The way
they work is you add a GUID to them everywhere. You also need to make
sure the WindowsFolder is listed in your Directory table for your Merge Module
(which I think is probably the root of your bug). Then, during the merge
process
Why? That's not really designed to work out well.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Peter G.
Sakhno
Sent: Tuesday, August 15, 2006 06:08
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] How to create shortcuts for files from MSM?
Are you building on Win2k3? If so, what version of the
Windows Installer do you have on the machine?
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Darrel
Miller
Sent: Wednesday, August 30, 2006 12:34
To: [EMAIL PROTECTED]; wix-users@lists.sourceforge.net
Subject:
This topic from MSDN might be interesting as well:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/msi/setup/windows_installer_start_page.asp?frame=true
-
Using Tomcat but need to do more? Need to support
You just need a TypeLib element. I think the new heat.exe can even pull the
TypeLib stuff from a .tlb directly... maybe.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Standa Kunc
Sent: Tuesday, September 05, 2006 13:51
To: WiX-users
Subject:
Also, Bob, we might consider allowing the Votive MSI install the
.xsd's even if we can't install the full plug-in. Sound reasonable?
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Rob
Mensching
Sent: Tuesday, September 12, 2006 10:19
To: Cullen Waters; Ali-Akber
going away so expect to see more questions (and I hope more answers) here.
There are no changes to those of you out here..
September 15th is the day the internal mailing list goes away. September
15th is going to be a big day.
virtually,
Rob Mensching
http
It's a MSI design decision that makes sense when you consider the way that
Fusion works (BTW, Fusion design frustrates me to no end).
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Petr Vones
Sent: Tuesday, September 12, 2006 02:03
To:
I'm a little confused. Why is NOT Installed wrong?
Based on your original question, I think Chandra provided the best answer.
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Saranath
Aravamudhan
Sent: Friday, September 15, 2006 17:01
To: Chandra Rentachintala;
Oh, wait, after seeing a different fork of this thread, REMOVEALL
would be the answer if you want to run during install and all repair situations
but not uninstall. That makes more sense to me.
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Rob
Mensching
Sent
1. For v2 and v3 look at the namespace on the Wix element.
WiX v1 was never released and the syntax is quite different from v2 and v3.
For example WiX v1 has no Id attributes.
2. WebDirProperties/@DefaultDocuments
3. That should work. Have you found that it doesn't?
From:
The Windows Installer reference counts Components not Resources (like files
and registry keys). You need to be very careful how you organize your
Resources in the Components (identified by their Guid). You can find a
Component Rules 101 discussion on my blog.
-Original Message-
From:
From: Rob Mensching
Sent: Saturday, September 16, 2006 2:38 AM
To: Saranath Aravamudhan; Chandra Rentachintala;
wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] FW: custom actions
Oh, wait, after seeing a different fork of this thread, REMOVEALL would
How do you measure the number of successful installs?
PS: Sorry for the mess, I'm cleaning up right now and this next build should
be much better.
-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Frederik
Carlier
Sent: Monday, September 18, 2006 22:48
To:
Title: RE: [WiX-users] Planning a new WiX release
Heh, so it's more of a negative test: nothing bad seems to
have happened so that's good. smile/
That's fine, I was just more curious than anything. You never told
me (or I just forgot) how you determined which releases were good to go to
You mean add a hyperlink to a MSI dialog? If so, then No,
the Windows Installer does not support hyperlinks. You'd have to go
to an external UI handler and that is a whole lot of work that just isn't worth
it. I'd suggest a button instead.
From: [EMAIL PROTECTED]
[mailto:[EMAIL
Also, note that there is a tool called WixCop that
will automagically upgrade your WiX v2 source code to WiX v3 source code.
It handles cases like this. It can save you significant amounts of time.
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Mike
Dimmick
Sent:
0. I was not intimately involved with the NGen development
so if I sound like I don't know what I'm talking about, I don't and I'm sorry.
1. Verbose log of the failed uninstall should show much more
detail.
2. Not sure. It looks like install and uninstall use
the same entry point so
There is a topic in the MSI SDK about creating multiple instance MSI files.
It is pretty tricky and a fair bit of work (not much different than
proposed, but transforms are used to minimize the number of MSIs
distributed).
I do *not* recommend using CopyFile to try and solve this problem.
Are you building on Win2k3? If so, make sure you have the latest Windows
Installer installed. There was a bug in the SAFER policy that prevented
validation from working correction on Win2k3 with just this sort of error.
If you're not on Win2k3, umm, I'll have to think some more.
-Original
The cultures switch is required, but why do you have to suppress
validation?
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Matthew
Janulewicz
Sent: Friday, September 22, 2006 17:29
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] WIX 3.0: Creating IIS
Do what the error message says. Remove the unexpected attribute Action
and add a Level attribute. The documentation explains when each attribute
should be used:
http://wix.sourceforge.net/manual-wix2/wix_xsd_condition.htm
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL
Yes. You don't need the square brackets around the Property.
I suggest reading the MSI SDK topic about Condition Syntax.
From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Saranath Aravamudhan
Sent: Saturday, September 23, 2006 00:50
To: wix-users@lists.sourceforge.net
No, you can't. Only a transform can be applied at the right time to change
those values.
Furthermore, I would not recommend using Script for CustomActions ever.
-Original Message-
From: Dmitry Briliuk [mailto:[EMAIL PROTECTED]
Sent: Monday, September 25, 2006 12:29 PM
To: Rob Mensching
Since Derek is gone, I guess it's my role to ask this question again,
Why do you have to do
this?
My installer needs to install on a volume other than
where Windows is installed (its a security issue for
our app). I can use the WindowsVolume property
to find the drive
You want the WixTasks.* files. If you install the new
Wix3.msi, it should configure the WixTasks for you automagically.
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Sayed
Hashimi
Sent: Tuesday, September 26, 2006 12:01
To: wix-users@lists.sourceforge.net
Subject:
This was discussed on the mailing list in the last few days. The only way
to do multiple instance installs is documented in the MSI SDK (and that says
you must use transforms).
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Dmitry Briliuk
Sent:
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bob Arnson
Sent: Thursday, September 28, 2006 18:49
To: Wilson, Phil
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Launching a CHM
Wilson, Phil wrote:
If Wix actually
has a built-in
So does that mean you are writing it, Bob? smile/
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bob Arnson
Sent: Thursday, September 28, 2006 18:49
To: Wilson, Phil
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Launching a CHM
Wilson,
You cant do that. I suggest reading the documentation
that Jason pointed out. It explains how limited exe CustomActions can
be. If you really want that much control over your installation, you
should write a DLL CustomAction. Those have the ability to be more
robust.
From: [EMAIL
This year? Stick to v2. I'm expecting there will be another bump or two in
the next few months in v3 that I would not want you to go through. WiX v2
isn't as cool as WiX v3 but it will behave consistently... which is probably
the most important thing for you in the next few months.
). Then back into the extensions.
* Justin Rockwood - Votive 3 was released. Seems to be mostly okay. Few bugs
but nothing blocking. Going to add $(var.Project.Item) support back like
Votive 2 had. That should get Votive 3 totally caught up and beyond Votive 2.
* Rob Mensching - Focusing
Your latter scenario should work today. If you create a
CustomTable with only Rows in it, it will automatically create a reference to
the CustomTable with the definitions. Did that not work? If not,
then please do open a bug and someone will fix it because it is supposed to
work that way.
Check out the File Versioning topic in the MSI SDK. That is what will control
how your files get upgraded. Changing the GUID on the Merge Module won't
affect them. The Merge Module signature has a version, I would suggest leaving
the GUID the same and just up'ing the version number... unless
You should schedule your CustomAction inside the Merge Module. When the Merge
Module is merged it will be put in the correct sequence in the final MSI. The
MSI SDK has more information about sequencing CustomActions in Merge Modules.
-Original Message-
From: [EMAIL PROTECTED]
You have to extract it. The Windows Installer engine doesn't know how to read
MSI files out of resource streams. Besides, you're going to want to put the
MSI in a place where future repair operations can find it. Otherwise the user
will get prompted to find an MSI that is hidden inside your
True, I take a more cautious stance. I really do want you guys to like me and
giving bad advice doesn't seem like a good way to do that. smile/
One thing I would add to Darrel's statement below is that WiX v3 is still under
development. From build to build, you may run into changes in the
One GACd assembly per Component is the rules from the
Windows Installer. Honestly, when considering the Component Rules, I
would suggest one file per Component in almost all cases.
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Douglas
Watts
Sent: Tuesday, October
:[EMAIL PROTECTED]
Sent: Thursday, October 05, 2006 9:26 AM
To: Rob Mensching
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Upgraded merge modules
Thanks Rob.
This issue has come about because our product groups use InstallShield to
incorporate the merge modules
Actually, your suggestion about using Fragments is a very much recommended.
Merge Modules should be used when you are distributing blocks of code to across
organizations that don't all use the WiX toolset. Otherwise, .wixlibs are far
more efficient and powerful.
-Original Message-
I actually thought the mailing bounced me off the list (again). I think now it
was just an outage in SF tons of mail showed up today.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Stefan Pavlik
Sent: Thursday, October 05, 2006 3:45 AM
To:
You could try moving to a more recent build. There were
some minor fixes but nothing that I think will actually fix this. Im
a bit at a loss on how to even go about debugging this. What version of the
CLR are you running? I wonder if maybe there is a double Dispose() in the
code somehow.
That's why I'm planning to write a Disk Clean-up Wizard plug-in for WiX.
smile/
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Magus
Sent: Thursday, October 05, 2006 11:42 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Embedding MSI in
1 - 100 of 5072 matches
Mail list logo
