Last post Nov 02, 2011 08:06 AM by bbcompent1
Nov 01, 2011 06:48 AM|Khrundel|LINK
I need my .net assembly to work with powerpoint 2010 (that specific version).
I've added to my assembly a referrence to "Microsoft.Office.Interop.PowerPoint, Version=220.127.116.11, Culture=neutral, PublicKeyToken=71e9bce111e9429c, processorArchitecture=MSIL"
and added following code:
Application app = new Application();
After this code executes, a window of Poweproint 2007 (v12) appears. Powerpoint 2010 is installed and works, but office interop assembly runs a previous version.
I've checked loaded assemblies, Microsoft.Office.Interop.PowerPoint v14 is loaded.
Is there way to make sure specific version of powerpoint will process my interop callings?
Nov 01, 2011 06:52 AM|bbcompent1|LINK
This link to download the 2010 office interop libraries should help.
Nov 01, 2011 10:19 PM|Khrundel|LINK
Thank you, but this didn't helped. I've already had this installed, reinstalled from a link, you shared, but still
app.Visible = true;
Makes Powerpoint 2007 window appear.
I can play with a registry or even delete office 2007, but this is not a solution, because I can't do such things on a client's machine.
Nov 02, 2011 07:58 AM|bbcompent1|LINK
Ok, so this is in essence trying to get 2010 apps to open on the client side? Ok, one thing to be aware of though is if your client has 2010 office installed, then 2010 applications would open dependent on them being the client-side default program. What
if the particular workstation that opens this app doesn't have PowerPoint 2010 but has the 2007 or 2003 version with the conversion tool? If you direct their system to open only the 2010 version of office programs in that case, I would think your document
would throw some error in that case. By definition, a workstation should have only one version of MSOffice though it can have multiple ones installed. I generally when building systems avoid doing that as it can cause DLL conflicts in some cases. Also, its
another thing to worry about patching and introduces complexity into the environment.
Nov 02, 2011 08:03 AM|patricgreat|LINK
may be you can try adding the desired dll into bin folder and refer from that folder, instead of from the system.
Nov 02, 2011 08:06 AM|bbcompent1|LINK
Even so, we still have very limited control over what the client side is going to do. Remember that 2007 can open 2010 office files. 2003 can open 2007/2010 with the compatibility kit.