There are too many problems known and unknown in Interop. MANAGEDCODE and UnmanageDcode's interaction problem, Microsoft solves the truth.
.NET2.0 Update to the Interop section
http://www.dotNetInterop.com/features/default.aspx?q=whidbey. The future update, in fact, it is the shortcoming of the current perspective.
The syntax of the Interop section is also very difficult. Such as "[Marshalas (UnmanagedType.FunctionPtr)]" or "[ClassInterface (ClassInterface (ClassInterFactype.autodu)]", it is inexplicable.
For example, sortedlist cannot pass from C # , such as C Class Class cannot be called C # call, such as C # call COM often have some strange problems, such as mixing programmed DLLs often lock when loading, such as ASP.NET loading Office component often error .
Such, etc., Etc..
Therefore, keep in mind the principle of M $: Any product has to be V3.0 or more is easy to use.