1. Type Equivalence and Embedded Interop Types.

2. Describes marshaling for COM interop and platform invoke.

3. Never use unsafe code unless when using interop.

4. COM interop tools, on occasion, might also apply the attributes described in this table.

5. Deploying interop assemblies: You can create a standard reference to an interop assembly.

6. Alternatively, you can apply interop - specific attributes to imported types and generate a new assembly.

7. For more information, see Type Equivalence and Embedded Interop Types.

8. When importing an interop method, assert unmanaged code permission, and demand appropriate permission instead.

9. The attribute is supported for COM interop and platform invoke only.

10. When the page opens, search for interop to move quickly to the Item Interoperation section.

11. Publishers of COM components produce primary interop assemblies and distribute them to developers for use in.

12. Describes the rules that the interop marshaling service uses to marshal data.

13. The following table describes attributes that COM interop tools apply during the conversion process.

14. But the group's urgency is underlined by its statement that a product demonstration is scheduled for next August's Interop.

15. Marshaling is one of the most costly aspects of managed/native interop.

16. Using this attribute in an application that does not use COM interop has no effect.

17. The rules for type equivalence are discussed in Type Equivalence and Embedded Interop Types.

18. The best way to contact publishers is to go to a technical conference (Usenix, Interop,(/Interop.html) etc.) and go to their booths and talk to them.

19. Click the Build tab and check the Register for COM interop box.

20. For publishers, this section provides information about producing primary interop assemblies.

21. What benefit do you get from using a Primary Interop Assembly ( PIA )?