Why convert it? Simply create your resulting DLL and reference it in
the IDE. This is what I did for a C# glassy button found on Code
Project web site. The only real reason for converting it is to modify
the code and you feel better doing so in VB.NET, otherwise language
doesn't matter.
Where such code snippets are small (and I haven't checked this one so I don't
know) I would always convert to the language I am already using (Normally
VB.Net).
The main reason for this is not that I don't like C#. (Although there are
some bits of it I am less keen on than others ;P )
It's more that I hate having to create additional projects/Dlls to house
code which logically belongs in a specific tier of my existing application.
My ideal scenario is to have a project ".VSProj" project type which would
accept code files of any recognised type and compile them down into one file.
Then I could mix Vb.Net and C# as appropriate to any given task without creating
new dlls all over the place.
I think I'm going to have to keep dreaming on this one though. MS has more
to gain bty the current situation. The more people who argue over VB vs C#
the less people there are considering Java etc