1. Actually it is supported. Burn supports runtime "variables" (roughly
equivalent to a property in the MSI world), and one of the built-in ones is
VersionNT64, that behaves the same as the namesake property in MSI.
Rob is correct, though, that Burn has quite some way left to go before it will
: [WiX-users] Trying to install 4 COM Plus DLLs
Ok, this is good to know. :) So, is there another way of installing
COMPlus DLLs? Is there a tutorial for Wix in this area? :)
-Original Message-
From: Fredrik Grohn [mailto:fredrik.gr...@microsoft.com]
Sent: Friday, March 06, 2009 5:13
If you don't know what a COM+ partition is you probably don't need it. They are
used for side-by-side'ish registration, to tie components to specific users.
Fredrik
-Original Message-
From: MacDiarmid, James D [mailto:james.macdiar...@eds.com]
Sent: Friday, March 06, 2009 7:58 AM
To: Gen
2000 for
> at least a year or more. If I could use COM+ 1.5, I wouldn't be using the GAC
> at all. I would prefer use private assemblies in conjunction with the
> application directory attribute of the COM+ application.
>
>
>> -Original Message-
>> F
This is actually supposed to work. Though neither Fusion or COM+ where designed
with deployment in mind, so plenty of unexpected things seems to happen here.
This probably has something to do with Fusion, but I am at a loss to tell what.
Are you saying that you have had it working with a previou
The Complus table in MSI just takes all configuration in one big undocumented
BLOB. It is not useful for anything else than the MSI's created by exporting a
COM+ application from the catalog as far as I know.
-Original Message-
From: Adam Burton [mailto:adz...@googlemail.com]
Sent: Monda
No, proxies are not possible to create programmatically, and thus the CA's
can't do it. The only way to do that is to export it from the COM+ catalog.
-Original Message-
From: fprince [mailto:frank_pri...@csgsystems.com]
Sent: Tuesday, January 13, 2009 8:28 AM
To: wix-users@lists.sourcefo
What error do you get in the log?
-Original Message-
From: Kalvagadda, SivaKrishna (MLX Technology)
[mailto:sivakrishna_kalvaga...@ml.com]
Sent: Monday, January 12, 2009 7:00 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Installing Files to multiple
Yes, that's possible. The syntax looks like "My message [2]". See MSDN
documentation for MsiFormatRecord() for details. You can then use
MsiProcessMessage() to pass a record holding values for the placeholders.
Again, see the MSDN documentation for details.
-Original Message-
From: [EMA
The @User attribute does not hold the user name directly, it refers to the id
of a User element as declared in the Util schema. Look it up in wix.chm for
details.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Andy Kachelmeier
Sent: Monday, July 21, 200
There is a COM+ custom action and compiler extension. Check out wix.chm for
details.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Michael Faden
Sent: Wednesday, July 16, 2008 1:44 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] COM+ Registr
There is a custom action library to do COM+ registration in WiX. For v2 see the
PubCA schema: http://wix.sourceforge.net/manual-wix2/pubca_xsd_index.htm
I am on the road, so I don't have an example ready to send, but if you search
the list archive there should be something.
-Original Messag
That error means that a component with the guid "GUID-Of-Class" in your example
below was not found in the application after registering the assembly. What
happens if you remove the ComPlusComponent element, does a component with that
guid show up?
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECT
I'll offer to
have a look.
From: Christopher Karper [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 01, 2008 11:54 PM
To: Fredrik Grohn
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] How do I execute a custom action before a dialog?
It does not.
error C2664: 'WcaAddTempReco
Just guessing but, does this work?
hResult = WcaAddTempRecord (&hTable, &hColumns, L"ListBox", 0, 3,
(LPCWSTR)L"LISTBOXVALUES", i, (LPCWSTR)L"Item 1");
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Christopher
Karper
Sent: Thursday, May 01, 2008 11:01 PM
To: wix-users@lists.so
This is a known problem. See bug #1942991.
http://sourceforge.net/tracker/index.php?func=detail&aid=1942991&group_id=105970&atid=642714
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Neil Sleightholm
Sent: Tuesday, April 22, 2008 4:07 PM
To: Krause, Henn
I have a feeling this has been mentioned before and that I have forgot about
it. I wasn't able to find a bug about it. So if you have some repro steps it
would be awesome if you could file a but on SourceForge about this issue. I'll
try to have a look at this as soon as time permits.
Thanks,
Fr
Did you provide the typelib file in the MSI? The CA won't create it for you if
you don't.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of LINFIELD ,
Andrew, GBM
Sent: Monday, June 04, 2007 5:34 PM
To: 'wix-users@lists.sourceforge.net'
Subject: [WiX-users] COM+ / RegAsm
I've got
The fact that you are trying to do this indicates that you are trying to break
the component rules that says to never install two components sharing the name
and target location.
What you really want to do is have an identical component in both the MSI's
that I presume you have. That will allow
There is currently no support for this and it is probably not going to be
implemented in WiX v2. Somebody should add a feature request for it for v3
though.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of thombrown
Sent: Thursday, April 05, 2007 10:51 AM
tell - not to create a queue if
it exists.
Thanks
Deval
>From: Fredrik Grohn <[EMAIL PROTECTED]>
>To: DEVAL SHAH <[EMAIL PROTECTED]>,
>"wix-users@lists.sourceforge.net"
>Subject: RE: [WiX-users] WiX create a MSMQ
>Date: Wed, 4 Apr 2007 22:29:41 +0100
>
>
In WiX 2.0 it is possible using the MessageQueue element of PubCA:
http://wix.sourceforge.net/manual-wix2/pubca_xsd_messagequeue.htm
In WiX 3.0 these bits are still pending inclusion however.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of DEVAL SHAH
Sen
3.0 or below as far as I can tell from the code. And it needs to be present on
the target machine.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott Sam
Sent: Wednesday, April 04, 2007 4:55 PM
To: Rob Mensching; wix-users@lists.sourceforge.net
Subject
But why would you want to do that?
You can have the UI set a property with the value the user enters, and then
have a registry element that places it in a registry key. All in a purely
declarative manner.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of fiordean dacian
Sent: Wedne
This would be similar to checking for ICE's from a conceptual perspective.
Whatever fits your environment really. Just think twice before trying to auto
generate the WiX source.
From: Christopher Brandt [mailto:[EMAIL PROTECTED]
Sent: Monday, April 02, 2007 9:05 PM
To: Fredrik Grohn
Cc:
Did you link dynamically to the CRT? If that is the case the CRT DLL's are
going to be on your normal system, but not on the "clean" system. You typically
want to link statically to the CRT for custom action DLL's to avoid the
dependency.
-Original Message-
From: [EMAIL PROTECTED] [mail
It's been a while since I looked at this part of the code, but I don't think
you actually can set these attributes currently. If you have any thoughts on
how that could be solved feel free to make a suggestion... (Note that there is
the [EMAIL PROTECTED] attribute that makes a WiX provided CA do
Somebody else on the list hit this exact problem last week too...
Copy paste reply:
This is a known problem, see bug #1067343:
http://sourceforge.net/tracker/index.php?func=detail&aid=1067343&group_id=105970&atid=642714
The workaround is to set the property SKIPCONFIGUREIIS to "1" when you are n
The problem with auto generating WiX source code like that is that you very
easily end up breaking the component rules. Each file should belong to its own
component, and the GUID of the component must remain identical as long as the
file has the same name and target location. Solving this in an
The SQL CA’s uses the SQL OleDB driver directly. And yes I believe that is a
part of MDAC. Are you saying you are having problems with the CA’s failing
because the driver is not present?
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of ???
Sent: Saturday, March 31, 2007 2:07 AM
To:
It is currently awaiting check in. Rob has the bits, and I don't think it will
bounce another time. But I don't know when exactly it is going to be in...
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Krishna Vaishnav
Sent: Friday, March 30, 2007 8:01 PM
To: wix-users@lists.source
If you are talking v3 it is because the pubca bits still hasn't been included
in the official distribution. On a side note there are no pcaext.dll in v3
either as it has been replaced with separate extensions for COM+ and MSMQ setup.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
Sorry, the COM+ bits still aren't in v3. They have bounced a couple of times,
but are currently laying on Rob's table awaiting inclusion in the official
release.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of R Kishe
Sent: Monday, March 26, 2007 7:36 PM
To: wix-users@lists.source
This is a known problem, see bug #1067343:
http://sourceforge.net/tracker/index.php?func=detail&aid=1067343&group_id=105970&atid=642714
The workaround is to set the property SKIPCONFIGUREIIS to "1" when you are not
installing any components that require IIS configuration.
From: [EMAIL PROTECTED]
Try using a dummy exe file instead. If you are having problems with managed
stuff, try a native exe instead. There are plenty of info on the net about how
to do this. Also I remember there being something funky like the id of the icon
row having to be the name of the file, but I might be wrong..
GAC and COM+ are two completely different things. In order for the COM+
framework to be able to load the assembly it needs to either be in a directory
provided to COM+ (see the ApplicationDirectory property of the COM+
Applications collection) or in GAC. IMHO, you are a lot better off if you are
10:12 +0100, Fredrik Grohn wrote:
Fredrik,
> Correct, see:
Actually, not that correct because Chris was looking for a way to check whether
the property has been set at all, not to read its value. In this case, <> won't
help, the syntax is:
PROPERTY
or
NOT PROP
Correct, see:
http://msdn2.microsoft.com/en-us/library/aa368012.aspx
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jacquet Fabian
Sent: Monday, March 26, 2007 4:03 PM
To: Chris Bardon; wix-users@lists.sourceforge.net
Subject: [WiX-users] RE : Simple question-not equals condition?
What I don't understand is why people are so eager to build managed custom
actions in the first place. I don't know for sure, but I don't think there are
quite as many threads over at the device driver lists about managed device
drivers... The only reason to use managed code from inside a custom
ow example.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Moni Chow
Sent: Friday, March 16, 2007 9:26 AM
To: 'Fredrik Grohn'; wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Wix for COM+ object
Dear Fredrik,
Sorry for my late rep
You are installing a .NET assembly into GAC, but you are telling the COM+ CA's
that it's a native module.
Try replacing:
With:
And see if that works.
The problem with COM+ is that the DLL needs to be loaded in order to be
registered, and anything that goes into GAC is not vi
You really don't want to call regasm.exe from inside an MSI. What you really
want to do is get all the necessary registry keys for your COM visible
assembly. I haven't done this myself but looking at one of Rob's old examples
you should be able to get these with the following command line:
rega
Nah, I don't think so. Is there anything in the log that indicates that
something went wrong? Would you be able to share some of your WiX code?
From: Moni Chow [mailto:[EMAIL PROTECTED]
Sent: Monday, February 12, 2007 3:40 AM
To: 'Fredrik Grohn'; wix-users@lists.sourceforge.
Are you using WCAUtil form your custom action? If you do, there is a call
WcaErrorMessage(), it has a prinf like syntax so it should be easy to use.
Your option is to call MsiProcessMessage() directly (see MSDN for
appropriate values for the eMessageType parameter). The values for the
placeholders
The answer to that is unfortunately that it is currently not supported. In
order the run the application under the Network Service account it needs to
also run as a service, and that cannot be set in the current version of the
COM+ CA's. I believe there is a feature request of a bug open at SF abou
I sent them off to Rob for review and possible check-in for less than 2
hours ago. So if all goes well they should be public in a week or so. J
Fredrik
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Subbu
Balakrishnan
Sent: Friday, February 09, 2007 1:34 AM
To: wix-users@lis
Remember that if you DLL is native you currently have to list all components
contained in the DLL under the tag as
tags. This is because the COMAdminCatalog does not
provide a method to uninstall an entire assembly.
Here is an old example I usually toss around:
http://schemas.microsoft.
What is happening here is that the COMAdminCatalog.InstallComponent() method
is failing, and the error code -2146368472 means "The TypeLib could not be
loaded". Does it work if you do the registration manually or from a vbs
script? What probably happens is that you have a dependency in the typelib
One to two weeks would be my current guess. And then there is probably going
to be another week before it will be available on SF.
Fredrik
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Anders
Ljusberg
Sent: Wednesday, January 03, 2007 9:44 AM
To: Rob Mensching
Cc: [EMAIL PR
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: Wednesda
The reason the TLB is required for .NET assemblies is because the TLB is an
installed resource that would need to be tracked in case you let
RegistrationHelper create it. The file would for instance be left behind on
the system if you don't explicitly remove it when the component is removed.
Also I
creates the application).
It looks to me like there is some condition required in the COM+ application
component so that msi doesnt try to create it during reinstall.
Fredrik Grohn-3 wrote:
>
> Does the properties COMDOMAIN, COMUSERNAME and COMPASSWORD contain correct
> values ev
Does the properties COMDOMAIN, COMUSERNAME and COMPASSWORD contain correct
values even during reinstall?
Fredrik
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of gcoates
Sent: Monday, December 11, 2006 6:07 PM
To: wix-users@lists.sourceforge.net
Subject: [
Yes, I am aware of this problem, and I have been working some larger changes
that would make this problem go away among other things. I haven't made a
lot of progress lately however, so since it is being raised here I'll try to
get a fix in for this specific issue within the next week or so.
Fredr
1. You probably don't want to leave the component behind on the system on
uninstall in any case. It sounds like what you really want to do is make the
removal of the database conditional. That sounds like a perfectly valid
feature request to me. Unfortunately I can't think of a way to do it with
th
(adding wix-users)
Hi Chris,
The latest release 2.0.4415.0 (http://sourceforge.net/project/showfiles.php?group_id=105970&package_id=114109)
should contain all fixes I had pending. I haven’t had time to look into
this specific issue. If you are still seeing this problem with build 2.
July 06, 2006 4:41 PM
To: 'jdrake'; wix-users@lists.sourceforge.net
Cc: Fredrik Grohn
Subject: Re: [WiX-users] Registry Issue
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 thi
Thursday, June 29, 2006 11:43 PM
To: 'Mike Goatly'; wix-users@lists.sourceforge.net
Cc: Fredrik Grohn
Subject: Re: [WiX-users] Creating MSMQ Queues on installation
Fredrik has actually been working on exactly this.
Using Tomcat but need to do more? Need to support web services, securi
Actually, pubca.wixlib isn't really a config file. It is comparable to a .lib
file for C/C++, and the pcashed.dll and pcaexec.dll are only companion files of
pubca.wixlib.
Fredrik
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of jdrake
Sent: Friday, Jun
59 matches
Mail list logo
