[2005] Compontent's concept

Can we count on a component as a big object?

Can we create it in .net?

I thought it was in vb 6 time.


Not sure.

Thanks for answer this silly question.

Do you mean to say custom control or dll? If yes then yes we can do that in .Net. Sorry for my silly answer. =)

I don't know. May be calling it COM is accurate.

Are you sure you aren't thinking of something like "ActiveX Controls" ?

It isn't ActiveX Control.
It contains properties and methods.

An ActiveX Control can contain properties and methods, it's just a glorified visual class library (in some cases).

In either case, whether it's COM/ActiveX or OCX/DLL, you can still reference it from your project. Visual Studio will create an interop wrapper around it to let you use it in your .NET code.

I don't know what you mean by big object specifically so I'm assuming you mean that you want to use it somewhere.

Maybe I am confused by the concepts between COM and compontent.

What are the difference?

I think they are same??

A component is a control (roughly).
COM is a technology that lets libraries and components to talk to each other (among other things).

You can create ActiveX Controls or components using COM.

COM actually stands for Component Object Model

Does .Net still use COM?

.NET is, for a large but incomplete part, supposed to be replacing COM.

MS wants you to use .NET rather than COM for future development.