Why do you want the mm's in the first place ? Is this for a reference count
scenario you are trying to fix ? Or are you just looking for an easy way to
install core components to multiple applications without the rework ?
Christopher Karper wrote:
>
> But the other installations are built wit
heres how to do what Neil mentioned.
http://johnmcfadyen.spaces.live.com/blog/cns!9DD01136FC094724!249.entry
Lio-2 wrote:
>
> Hello Everyone,
>
> I have a question on how to popup a warning mesagebox if there is old
> version already installed.
> I will appreciate any help.
>
> Backround:
Hey Rob, could you elaborate on what you mean by that? Have you already
discussed this elsewhere?
On Thu, Jun 26, 2008 at 5:36 PM, Rob Mensching <[EMAIL PROTECTED]>
wrote:
> Correct, .wixlibs won't help you there. Unfrotunately, that means you're
> stuck fighting with the Modularization of ident
Doesn't that use version lying? And has that been an issue? The TechNet FAQ
describes how to do it, but the caveat is that updates require access to the
original install source.
http://www.microsoft.com/technet/community/en-us/management/msi_faq.mspx
The issue is that the "version" of the actu
Please report bugs for both of these issues. They're separate issues. For #1
are you adding the .wixlib as a reference or the project that builds the
.wixlib as a reference (one is a file reference the other is a project
reference)? The code is slightly different between the two, which is why I
ask
I have a couple of problems with Votive and wixlibs:
1. I have created a wixlib file with the files embedded in to it.
When I try to add this as a reference to a votive project it says "A
reference to myfile.wixlib could not be added. Please make sure that the
file is accessible, and that
Force-Spank LOL, I've never heard that one before. I like it.
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 Thu, 7/3/08, John Nannenga <[EMAIL PROTECTED]> wrote:
> From: John N
Another option is to create a transitive component to remove the non-versioned
file. [The RemoveFiles action runs prior to the InstallFiles action]
An advantage here is that you can condition the transitive component to only
force-spank the file when you want it to be spanked (depending on what
Thanks for the confirmation Chris. I think this is the last hurdle to my
first fully featured working MSI-based installer. My next installer
project will be considerably more complex, but I've learned a lot from
this experience, and from the list.
Incidentally, for those of you keeping score at ho
I've been doing it for years without problems. InstallShield has a feature
called `Always Overwrite` that essentially does this.
The downside to going this is if the file does contain user data, it will get
wasted unless you have a harvest/configure pattern to go before and after the
file co
If I have a text file (or other unversioned resource) that I want to
overwrite during a minor update, is it ok to give the file a "version"
using the DefaultVersion attribute of the File element? It seems like
this works and forces the overwrite only if I increment the
pseudo-version. I just want t
Thanks for pointing me in the right place
This is more what I wanted:
http://wix.cvs.sourceforge.net/*checkout*/wix/wix/src/ext/UIExtension/wixlib/WixUI_en-us.wxl
Neil Enns wrote:
>
> See:
>
> http://wix.cvs.sourceforge.net/*checkout*/wix/wix/src/ext/UIExtension/wixlib/ErrorProgressText.wxs
12 matches
Mail list logo
