>I actually found this article right after I posted my first message. But I've struggled to make it work for me. The example is in C#, and though I've been pretty successfull porting other C# snippets to VB, I had no luck with with this one.
>

I know its a pain in the butt, but its good practice to be able to mix and match languages. Maybe the path of least resistence is to keep the c# code in a separate project that you include in your solution. Then just reference that c# code from your vb code.