Getting rid of TypeLoadException in your WinRT app

I’ve seen enough people asking about this so I thought I should talk about this in my blog. They see strange first-chance TypeLoadException happening in their application but it doesn’t seem never cause any problem (app doesn’t crash) and everything still seem to work ‘fine’. This seem to happen mostly if you have a C++…

0

WARNING: VS 2012 might break your broken P/Invoke

I’m seeing many people reporting that they are seeing strange P/invoke issues when they moved their code to VS 2012. Typically, they have P/invokes like this: [DllImport("Win32Project2.dll", PreserveSig = true, CharSet = CharSet.Unicode)] static extern int MyPInvoke(out string ret); If you attach a native debugger (or enable native debugging), with the right symbols (public symbol…

2

Marshal.GetHRForException does more than just Get-HR-For-Exception

Let’s first start by looking at a small code snippet: if (Marshal.GetHRForException(myException) == E_SOME_COM_ERROR) DoSomething(); This looks perfectly fine, right? Not really. It turns out this API is actually poorly named, and it actually does more than just retrieving the HR from the exception object. Using this API incorrectly could give you some weird problems,…

0

Interpreting HRESULTS returned from .NET/CLR: 0x8013XXXX

What is 0x8013XXXX Occasionally you might run into mysterious HRESULTs returned from .NET that begins with 0x8013, for example, 0x80131522. Unfortunately the error lookup shipped with Visual Studio doesn’t really work on those strange HRESULTs. What are they? It turns out they are in fact, defined by .NET/CLR in the header files. All these failure/success…

0