What could replace ActiveX in .NET?

[Guest]

Currently I have in-house software package written around ActiveX(supporting
VB and C++). Currently we are moving to .NET and I wonder what (component)
in the .NET can replace(?) the ActiveX?
I am a novice in .NET

 

[John Spiegel]

Hey Irene,

Take a look at the "COM Interop" and Runtime Callable Wrappers (RCW). To
their credit, MS recognized that a lot of functionality has been wrapped
into COM objects. The interop abilities built into .NET allow for .NET to
call and be called by COM components and for most intents they appear to
each other to be the same technology. The idea is to be able to use
existing components and gradually migrate to their functionality to .NET
rather than having to replace everything before you can deploy anything.

As far as what can replace ActiveX--that's pretty broad. Basically, .NET is
built around the same _basic_ principle of creating chunks of functionality
(chunkcionality??? <g>), but does it better.

- John

 

[Scott M.]

The concept of a "User Control" or a "Custom Server Control" both can
provide similar functionality to ActiveX.