Hamish -- I'm pulling out of the comment stream to answer the question directly. There doesn't seem to be a magic program, unfortunately. But the good news for you is that it is a relatively small program (400 lines of code in only 4 files).
So, if it were me, I would
- start a new C# project,
- add the 4 class files that you have,
- run them each through the VB->c# translator you linked to originally,
- dump the VB logging stuff and add in log4net
- turn the Windows Scripting stuff from VB into C# (I think your problem with this is that the translator above is flipping out on the types of WindowsScripting Host stuff)
- Compile and test.
With luck, this will take you a couple of hours. With bad luck, it depends on what the project actually does and that will determine how long.
I wish you good luck.
If you decide to go this route, be liberal about commenting out huge parts of code and compiling and working on eliminating compiling errors first. I'll try to keep an eye out to help you with any other specific questions that I see come across the front page.
Matt Dawdy
2010-05-25 18:21:03