MS Office Add-In's: Need References...
-
I've developed a Power Point add in which works well enough right now (except it doesn't interact with PowerPoint (other than the button on the toolbar) yet. :-D Essentially it automates some background processes for the creation of some multimedia. In any case I've found it very difficult to find good articles and/or code examples out there for actually manipulating powerpoint itself (or any other office app for that matter). Perhaps I've been entering the wrong search criteria...I don't know. In any case the C# Code Project community has been VERY helpful in the past, so I just wanted to ping your # minds for some reference materials be they web sites or books. I *have* found several books out there but have not yet had a chance to look any of them over. So any recommendations would be great. --Tony Archer "I can build it good, fast and cheap. Pick any two."
-
I've developed a Power Point add in which works well enough right now (except it doesn't interact with PowerPoint (other than the button on the toolbar) yet. :-D Essentially it automates some background processes for the creation of some multimedia. In any case I've found it very difficult to find good articles and/or code examples out there for actually manipulating powerpoint itself (or any other office app for that matter). Perhaps I've been entering the wrong search criteria...I don't know. In any case the C# Code Project community has been VERY helpful in the past, so I just wanted to ping your # minds for some reference materials be they web sites or books. I *have* found several books out there but have not yet had a chance to look any of them over. So any recommendations would be great. --Tony Archer "I can build it good, fast and cheap. Pick any two."
Ok, haven't read them yet but just noticed there are quite a few articles listed under Add-In's on the main page. PS to webmaster (the search functionality could stand a tweak I think) --Tony Archer "I can build it good, fast and cheap. Pick any two."
-
Ok, haven't read them yet but just noticed there are quite a few articles listed under Add-In's on the main page. PS to webmaster (the search functionality could stand a tweak I think) --Tony Archer "I can build it good, fast and cheap. Pick any two."
So my original question remains. All the articles I saw were for vb add-ins. --Tony Archer "I can build it good, fast and cheap. Pick any two."
-
So my original question remains. All the articles I saw were for vb add-ins. --Tony Archer "I can build it good, fast and cheap. Pick any two."
So? Don't you realize that VB uses automation, which is what the interop assemblies you'd use does? It's the same thing. The object model documented for any automation client like VB is the same which you'd use in .NET. If you're talking about VB.NET, then you don't seem to understand that different languages that target the CLR are only different syntaxes (some compilers support different levels of the CLI/CLR, however). All the languages compile down to Microsoft Intermediate Languages (MSIL), which is why the .NET Framework allows for so many languages. For a true .NET developer, translating between VB.NET and C# should be no problem. If you're talking about VB6, then again I remind you that the automation object model exposed to clients like VB6 is the same that comprises the interop assemblies I mentioned in previous replies to your posts.
Microsoft MVP, Visual C# My Articles
-
So? Don't you realize that VB uses automation, which is what the interop assemblies you'd use does? It's the same thing. The object model documented for any automation client like VB is the same which you'd use in .NET. If you're talking about VB.NET, then you don't seem to understand that different languages that target the CLR are only different syntaxes (some compilers support different levels of the CLI/CLR, however). All the languages compile down to Microsoft Intermediate Languages (MSIL), which is why the .NET Framework allows for so many languages. For a true .NET developer, translating between VB.NET and C# should be no problem. If you're talking about VB6, then again I remind you that the automation object model exposed to clients like VB6 is the same that comprises the interop assemblies I mentioned in previous replies to your posts.
Microsoft MVP, Visual C# My Articles
Oops, no I typed the wrong letter. I am well aware that they all compile to the same thing and use the same object structure. I meant VS as in Visual Studio Add-Ins. I am interested in Office Add-Ins. Specifically Power Point. I cannot seem to find many docs on automation of powerpoint (or office in general) from .NET I already wrote an the add-in, so now there is an extra button on the toolbar when I run Power Point. The button when clicked opens a custom form but I am having trouble finding documentation on how to interact with Power Point from that form. Specifically, - How do I get a reference to the power point application so I can set my form's .owner property (or .parant)? - How can I programatically make power point go into full screen mode? - How can I read/set notes for specific slides in the current .ppt file? --Tony Archer "I can build it good, fast and cheap. Pick any two."
-
Oops, no I typed the wrong letter. I am well aware that they all compile to the same thing and use the same object structure. I meant VS as in Visual Studio Add-Ins. I am interested in Office Add-Ins. Specifically Power Point. I cannot seem to find many docs on automation of powerpoint (or office in general) from .NET I already wrote an the add-in, so now there is an extra button on the toolbar when I run Power Point. The button when clicked opens a custom form but I am having trouble finding documentation on how to interact with Power Point from that form. Specifically, - How do I get a reference to the power point application so I can set my form's .owner property (or .parant)? - How can I programatically make power point go into full screen mode? - How can I read/set notes for specific slides in the current .ppt file? --Tony Archer "I can build it good, fast and cheap. Pick any two."
The best object model documentation is actually in the programming help that is not installed by default (with a typical installation) of Office. Re-run set and choose the programming help files. MSDN Online doesn't have much for some reason. When your control is created, the context in which it's created is the
ApplicationClassas it's known in the interop assembly for PowerPoint (one word, BTW). The add-in object model should already expose a way to get the running instance, such as anApplicationproperty. This is very common throughout the object model.Microsoft MVP, Visual C# My Articles