[2005] Compontent's concept

[zhshqzyc]

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.

[dee-u]

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

[zhshqzyc]

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

[kleinma]

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

[zhshqzyc]

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

[mendhak]

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.

[zhshqzyc]

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

What are the difference?

I think they are same??

[mendhak]

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.

[kleinma]

COM actually stands for Component Object Model

[zhshqzyc]

Does .Net still use COM?

[mendhak]

.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.