I agree that this is generally the case where IT needs to "rewrite" a
system. In this case the existing COM code / business logic is out of
date / obsolete. There is still a lot of "legacy COM code" so you need
to be able to create a COM interop wrapper DLL to call the COM code from
ASP.NET.

The .NET framework has a lot of utility / environment / machine related
information built in so this reduces the need for Utility COM
components.


Regarding ASP.NET interview question.

Take a look at: www.brainbench.com/

http://www.brainbench.com/xml/bb/common/testcenter/taketest.xml?testId=1
231


Test Outline



.NET Framework
.NET Framework
ASP.NET
Class Libraries
Collections
Namespaces
Object Orientation
Architecture
Administration
Performance
Security
Data Integration
Accessing Data
Data Binding
Updating Data
Events
Application and Session Events
Event Arguments
Event Model
IsPostBack
Page and Control Events
Troubleshooting
Debugging
Error Handling
Tracing
Web Applications
Configuring Web Applications
Controlling Web Applications
Creating Web Applications
Deploying Web Applications
Technology
Web Controls
Custom Controls
Input Validation Controls
Intrinsic Controls
List Bound Controls
Rich Controls
User Controls
Web Forms
Code-Behind
Directives
Lifecycle
State
Using the IDE
Web Services
Consuming Web Services
Creating Web Services
Technology