I have successfully used the sample code below to control Word 2K and XP.
This was an Extensibility project so the app was started when Word started
but you should be able to use late binding on the generic "Word.Applicati on"
to do the same thing. The project used the Primary Interop Assemblies for
XP but they were not "installed" . The required interop assemblies were
placed in the same directory as the project dll.
Specific method calls require checking the version you are running on. I
used only Open and SaveAs but others include Compare, Merge, Sort and
PrintOut.
Hope this helps.
//get the version of Word we are running
WordVersion = (string)appObj. GetType().Invok eMember("Versio n",
BindingFlags.Ge tProperty , null, appObj , null);
//add event handlers via reflection
BindingFlags oBindFlags = BindingFlags.In stance | BindingFlags.Pu blic |
BindingFlags.No nPublic;
Type oType;
EventInfo oEvent;
MethodInfo oMethod;
object result;
// add our handlers to the events based on app
if ( WordVersion == OfficeXP ) // OfficeXP is a constant defined as 10.0
{
// the Word XP version 10.0 events
oType = typeof(Word.App licationEvents3 _Event);
//DocumentOpen
oEvent = oType.GetEvent( "DocumentOp en", oBindFlags);
oMethod = oEvent.GetAddMe thod();
result = oMethod.Invoke( appObj, new object [] { new
Word.Applicatio nEvents3_Docume ntOpenEventHand ler(this.DocOpe nEventHandler) }
);
}
else if ( WordVersion == Office2K )
{
// The Word 2000 version 9.0 events
oType = typeof(Word.App licationEvents2 _Event);
//DocumentOpen
oEvent = oType.GetEvent( "DocumentOp en", oBindFlags);
oMethod = oEvent.GetAddMe thod();
result = oMethod.Invoke( appObj, new object [] { new
Word.Applicatio nEvents2_Docume ntOpenEventHand ler(this.DocOpe nEventHandler) }
);
}
if ( WordVersion == OfficeXP )
appObj.Document s.Open(ref sFile, ref No, ref No, ref No, ref oMissing, ref
oMissing, ref oMissing, ref oMissing, ref oMissing, ref oMissing, ref
oMissing, ref oMissing, ref oMissing, ref oMissing, ref oMissing);
else if ( WordVersion == Office2K )
appObj.Document s.Open2000(ref sFile, ref No, ref No, ref No, ref oMissing,
ref oMissing, ref oMissing, ref oMissing, ref oMissing, ref oMissing, ref
oMissing, ref oMissing);
else if ( WordVersion == ? )
appObj.Document s.OpenOld(...); // I assume this will open a Word97
document??
else
throw new Exception("Unkn own Word Version");
--
Michael R
NO********@tamp abay.rr.com
"Nicholas Paldino [.NET/C# MVP]" <mv*@spam.guard .caspershouse.c om> wrote in
message news:uD******** ******@TK2MSFTN GP11.phx.gbl...
Mystery Man,
Technically, you should be able to go with option #1, as COM
interfaces are supposed to be immutable. However, the implementations behind each
may have changed. If you are not making that many calls to Office, then you
might want to consider #3, because you could do it all in code without any
interop assemblies.
Avoid #2 at all costs. That is just a nightmare waiting to happen.
Hope this helps.
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard. caspershouse.co m
"Mystery Man" <Pr************ @hotmail.com> wrote in message
news:87******** *************** ***@posting.goo gle.com... We are developing a C# application that has many interfaces to the
Microsoft suite (eg Word, Excel, Outlook, Powerpoint, etc). We need to
support Office 97, 2000, 2002 and any future versions.
Our first cut used early binding and worked fine with Office 2002. We
then ran on a machine that had Office 2000 installed and it all turned
to custard.
There appears to be a number of options to take to support multiple
versions:
(1) Use early binding on the lowest common demoninator (in our case
office 97)
(2) Use early binding for each office version (ie in our case, have
three different assemblies for 97, 2000 and 2002)
(3) Use late binding
We would prefer to go with Option (1) as this means no code changes
(not yet clarified). However, we are not convinced that this is the
correct thing to do.
What do others think?
