Comments on: COM automation in Silverlight 4 is not an “edge case” http://www.itwriting.com/blog/1975-com-automation-in-silverlight-4-is-not-an-edge-case.html Tech writing blog Wed, 17 Mar 2010 23:52:51 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: tim http://www.itwriting.com/blog/1975-com-automation-in-silverlight-4-is-not-an-edge-case.html/comment-page-1#comment-152298 tim Wed, 09 Dec 2009 07:03:01 +0000 http://www.itwriting.com/blog/1975-com-automation-in-silverlight-4-is-not-an-edge-case.html#comment-152298 Pete Thanks for the comment. Can you translate "unlock customer scenarios"? Thanks! Tim Pete

Thanks for the comment. Can you translate “unlock customer scenarios”? Thanks!

Tim

]]> By: Pete http://www.itwriting.com/blog/1975-com-automation-in-silverlight-4-is-not-an-edge-case.html/comment-page-1#comment-152255 Pete Tue, 08 Dec 2009 23:56:46 +0000 http://www.itwriting.com/blog/1975-com-automation-in-silverlight-4-is-not-an-edge-case.html#comment-152255 FWIW, the DLL scenario isn't one that works well at all. You run into issues with 32bit vs 64 bit systems. I wrote about that recently in my blog. The COM Automation feature is meant for the scenarios demoed: accessing apps like Word, Excel etc. to unblock customer scenarios. If you're going to package up a DLL and deal with registering it, the 32bit vs 64bit checking etc., just write the application in WPF. Your developers and end users will thank you for it. Pete Microsoft Windows Client Dev Community PM FWIW, the DLL scenario isn’t one that works well at all. You run into issues with 32bit vs 64 bit systems. I wrote about that recently in my blog. The COM Automation feature is meant for the scenarios demoed: accessing apps like Word, Excel etc. to unblock customer scenarios.

If you’re going to package up a DLL and deal with registering it, the 32bit vs 64bit checking etc., just write the application in WPF. Your developers and end users will thank you for it.

Pete
Microsoft Windows Client Dev Community PM

]]>