Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsVB SyntaxEnterprise DevelopmentDatabase AccessControlsCOMWin APICrystal ReportDeploymentGeneralGeneral 2
Related Topics
VB.NET / ASP.NETMS SQL ServerMS AccessOther Database ProductsMore Topics ...

VB Forum / COM / July 2008



Tip: Looking for answers? Try searching our database.

HOw to create a com+ dll component in VB

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
pkiran - 07 Jun 2008 03:38 GMT
Hi,

How to create a com+ dll component in VB,
what all the steps I need to follow in doing this.
Suppose if there is already a com client dll project is there.
what steps I need to follow to make this client dll file as COM+ Server
object.

thanks

pk
Brian Muth - 09 Jun 2008 23:40 GMT
> Hi,
>
[quoted text clipped - 3 lines]
> what steps I need to follow to make this client dll file as COM+ Server
> object.

What COM+ services are you expecting to use? Or put another way, why do you want to use COM+ for your VB component?
pkiran - 24 Jun 2008 01:15 GMT
> > 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
Ricardo Lavia - 07 Jul 2008 02:51 GMT
Are the COM client and the COM+ server actually running on different machines?

> Hi,
>
[quoted text clipped - 7 lines]
>
> pk
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.