It was a release build in a sandbox.

It could just be some DllExport/VB:NET oddity, I've never encountered it before. Just wanted to see if the combination worked, and it did.