General questions

[Oriane]

Hi there,

I have a few unanswered questions !

1> Can I create an ActiveX control with .NET ?
2> .NET is supposed to provide the COM functionalities. So how can I build a "COM server" in .NET ? I mean: suppose I build a .NET application/product, and I want to give my customers an tool to interop with that tool on the same machine, that is a COM component, but in ..NET. I suppose it would be stupid to use the Web Services or .NET remoting... ?

Sincerely

Oriane

 

[Mr. Arnold]

Hi there,

I have a few unanswered questions !

1> Can I create an ActiveX control with .NET ?

Yes, I would say in regards to a COM or COM+ object needing to interface
with a .NET solution.

Google is your friend.

http://preview.tinyurl.com/yst3s3

2> .NET is supposed to provide the COM functionalities. So how can I build a
"COM server" in .NET ? I mean: suppose I build a .NET application/product,
and I want to give my customers an tool to interop with that tool on the
same machine, that is a COM component, but in .NET. I suppose it would be
stupid to use the Web Services or .NET remoting... ?

You want to make a COM component then why mess around. You use VS 6 that
makes COM components and be done with it.

In VB.NET there is a COM Wrapper Class, at least it was there in .NET 2003's
IDE that interfaced with a COM component. For C# .NET 2003, one had to
manually make that class. It may be different now for VS 2005 and I have not
looked, but I don't see why you would need a Web service or .Net Remoting.

You should be able to interface with a existing COM component on the machine
using .NET 2005, use Google and look up examples.

 

[Oriane]

Hi Mr,

Hi there,

I have a few unanswered questions !

1> Can I create an ActiveX control with .NET ?

Yes, I would say in regards to a COM or COM+ object needing to interface
with a .NET solution.

Google is your friend.

http://preview.tinyurl.com/yst3s3 Ok. Thanks !
2> .NET is supposed to provide the COM functionalities. So how can I build a
"COM server" in .NET ? I mean: suppose I build a .NET application/product,
and I want to give my customers an tool to interop with that tool on the
same machine, that is a COM component, but in .NET. I suppose it would be
stupid to use the Web Services or .NET remoting... ?

You want to make a COM component then why mess around. You use VS 6 that
makes COM components and be done with it.

My question is juste theoritical. I know I can wrap a COM component in ..NET. But what can I do without COM ?

 

[Mr. Arnold]

Hi Mr,

Hi there,

I have a few unanswered questions !

1> Can I create an ActiveX control with .NET ?

Yes, I would say in regards to a COM or COM+ object needing to interface
with a .NET solution.

Google is your friend.

http://preview.tinyurl.com/yst3s3 Ok. Thanks !
2> .NET is supposed to provide the COM functionalities. So how can I build
a
"COM server" in .NET ? I mean: suppose I build a .NET application/product,
and I want to give my customers an tool to interop with that tool on the
same machine, that is a COM component, but in .NET. I suppose it would be
stupid to use the Web Services or .NET remoting... ?

You want to make a COM component then why mess around. You use VS 6 that
makes COM components and be done with it.

My question is juste theoritical. I know I can wrap a COM component in .NET.
But what can I do without COM ?

..NET is not a COM solution.