Diagnosing Marshaling Errors using Interop Logging

In a previous post I described how the Loader Log can be used to help diagnose problems such as assembly load failures, version mismatches and so on (http://blogs.msdn.com/stevenpr/archive/2005/02/28/381744.aspx ).  Another critical element of our new diagnostics feature set in Whidbey is Interop Logging. Interop logging was added in response to the huge number of questions…

4

Update on “Using POOM with .Net Compact Framework Whidbey”

Last summer I wrote a post about how to access the PocketOutlook Object Model (POOM) using the Beta1 build of the .Net Compact Framework (http://blogs.msdn.com/stevenpr/archive/2004/08/05/209390.aspx ).  A few things have changed since then that make this scenario even easier. Specifically, last summer’s post included instructions for registering the POOM type library on your device.  This…

3

Using POOM with .Net Compact Framework Whidbey Beta1

Note: Be sure to also read the update to this post.  Working with POOM in the Compact Framework is even easier now that version 2 has shipped. —– One of the areas that I work on in the .Net Compact Framework group is native code interoperability.  Now that Whidbey Beta1 has shipped, I’m anxious to…

12