InterOP in. NET is too bad.

There are too many known and unknown problems in InterOP. The interaction between managedcode and unmanagedcode is not very good.

. Net2.0 update http://www.dotnetinterop.com/features/default.aspx for the InterOP part? Q = whidbey. In the future, we can look at the shortcomings from another perspective.

The syntax of InterOP is also very ugly. For example, the syntax of [categoralas (unmanagedtype. functionptr)] or [classinterface (classinterfacetype. autodual)] is confusing.

For example, sortedlist cannot be transferred from C # To C ++. For example, C ++ class cannot be called by C #. For example, C # Calling com often has some strange problems, for example, mixed programming DLL often deadlocks during loading, such as ASP. net is often used to load Office components.

And so on.

Therefore, keep in mind the M $ principle: Any product must be V3.0 or above.