I’m using the office viewer activex control. I have spent lots of time in solving the bug of dsoframer. It is originally developed by Microsoft as a C++ ActiveX control sample to host/embed ms-office documents (download here). But unfortunately it also have several bugs:
1. The title of the host application will go garbled when the control is disposed.
2. Event can not be fired correctly when embedded directly in a winform control.
3. Events can not be fired when wrapped in a C# user-control.
4. Call DSOFramer to handle word in IE cause IE crash.
5. Word 2007 files will be deleted after saving.
6. Files are locked so the upload action will always fail.
Can not start a separate office process to handle the documents if there is already an existing one. For destop application, this may lead to miscellaneous bugs such as: no response of toolbar, can not start office externally after control is initialized, redo/undo influence all the instances instead of the active one, etc.
Are the issues exist in your component? It looks more steady than the dsoframer and has more functions.
One Response to “dsoFramer replacement?”
Leave a Reply
You must be logged in to post a comment.
August 27th, 2007 at 10:46 am
The DSOFramer VC++ Control is released provided by Microsoft to demonstrate how to host Office documents in VB or HTML. As a COM component, it can also be invoked inside .net applications. Unfortunately MS does NOT guarantee any support as it is provided as an example only.
We provided a good tech support and better component for the users. As you try, you can find we have solved lots of issues as you said.