Dr. Dobbs has an interesting article by Frank Wu called .NET Versus .NOT… Frank talks how to spot a great .NET Component.  Customers can clearly tell if a component was designed for the .NET Framework or not.  Component vendors, both inside and outside of your company, should understand what makes a good .NET Component to make developers as productive as possible…

 

As Frank says, there is a time for both kinds of components, but users should understand which they are using.  I’d generalize Frank’s list of what makes a good .NET Component and just say a good component follows the .NET Framework Design guidelines (more). Is anything else needed?   ;-)

 

I’d love to hear some examples on good and bad .NET Components you have had the joy or misfortune to use.