Hi Rob
I have two assemblies that I am trying to install into the GAC. Both are
signed, both are generated using .NET 1.1 compiler.
One is a wrapper around a COM type library, generated by tlbimp, and the
other is a DLL which is dependent on the wrapper.
They are in separate components in
Hmm, there is nothing below that looks wrong. Can you provide more details
about the exact command lines and exact .wxs file that is causing the problem?
If you can't send the whole thing, can you send an example .wxs file that
demonstrates the same problem? I just can't repro the problem
StupidQuestion: Admin login password.
But of course, if you turn off JAAS you don't get to log in or use page
permissions.
It s perfect for planning for the weeks ahead or noting past historic
events. However, my wiki:Skins tag can't be used and there's no reason
that I can see why.
Multiple
Hi,
I've found the nice tallow.exe tool (WiX 2.0) which allows me to create
a Fragment that contains all the directories there should be packed into
my MSI file. This is nice. Now, my problem is, that tallow.exe creates a
Component for each directory, but what I want is actually a single
A component is a specific thing in a specific place. Although you can group
all the files in a
directory into a component, you can't have multiple directories in a component.
What you can do is
create a ComponentGroup in your fragment. Then your feature can contain just
one
Can anybody explain me why I get the 'Action: Null' decision in some cases,
but not in all?
MSI (s) (68:C0) [12:28:49:678]: Component: Hasp_52; Installed: Local;
Request: Absent; Action: Absent
MSI (s) (68:C0) [12:28:49:678]: Component: NetlmProgramMenu; Installed: Local;
Request:
The hottest gold stock pick
this year!
It just doesn't get any
better than this. Booming sector, tightly held, with an incredible PR
blitz starting up. Not only that, but the company is set to release some
smashing news as it moves into the New
Year! Drake Gold
Resources Inc.
Symbol:
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
André Pönitz
Sent: Wednesday, December 20, 2006 12:34 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Installed: Local; Request: Absent; Action: Null ?
Can anybody explain me
Non-Windows Installer installers use the SharedDlls registry key to refcount
the usage of common/shared dlls. By default Windows Installer will only
increment that refcount if it already exists so that the other installer will
track the refcount properly if a WI installer installs the same
Mike Dimmick wrote:
If you don't think you need install-on-demand,
repair-on-launch, or the ability for domain administrators to
advertise software through Group Policy, by all means use
non-advertised shortcuts.
Which, unfortunately, does not seem to work with Wix v3 and
validation. At
Matthew Janulewicz wrote:
I don't think there is an elegant way to do this, as the Wix
tools (or any other tools for that matter) can't predict what
ComponentRef's you want under which features.
Everything under a certain directory put in one feature seems
to be a fairly good first
Dont know if anybody answered this but here is some code...
Shows how to run XmlPreprocess.exe by Loren Halvorson.
Property Id=QtExecCmdLine Value=1/
CustomAction Id=Set_QtExecCmdLine Property=QtExecCmdLine
Value =quot;[#XMLParser]quot; /i
quot;[#ConfigFile]quot; /s
Sorry, Dhaval, I should have made it clearer that the first paragraph was my
advice to you while the subsequent paragraphs are discussing what we can do
to stop the problem recurring, i.e. potential changes to the WiX toolset so
that others don't run into the problem. I need to separate that stuff
On Mon, 18 Dec 2006 15:29:41 +0300
Alexander Biryukov [EMAIL PROTECTED] wrote:
Wix COM+ CA (pcaexec) does not allow to install COM+ .Net assembly
without TLB file, but basically it possible.
Okay, I'm having a hard time installing a COM+ .Net assembly *with* a
TLB file (Take a look at the
The validation assumes that the ALLUSERS property is not present or is set
to 0. Even if you've set ALLUSERS=1 in your package, the user installing
could set it to 0 on the msiexec command line, or a network administrator
could deploy it in the per-user part of Group Policy. You should ideally try
On Wed, 20 Dec 2006 10:58:27 +0100
Subscriber [EMAIL PROTECTED] wrote:
Hi,
I've found the nice tallow.exe tool (WiX 2.0) which allows me to
create a Fragment that contains all the directories there should be
packed into my MSI file. This is nice. Now, my problem is, that
tallow.exe creates
a Mail that was send to you with The Error.bmp has been blocked,
and Replace has been taken on 12/20/2006 8:12:43 PM.
Message details:
Server:TLVMAIL7
Sender: [EMAIL PROTECTED];
Recipient:[EMAIL PROTECTED];[EMAIL PROTECTED];wix-users@lists.sourceforge.net;
Subject:Re: [WiX-users] SQL Script
Does your components derive from ServicedComponent? Other ways they are not
COM+ components. Managed COM+ components are registered with regsvcs.exe and
not with regasm.exe.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Christer
Solskogen
Sent:
I was getting errors trying to use the script you suggested, Michael.
I ended up using Dark and just eyeballing through Orca, and actually found
several items using both methods.
Thanks everyone, for the suggestions.
From: Michael Osmond [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 06,
Maybe you confuse COM with COM+ ?
If you installing COM+, than why you do't use standart Wix CA
(ComPlusApplication element) ?
--
Alexander Biryukov
On Wed, 20 Dec 2006 20:27:54 +0300, Christer Solskogen
[EMAIL PROTECTED] wrote:
On Mon, 18 Dec 2006 15:29:41 +0300
Alexander Biryukov
I wrote a small program to walk a directory hierarchy and generate the XML
for a fragment that defines a ComponentGroup for the root folder that you
specify. It's an easy program to write and the output can be customized to
the way I like it, i.e. a lot cleaner than the output from the WiX tool,
Hi,
Can anybody suggest universal mechanism to upgrade XML config files (such
as Web.config) ?
I need to upgrade/reinstall product with XML config file, but modified by
user XML attributes and added elements must be stay.
Thanks.
--
Alexander Biryukov
Do y'all have any pointers for extracting COM data from executable COM
servers? When I heat (-gg) BOB.exe (a legacy VB component not quite
ready to be retired) for example, I get something like this:
Component Id=BOB.exe Guid={14E7...}
File Id= BOB.exe Name= BOB.exe KeyPath=yes
There are plenty of facilities to add and remove entire keys on
install/uninstall, but is there any way to remove a single registry value on
uninstall or do I need to write a custom action to do this?
Specifically, I am interested in using wix to install a Firefox extension
along with the rest
If you make a full path Root\Key\Name registry key a part of a Component,
during uninstall that key should be removed for you.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Brian Patton
Sent: Wednesday, December 20, 2006 17:15
To: wix-users@lists.sourceforge.net
Subject:
This is fine, and it works if you want to remove the whole key on uninstall.
My problem is that I want to remove a single value from a key on uninstall,
not the entire key.
On 12/20/06, Rob Mensching [EMAIL PROTECTED] wrote:
If you make a full path Root\Key\Name registry key a part of a
I'm confused are you adding a value to a MULTI-SZ or are you just creating
another Name=Value registry key. If the latter, then my statement should work
(or else I'm remembering something very wrong).
From: Brian Patton [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 20, 2006 17:29
To: Rob
I think I must have misunderstood the documentation/what you wrote.
I was under the impression that Registry Action='write' would create a value
but never delete it (and that, for that you'd have to use
createKeyAndRemoveKeyOnUninstall).
However, I rebuilt the MSI with
Registry Action='write'
Specifically, I'm looking to add a key to HKCU\Software\Microsoft\Internet
Explorer\MenuExt\ for each user.
I've tried writing to HKU\.DEFAULT\Software\Microsoft\Internet
Explorer\MenuExt\ but this seems to work only for S-1-5-18 (which must be
the default user).
I'm thinking something like:
Hi all,
I'm trying to maintain an old .wxs file generated a while ago by
decompiling a Visual Studio-generated .msi. It contains a RegistrySearch
.type=Registry node which doesn't appear to be supported any more.
(2.0.4611 doesn't like it; 2.0.2613 does). Could anyone tell me what it did,
and
You can't write to every user's profile. You can however write to the AllUsers
profile and all users will inherit that if you create a per-machine install
(see the ALLUSERS Property in the MSI SDK).
From: Brian Patton [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 20, 2006 17:59
To: Rob
Hi...
Type='registry' is not supported (it was deprecated for a long time...)
You should replace it with Type='raw' probably.
Here is actual help for Type attribute:
This attribute's value should be one of the following:
directory
Sets a directory path from the registry value.
file
32 matches
Mail list logo
