On 7/30/06, Bob Arnson <[EMAIL PROTECTED]> wrote:
Shmarya Rubenstein wrote:> - A set of merge-modules for various "software components".The first question: Do you need merge modules at all? They complicatethings, as you've discovered, and with .wixlibs, they're not necessary
unless you need to dist
I think you might be mixing concepts. In
wixlib files, there are no appended guids (there don’t need to be because
collisions are detected directly). You should never have to refer to things
with their appended guids in WiX authoring. The modularization should just
happen when appropriat
I'm not using wixlibs.. I'm using modules!On 7/31/06, Derek Cicerone <[EMAIL PROTECTED]> wrote:
I think you might be mixing concepts. In
wixlib files, there are no appended guids (there don't need to be because
collisions are detected directly). You should never have to refer to th
You could use CopyFile and RemoveFile elements, but it's much easier to just
include the file twice.
I'd only really consider this option if the file was huge.
Rob
Derek Cicerone wrote:
> There's no better way - that's it.
>
> Derek
>
> -Original Message-
> From: [EMAIL PROTECTED]
>
Hi all,This question has come up a couple of times in the last couple of days on various threads... but I'm still a little confused.Which should be used when: MergeModules or WixLib?So far as I understand these are the charactheristics:
MergeModules:- Standard MSI object- 'hard' linked by light- se
You cannot make a reference into a merge
module. Merge modules are processed by mergemod.dll (a special dll from the
Windows SDK), so WiX has very little interaction with the contents of merge
modules being put in your MSI file. This is one of the reasons we advise
against using merge mod
Derek just pretty much answered in one of the other threads on this issue:"Merge modules are processed by
mergemod.dll (a special dll from the
Windows SDK), so WiX has very little interaction with the contents of merge
modules being put in your MSI file. This is one of the reasons we advise
again
The ICEs are paranoid and assume that someone could change ALLUSERS when they
install the product in
order to do a per-user install. In this case the component needs a per-user
keypath in order to
keep track of it for each user, which is why it wants an entry in HKCU. I'm
not sure why this i
Hi List,
when starting a fresh installation, there's always a window saying
"Preparing to install ...". I see in the log file that this "show
dialog" event is not wrapped between any actions, so my question is - Is
there a way to customize this window?
Best regards,
Calin
--
On 7/31/06, Rob Hamflett <[EMAIL PROTECTED]> wrote:
The ICEs are paranoid and assume that someone could change ALLUSERS when they install the product inorder to do a per-user install. In this case the component needs a per-user keypath in order tokeep track of it for each user, which is why it wan
Calin Iaru wrote:
> when starting a fresh installation, there's always a window saying
> "Preparing to install ...". I see in the log file that this "show
> dialog" event is not wrapped between any actions, so my question is - Is
> there a way to customize this window?
>
No. MSI shows thi
>
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
Hi all,
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.
Any feedback on this version in particular (both people
having good and bad exp
Hi all,
We just adopted WIX in our installer building. We tested on
one of our products. Everything works smoothly so far, but with one small
caveat – the add/remove program icon does not show up on Windows 2000. It
is fine on Windows XP and win2K3. The icon is pointed to an icon file.
> 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
> the add/remove program icon does not show up on Windows 2000. It
> is fine on Windows XP and win2K3. The icon is pointed to an icon file.
> Any ideas?
I want to say I remember something about Win2K ARP requiring the .ico to be
stored in the resource stream in a DLL (resource-only DLL is fine).
I doubt you are missing anything obvious. I just noticed it on GDN and
thought I'd point it out to the people using EL on the list. I'm still
convinced that a better installer for EL could be made that actually did the
instrumentation features declaratively, but it is a starting point and migh
The tool definitely has a long way to go before it becomes a great GUI for
WiX. Some notion of factoring your authoring into fragments is an absolute
must, among the other features that aren't implemented yet. However, it
does look promising and has nice eye candy.
The thing that I thought wa
Perhaps some would find useful WixEdit
(http://wixedit.sourceforge.net/); it appears to be in more active
development than WixTrim, and has a dialog editor and rather good
overall interface. It supports editing, though not creating, Fragments.
-Original Message-
From: [EMAIL PROTECTED]
[ma
Hi Rob,Firstly, I've now completed my migrate to .wixlib (thanks to a lot of multi-file/regex/find-replace ;)) and am very happy with the results... for a number of reasons:0. You're absolutely right, wixlibs are what I needed all along... I think I was just mislead by what I'd previously heard abo
That is an excellent point – what if
we keep the ???... syntax just for Product/@Id in that case and go with the
recommendations below for everything else?
Thanks,
Derek
From: Rob Mensching [mailto:[EMAIL PROTECTED]]
Sent: Monday, July 31, 2006 8:32
AM
To: [EMAIL PROTECTED
Please note that CopyFile and RemoveFile are dangerous from a security
perspective because they don't provide a simple patching solution. I would
advise against that method.
Derek
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Rob Hamflett
Sent: Monday,
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 po
For our class libraries (shared assemblies that are GAC-installed), we just
create two components for the same file (and add the file twice).
In our case, we are conditionally adding the assemblies to both the GAC and
a local install directory to support adding of references to our .NET
project
You can probably just pretty print the
wixlib files and inspect them directly – its just xml (unless you use the –bf option
to bind files into it – in which case it’s a cabinet file with xml appended to
the end).
Derek
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Beh
I’d like to propose replacing the
element with more specific “SuppressModularization”
attributes on the and elements.
This basically allows the developer to suppress modularization for the 2
specific scenarios in which we currently know about the need to suppress
modularization.
It
> From: Rob Mensching
> Sent: Monday, July 31, 2006 09:06
>
> > the add/remove program icon does not show up on Windows 2000. It is
> > fine on Windows XP and win2K3. The icon is pointed to an icon file.
> > Any ideas?
>
> I want to say I remember something about Win2K ARP requiring
> the .ico
Right now I am trying to create a dialog that will basically time out of the
user doesn't do anything after a give amount of time. When it times out I
want to installation program to close. What type of action do I need to do
in order to achieve this
--
View this message in context:
http://www
Derek Cicerone wrote:
That is an
excellent point – what if
we keep the ???... syntax just for Product/@Id in that case and go with
the
recommendations below for everything else?
Any chance of a different syntax? @Id="*" maybe, keeping with the
wildcard scheme?
--
sig://boB
Hello,
After an hour of Googling, I can't see how to disallow silent installs.
The default WiX installs allow you to specify \q to MSIEXEC.EXE and you
get a silent install. However, that allows you to skip checking the
license agreement option, which my client doesn't like. What's the WiX
magic I
John Robbins wrote:
> After an hour of Googling, I can't see how to disallow silent installs.
> The default WiX installs allow you to specify \q to MSIEXEC.EXE and you
> get a silent install. However, that allows you to skip checking the
> license agreement option, which my client doesn't like. Wha
I've been thinking about adding a warning to the LaunchConditions parsing
code in the compiler. In almost every case, you should add "Installed OR"
to the beginning to ensure it only runs during initial install.
Derek
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] O
Bob Arnson wrote:
John Robbins wrote:
After an hour of Googling, I can't see how to disallow silent installs.
The default WiX installs allow you to specify \q to MSIEXEC.EXE and you
get a silent install. However, that allows you to skip checking the
license agreement option, which
Has a solution come up for setting WebServiceExtensions?
__
Don Tasanasanta
VIACK Corporation
425-605-7423
From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Joannic Laborde
Sent: Wednesday, December 14, 2005
6:19 AM
To: Jim Swainst
37 matches
Mail list logo
