> > Hi,
> >
[quoted text clipped - 5 lines]
>
> What COM+ services are you expecting to use? Or put another way, why do you want to use COM+ for your VB component?
Hi Brian,
Thanks for the reply.
basically I am Java programmer.
In my project requirement, I need to interface with COM+ objects.
COM+ objects returns the ADODB.recordset object .
COM client objects( another dll file ) gets the reference of recordset and
populates the data into a collection object. if I interface with COM client
components, I have to do very little coding else very tough to interface with
COM+ objects as it returns the recordset object.
in this situation, I feel converting com client part would be easier than
interfacing with COM+ object.
To convet COM client to COM+ component ,
is it ok create an appliaction in COM+ Component Servcies and copy this dll.
Is these steps are sufficient to convert COM client to COM+ Server.
I observered with COM+ class files properties are
Databinding Behaviour = 0-VBNone
DataSourceBahavior = 0-VBNone
Instancing = 5-multiuse / ( only one file has instancing propety - 6
Global multiUse )
MTSTransactionmode = 2-RequiresTransaction
Persistable = 0 - NotPersistable.
Client part class files are having the following properties
Databinding Behaviour = 0-VBNone
DataSourceBahavior = 0-VBNone
Instancing = 5-multiuse
MTSTransactionmode = 0-NotAnMTSObject
Persistable = 1 - Persistable.
Should I have to change these propeties before converting the COM compnent
to COM+ component. Please guide me
thanks
pkiran
Brian Muth - 24 Jun 2008 05:33 GMT
> basically I am Java programmer.
> In my project requirement, I need to interface with COM+ objects.
> COM+ objects returns the ADODB.recordset object .
So can regular COM objects. No need to convert to a COM+ object at all. Just use the COM object.
You haven't provided any compelling reason to convert to COM+. Just leave it as COM.
Brian