By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
429,373 Members | 1,792 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 429,373 IT Pros & Developers. It's quick & easy.

COM issue under .NET

P: n/a
Dear all,

Can I know is there any improvement if develop COM
under .NET comparing to develop COM using VC6?

thanks.
Jul 19 '05 #1
Share this Question
Share on Google+
6 Replies


P: n/a
You can't develop COM applications in the .NET Framework.

You can CALL a COM component and use it within a .NET application, but this
usually creates a performance hit, since the .NET Framework will have to
create a runtime callable wrapper class around your COM object.
"Bryan Gan" <gc***@yahoo.com> wrote in message
news:08****************************@phx.gbl...
Dear all,

Can I know is there any improvement if develop COM
under .NET comparing to develop COM using VC6?

thanks.

Jul 19 '05 #2

P: n/a
Actually you can create COM components using .NET, or at least using VB.NET
and C#, I'm not sure about other languages. COM Interop works both ways, you
can use TLBIMP to create a runtime callable (RCW) so that .NET can use a COM
component or you can use TLBEXP to create a COM callable wrapper (CCW) so
that COM enabled applications can use you .NET component.

One resource that describes this in detail is "Professional Visual Basic
Interoperability" by Lhotka and Hollis (WROX).

---
Rob Windsor
G6 Consulting
Toronto, Canada

"Scott M." <s-***@badspamsnet.net> wrote in message
news:%2****************@TK2MSFTNGP12.phx.gbl...
You can't develop COM applications in the .NET Framework.

You can CALL a COM component and use it within a .NET application, but this usually creates a performance hit, since the .NET Framework will have to
create a runtime callable wrapper class around your COM object.
"Bryan Gan" <gc***@yahoo.com> wrote in message
news:08****************************@phx.gbl...
Dear all,

Can I know is there any improvement if develop COM
under .NET comparing to develop COM using VC6?

thanks.


Jul 19 '05 #3

P: n/a
Hi Scott,

OK, I see what you're saying now. You're right, you can't do it natively in
..NET.

Rob

"Scott M." <s-***@badspamsnet.net> wrote in message
news:uD*************@TK2MSFTNGP11.phx.gbl...
That's true, but you can't create the COM component using .NET. You can
only call it from within a .NET app or you can wrap a .NET assembly in a CCW to use in a COM app. But, you can't actually create a COM app in .NET.
"Rob Windsor" <rw******@NO.MORE.SPAM.bigfoot.com> wrote in message
news:%2****************@TK2MSFTNGP11.phx.gbl...
Actually you can create COM components using .NET, or at least using

VB.NET
and C#, I'm not sure about other languages. COM Interop works both ways,

you
can use TLBIMP to create a runtime callable (RCW) so that .NET can use a

COM
component or you can use TLBEXP to create a COM callable wrapper (CCW) so that COM enabled applications can use you .NET component.

One resource that describes this in detail is "Professional Visual Basic
Interoperability" by Lhotka and Hollis (WROX).

---
Rob Windsor
G6 Consulting
Toronto, Canada

"Scott M." <s-***@badspamsnet.net> wrote in message
news:%2****************@TK2MSFTNGP12.phx.gbl...
You can't develop COM applications in the .NET Framework.

You can CALL a COM component and use it within a .NET application, but

this
usually creates a performance hit, since the .NET Framework will have to create a runtime callable wrapper class around your COM object.
"Bryan Gan" <gc***@yahoo.com> wrote in message
news:08****************************@phx.gbl...
> Dear all,
>
> Can I know is there any improvement if develop COM
> under .NET comparing to develop COM using VC6?
>
> thanks.



Jul 19 '05 #4

P: n/a
Is it possible to call CORBA stuff from .NET as standard or must I use some
other 3rd party libraries.
"Rob Windsor" <rw******@NO.MORE.SPAM.bigfoot.com> wrote in message
news:#4*************@TK2MSFTNGP10.phx.gbl...
Hi Scott,

OK, I see what you're saying now. You're right, you can't do it natively in .NET.

Rob

"Scott M." <s-***@badspamsnet.net> wrote in message
news:uD*************@TK2MSFTNGP11.phx.gbl...
That's true, but you can't create the COM component using .NET. You can
only call it from within a .NET app or you can wrap a .NET assembly in a CCW
to use in a COM app. But, you can't actually create a COM app in .NET.
"Rob Windsor" <rw******@NO.MORE.SPAM.bigfoot.com> wrote in message
news:%2****************@TK2MSFTNGP11.phx.gbl...
Actually you can create COM components using .NET, or at least using

VB.NET
and C#, I'm not sure about other languages. COM Interop works both ways,
you
can use TLBIMP to create a runtime callable (RCW) so that .NET can use
a
COM
component or you can use TLBEXP to create a COM callable wrapper (CCW)

