Where did you crash? What did VS show as the callstack?
A couple of suggestions - if you can, use the debug build (then you get asserts and can see the callstack into Max.
Did you have the "Break on Exceptions" bit checked (ctrl-alt-e shortcut)? Often a crash happens, is caught by a catch-all, but we then proceed to crash elsewhere with no clue of what originally caused the crash. When debugging Max, I try to have the check "Win32" checkbox enabled. Max throws a bunch of exceptions on startup, but you can "add" the error code to the Win32 exception list, and then deselect it so Max doesn't break on that exception in future.
Another tidbit when debugging managed code, enable the checkbox to "debug native code" (in the project options somewhere). Then you will see whats happening on the native stack, which can be extremely helpful.
The .Net SDK has a few difficulties, but there should be no issues with creating an exporter for it.