| ActiveMac | Anonymous | Create a User | Reviews | News | Forums | Advertise |
|
|
|
User Controls |
|
New User |
|
Login |
|
Edit/View My Profile |
|
|
|
|
|
|
|
ActiveMac |
|
Articles |
|
Forums |
|
Links |
|
News |
|
News Search |
|
Reviews |
|
|
|
|
|
|
|
News Centers |
|
Windows/Microsoft |
|
DVD |
|
ActiveHardware |
|
Xbox |
|
MaINTosh |
|
News Search |
|
|
|
|
|
|
|
ANet Chats |
|
The Lobby |
|
Special Events Room |
|
Developer's Lounge |
|
XBox Chat |
|
|
|
|
|
|
|
FAQ's |
|
Windows 98/98 SE |
|
Windows 2000 |
|
Windows Me |
|
Windows "Whistler" XP |
|
Windows CE |
|
Internet Explorer 6 |
|
Internet Explorer 5 |
|
Xbox |
|
DirectX |
|
DVD's |
|
|
|
|
|
|
|
TopTechTips |
|
Registry Tips |
|
Windows 95/98 |
|
Windows 2000 |
|
Internet Explorer 4 |
|
Internet Explorer 5 |
|
Windows NT Tips |
|
Program Tips |
|
Easter Eggs |
|
Hardware |
|
DVD |
|
|
|
|
|
|
|
Latest Reviews |
|
Applications |
|
Microsoft Windows XP Professional |
|
Norton SystemWorks 2002 |
|
|
|
Hardware |
|
Intel Personal Audio Player 3000 |
|
Microsoft Wireless IntelliMouse Explorer |
|
|
|
|
|
|
|
Site News/Info |
|
About This Site |
|
Affiliates |
|
ANet Forums |
|
Contact Us |
|
Default Home Page |
|
Link To Us |
|
Links |
|
Member Pages |
|
Site Search |
|
Awards |
|
|
|
|
|
|
|
Credits |
 |
Office XP Primary Interop Assemblies | |
|
||
| Time: 00:22 EST/05:22 GMT | News Source: ActiveWin.com | Posted By: Robert Stein | ||
|
To make Microsoft® Office® XP applications available to Microsoft Visual Studio® .NET developers, Microsoft has created several primary interop assemblies (PIAs) that contain the official description of commonly-used Microsoft Office XP type libaries for applications such as Microsoft Access 2002, Microsoft Excel 2002, Microsoft FrontPage® 2002, and so on. This group of PIAs is known as the Office XP Primary Interop Assemblies. Microsoft has customized the Office XP PIAs to make them easier for managed code to interoperate with the Office XP COM type libraries. Avoid using any Office XP COM interop assembly that is not provided as part of the Office XP PIAs, or any Office XP COM interop assembly that is generated by Microsoft Visual Studio .NET at design time because they are considered unofficial. | ||
|
Write Comment
Return to News |
Displaying 1 through 25 of 156 Last | Next |
The time now is
9:17:28 AM
ET.
Any comment problems? E-mail us |
| #1 By 531 (216.137.13.67) at 2/14/2003 1:07:39 AM |
| About bloody time... |
| #2 By 1845 (12.209.152.69) at 2/14/2003 1:17:47 AM |
| These have been available for months, haven't they? Even without them, the Framework SDK and VisualStudio provide tools to generate a .NET wrapper for COM components. |
| #3 By 8273 (4.47.64.29) at 2/14/2003 2:50:33 AM |
|
#2: Yes, you could use VS to generate a wrapper around the COM type libs, but for type safety you should use an 'official' PIA from the company creating the COM object.
Suppose you create a .NET component that uses the object model of an Office application. Also suppose you have purchased/downloaded a component from another vendor. When your component references an assembly the specific public key, version number, assembly name, culture, etc must match exactly for that assembly to be loaded by your component. If you are to pass a type from your assembly to the assembly you purchased/downloaded the type, including key, version, etc must also match otherwise they are considered different types and the type cannot be passed to the other component. For example, suppose you have a component that passes the Word Application object to another component. If you have two different PIAs for the Word application, then the type for one IA would be (for brevity, leaving out some information) Application#1 and the type of the other IA would be Application#2. These are different types, and you would not be able to pass them back and forth. Notice I said IA because when you generate a wrapper around a COM object, you are generating an interop assembly (IA), and not a primary interop assembly (PIA). There are workarounds to this, such as publisher policy, but it is better to have the two components use the same assembly. There are reasons behind this, such as fixing 'DLL hell', type safety, etc. There is nothing wrong with generating an IA and using that, but you sacrifice any ability to pass a type in the IA to another application unless they also use your IA. |
|
Write Comment
Return to News |
Displaying 1 through 25 of 156 Last | Next |
The time now is
9:17:28 AM
ET.
Any comment problems? E-mail us |
