R – .NET client vs. ActiveX (or another approach?)

activexnetsilverlightwpfxbap

Does anyone have any white papers or articles that would compare and contrast a web architecture where a .NET client component is required and the options being considered are ActiveX or a .Net component solution?

I have a customer that wants to architecturally recommend a .Net client approach over Active X. However, there are some strong opinions for ActiveX. What I would like to do is gather more background and industry support for our direction.

I personally would not recommend that anybody write an ActiveX component any more. If they are in need on enhanced features in the browser deployment model, I would generally recommend using WPF via XBAP or writing a Silverlight application. Ideally, I'd like to have a conversation about the pros / cons of standard web, augmented web (silverlight), or platform optimized (WPF).

Is this something you guys can help point us in the right direction? Any thoughts?

Best Answer

I wrote about this in 2007 - it's still applicable today - although I am seeing a great amount of interest in using Silverlight for Line Of Business applications lately.