Again and again, it's always the same story... switching from project to
project I found at least one case where my life will be more happy (and
easy) if I could have my dear ActiveDocumentHost Control ready
to use. 
On the Beta 1 release of Visual Studio 2005 there was a great
control called ActiveDocumentHost, that essentially permits you to host
active documents (OLE documents) in your Windows applications. The documents
that was possible to host were a lot, such as Excel Worksheets and Charts, Word
documents, PowerPoint presentations, Visio projects, WordPad documents, PDF
documents and a lots of other images, sounds, media, video, and graphics
objects.
I've never known the real reason, but the control was dropped after the Beta
1 and we've loosed one of the useful new controls that the .NET 2.0 Framework
have initially provided.
Without this control, if you want to integrate Office documents inside a
Windows Form application (and maybe permit the user to edit and save it) it's
not an easy task (more hard than using the ActiveDocumentHost
control).
Obviously, we can always open office documents in a Windows Form application
using a WebBrowser control, but I think that this is not the ideal
choice and in this way you've also some limitations (for example the main of
them is that you can't edit office documents because they're loaded as read-only
documents).
If the control was ready and well-working, why the choice to drop it?
This control could save lots of time and hard work during development for many
and many cases.
I'd like to know also why the control could not be released as an unsupported
control on GotDotNet for example (maybe added to a project like Genghis). Can we
have a chance to have it again?
I want my old, dear ActiveDocumentHost control...
