Ramesh asked:
What is the use of COM object in present scenario..?
There is no such role. Why?
ASP.NET is nothing but a plug-in for the HTTP server (HTTP server's terminology more usually operates the term "module") which programmatically handles some HTTP requests and generate HTTP responses. The ASP.NET controls are no more than wrappers of HTTP control and other elements.
COM, from the other hand, is a sophisticated work-around of the non-OOP OS (more exactly OS APIs; for example, Windows is inherently object-oriented in its internal design, but it exposed non-OOP API, to support development with non-OOP languages), designed to add the support for OOP programming, and, importantly, to restore the compatibility between languages and system, which was essentially lost in competition between different ambitious companies, organizations and teams who did not want to get into agreements. In other words, it was designed as some crutches to fix the lameness.
As .NET was originally designed as OOP platform, and non-OOP languages are completely out of the picture, it does not need such crutches. COM is still used internally to interface with some OS component and exposed to the developer, also to be used for compatibility reasons. Why would such trash be ever needed in ASP.NET? No reasons.
—SA