I have been looking online for sometime now, and getting all the more confused...
- How are VSTO, COM objects and Office.Interops related?
- Are all Interop objects COM?
- How would I serialize a class using VSTO?
I have been looking online for sometime now, and getting all the more confused...
A similar question answered. In a few words:
How are VSTO, COM objects and Office.Interops related? Microsoft Office has been developed mostly as unmanaged code which exposes its Object Model as a set of COM objects (classes) and interfaces. Office.Interops
(or Office PIA) provides Runtime-Callable Wrappers for those interfaces, so they can be called from managed .NET code. VSTO is a set of managed libraries which make use of the Office PIA to facilitate Office add-in, smart tag and document customization development.
Are all Interop objects COM? Not exactly, they're more like proxies from .NET into COM.
How would I serialize a class using VSTO? If I understood this question correctly, this is done via document customization. A VSTO extension can save its state in the Office document as custom properties or custom tags (a related question).