On 6 Feb 2009, at 21:47, Rob Mensching wrote:
> The __Components are MSI things (for costing, IIRC). You can ignore
> them.
OK. I double-checked my WXS and they weren't there.
> The registry key path/name/value should not be case sensitive but
> whenever referring to an Id in the MSI you s
That's Windows Installer behavior. WiX doesn't control the display of launch
conditions.
You could always create a custom dialog and show that... more work but more
control
-Original Message-
From: Bo Cordell [mailto:bcord...@microsoft.com]
Sent: Friday, February 06, 2009 15:19
To: Ge
Uhh, no. Not possible to modify the install state of features of one MSI from
another. That's weird. Sounds like you really want a bootstrapper/chainer
that can see across multiple MSI files.
-Original Message-
From: Greg Silin [mailto:greg.si...@microsoft.com]
Sent: Friday, February
No such thing as a standard directory for GAC. ComponentSearch would be the
ideal (you shouldn't need a FileSearch) but I hear you on the GUID problem.
Have to verify that the guid would remain stable.
-Original Message-
From: Kevin Fischer [mailto:kevinfischer...@hotmail.com]
Sent: F
Hi Bob,
I removed the Overrideable attribute,
Sie besitzen keine ausreichenden Berechtigungen,
um auf dieses Verzeichnis zuzugreifen: [2]. Die Installation kann nicht
forgesetzt werden. Melden Sie sich als Administrator an, oder wenden Sie
sich an den Systemadministrator.
But I'm still seeing th
Hi,
Is a RegistrySearch on the following registry key the best way to achieve that?
HKLM\Software\Microsoft\Inetstp\PathWWWRoot
Thanks,
Zhisheng
--
Create and Deploy Rich Internet Apps outside the browser wi
Hi,
Is a RegistrySearch on the following registry key the best way to achieve that?
HKLM\Software\Microsoft\Inetstp\PathWWWRoot
Thanks,
Zhisheng
--
Create and Deploy Rich Internet Apps outside the browser wi
Step 1 is just a standard install, I think that's what you're saying, where the
user chooses FeatA and FeatB from the feature tree. Step 2 a) is maintenance
mode from Add/Remove Programs where the user selects FeatC to add. That's
pretty standard if you've ever changed features from Add/Remove P
Hi,
I recently posted a similar question here, but it was poorly worded :).
Suppose our MSI contains 3 different features:
MyInstaller.MSI
FeatA
FeatB
FeatC
Step 1:
- Install FeatA, FeatB
Step 2 (some discreet time later):
- Install FeatC using *same version* of MyInstaller.msi
o
I don't think you should be doing this. Windows will just take of the
situation. I have several versions of Visual Studio on my system, and if they
are all running at the same time they're all called devenv.exe. Are you going
to shut them all down whether they have your add-in loaded or not? Or
Thanks again, Rob.
To mitigate it, we are thinking about displaying the launch condition message
one after another. But I don't think it can be done using launch condition
message box since first launch condition will just terminate the install. But
are there other message box type element in W
I need to determine if a feature from SQL Server has been installed (SMO) in my
MSI. This feature can be installed via the core SQL Server package or via
standalone redist MSIs.
I know I need only a few DLLs installed by this feature's component into the
GAC.
Is the recommended way to dete
Hello all,
I just downloaded and installed Project Aggregator 2 and WiX 3.0.4805.0 on my
Windows XP SP 3 computer with VS 2005. When I run VS 2005 and click on Create:
Project (on the Start Page) the New Project dialog has a WiX item in the
"Project types" tree, but when I click on it no templ
Hmm, good question. Never had a message that stressed it. Wouldn't surprise
me if the Windows Installer is just calling ::MessageBox().
-Original Message-
From: Bo Cordell [mailto:bcord...@microsoft.com]
Sent: Friday, February 06, 2009 13:35
To: General discussion for Windows Installer
Based on my experience, I have several projects each use different installer. I
can tell you after worked(still working) with InstallShield 2009, Wise for
Windows Installer - Professional Edition and InnoSetup I found Wix
better(InnoSetup comes close) in terms of installation (even though it has
The __Components are MSI things (for costing, IIRC). You can ignore them.
The registry key path/name/value should not be case sensitive but whenever
referring to an Id in the MSI you should assume that it is case sensitive
(because it almost always is).
-Original Message-
From: Chris R
Never used Wise myself.
However, you can interoperate between the two technologies by sending Merge
Modules one way or the other. That solution won't be able to take advantage of
all of the functionality of the WiX toolset but it should all work just fine.
-Original Message-
From: Ma
Thanks Rob.
Now I have it working. But when I set the condition message, the message box is
too small to display the whole text. Is the launch condition message box fixed
size? Doesn't it adjust to the content length?
Bo
-Original Message-
From: Rob Mensching [mailto:rob.mensch...@micro
Thanks Alex. Would this be the general consensus of everyone on the
list? :)
-Original Message-
From: Alex Ivanoff [mailto:alex.ivan...@shavlik.com]
Sent: Friday, February 06, 2009 4:11 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Wix with Wis
The only advise I can give you: do not use Wise.
-Original Message-
From: MacDiarmid, James D [mailto:james.macdiar...@eds.com]
Sent: Friday, February 06, 2009 14:59
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Wix with Wise Package Studio 7
I've been
I've been experimenting with Wix for the last week or so and really like
what it can do. Now I am hearing that our team could be getting the
Wise Package Studio 7 - Standard Edition. If this is the case, can WiX
be used with another authoring package like that? If so, would there be
any benefit
Thanks a lot. I'll give it a try.
-Original Message-
From: Moradi, Ari [mailto:arastoo.mor...@hp.com]
Sent: Thursday, February 05, 2009 6:59 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Costing and external UI
Take a look at MsiGetFeatureCost --
h
On 5 Feb 2009, at 18:36, Rob Mensching wrote:
> You need the "*v" to get it all. I never bother with logs any other
> way. Nothing else (except the MSI itself to cross reference) is
> usually necessary.
OK, I now have verbose logs of an install with Java and without Java.
I'm eliding all
Hello All!
I need remove file and execute custom action during patch installation. Is this
possible? And if yes please give me small example.
--
Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM)
Yes, I like Raymond Chen's blog :) Like the original poster, I just found that
the documented
method wasn't actually working for me.
Rob
Rob Mensching wrote:
> Understood.
>
> My point was that unorthodox methods for doing things that are naturally
> supported via specifically documented mea
Understood.
My point was that unorthodox methods for doing things that are naturally
supported via specifically documented means can create support burdens for
either your application or the platform that supports your application.
Raymond Chen is one of the more popular historians of such thin
Rob Mensching wrote:
> And what are you going to do when there is a support issue?
My point was that it works, not that I've been lucky.
Rob
>
> -Original Message-
> From: Rob Hamflett [mailto:r...@snsys.com]
> Sent: Thursday, February 05, 2009 03:01
> To: wix-users@lists.sourceforge.n
27 matches
Mail list logo