so that COM enabled applications can use you .NET component.

One resource that describes this in detail is "Professional Visual
Basic Interoperability" by Lhotka and Hollis (WROX).

---
Rob Windsor
G6 Consulting
Toronto, Canada

"Scott M." <s-***@badspamsnet.net> wrote in message
news:%2****************@TK2MSFTNGP12.phx.gbl...
> You can't develop COM applications in the .NET Framework.
>
> You can CALL a COM component and use it within a .NET application, but this
> usually creates a performance hit, since the .NET Framework will

have to > create a runtime callable wrapper class around your COM object.
>
>
> "Bryan Gan" <gc***@yahoo.com> wrote in message
> news:08****************************@phx.gbl...
> > Dear all,
> >
> > Can I know is there any improvement if develop COM
> > under .NET comparing to develop COM using VC6?
> >
> > thanks.
>
>



Jul 19 '05 #5

P: n/a
"Mr.Tickle" <Mr******@mrmen.com> wrote in message
news:u0*************@tk2msftngp13.phx.gbl...
Is it possible to call CORBA stuff from .NET as standard or must I use some other 3rd party libraries.

I think it can currently only be done via third party libraries.
From what I've read borlands C# builder provides a CORBA library, Mono
provides a CORBA library, and there is an open source library[1](that I
believe mono either uses or based their CORBA support off of, but i'm not
sure and i'm too tired to look).
As i recall, the CORBA support in all cases is done using remoting.(i could
be wrong about borland's library)
I don't know if MS will ever support CORBA in the standard BCL, its
something i'd like to see, but...who knows.
COM is much more of an issue on the windows platform with application
integration, it had to be there v1.

1. that project can be located at http://remoting-corba.sourceforge.net/
"Rob Windsor" <rw******@NO.MORE.SPAM.bigfoot.com> wrote in message
news:#4*************@TK2MSFTNGP10.phx.gbl...
Hi Scott,

OK, I see what you're saying now. You're right, you can't do it natively in
.NET.

Rob

"Scott M." <s-***@badspamsnet.net> wrote in message
news:uD*************@TK2MSFTNGP11.phx.gbl...
That's true, but you can't create the COM component using .NET. You can only call it from within a .NET app or you can wrap a .NET assembly in a
CCW
to use in a COM app. But, you can't actually create a COM app in
..NET.

"Rob Windsor" <rw******@NO.MORE.SPAM.bigfoot.com> wrote in message
news:%2****************@TK2MSFTNGP11.phx.gbl...
> Actually you can create COM components using .NET, or at least using
VB.NET
> and C#, I'm not sure about other languages. COM Interop works both ways, you
> can use TLBIMP to create a runtime callable (RCW) so that .NET can
use a COM
> component or you can use TLBEXP to create a COM callable wrapper
(CCW) so
> that COM enabled applications can use you .NET component.
>
> One resource that describes this in detail is "Professional Visual

Basic > Interoperability" by Lhotka and Hollis (WROX).
>
> ---
> Rob Windsor
> G6 Consulting
> Toronto, Canada
>
>
>
> "Scott M." <s-***@badspamsnet.net> wrote in message
> news:%2****************@TK2MSFTNGP12.phx.gbl...
> > You can't develop COM applications in the .NET Framework.
> >
> > You can CALL a COM component and use it within a .NET application, but > this
> > usually creates a performance hit, since the .NET Framework will

have
to
> > create a runtime callable wrapper class around your COM object.
> >
> >
> > "Bryan Gan" <gc***@yahoo.com> wrote in message
> > news:08****************************@phx.gbl...
> > > Dear all,
> > >
> > > Can I know is there any improvement if develop COM
> > > under .NET comparing to develop COM using VC6?
> > >
> > > thanks.
> >
> >
>
>



Jul 19 '05 #6

P: n/a
"Daniel O'Connell" <on******@comcast.net> wrote in message news:<CSj4b.234084$cF.76426@rwcrnsc53>...
"Mr.Tickle" <Mr******@mrmen.com> wrote in message
news:u0*************@tk2msftngp13.phx.gbl...
Is it possible to call CORBA stuff from .NET as standard or must I use

some
other 3rd party libraries.

I think it can currently only be done via third party libraries.
From what I've read borlands C# builder provides a CORBA library, Mono
provides a CORBA library, and there is an open source library[1](that I
believe mono either uses or based their CORBA support off of, but i'm not
sure and i'm too tired to look).
As i recall, the CORBA support in all cases is done using remoting.(i could
be wrong about borland's library)


MiddTec provides a C# Object Request Broker: http://www.middtec.com.
Jul 19 '05 #7

This discussion thread is closed

Replies have been disabled for this discussion.