Alan,

>We're doing a white paper on troubleshooting COM Interop and we thought that
>we'd ask you what topics should be covered. We figure that interop
>marshaling and using the Windows API top the list, but what other issues
>would you like us to cover?

Are any portions of the .NET Framework automatically exposed to COM Interop in the final version (as was the case in one of the earliest releases), or do we still have to create a VB or C# class to wrap .NET classes to expose them to COM Interop?

I think some explanations of that mechanism certainly belong in the paper, or at least references to the documentation for that.