The Lounge is rated PG. If you're about to post something you wouldn't want your
kid sister to read then don't post it. No flame wars, no abusive conduct, no programming
questions and please don't post ads.
Why else would I accept a job to port a VB6 fustercluck to .net? Oh great I'll do it C#. No, it has to be VB.net as that's the only language the teaboy IT can write in and he'll take it over and support it post porting.
Geez, time for a large one before I go and search out the XP vm to work on.
There are plenty and nicely enough the prices are slowly rising as less people are willing to touch it. I've worked on the code base before, it's no worse or better than many and it should be a couple of months of steady work if all works out.
I've worked with this product on and off for nearly 20 years! The original was actually a VB4 re-write of an older VB3 product. At this port, 1996/97, it was pretty bleeding edge and worked very well.
It got sold and the upgrade to VB6 was no more than a rebuild. Over the years it has had so many dirty hands on it, it is hard to tell where the original is and where the band aid starts. The problem is now there is far too much band aid and the last company using it can't maintain and want to move off of XP...
You can reverse byte code derived from C# back to VB.NET?
(I think its byte code, or is it P code, I forget)
How is it gong to come up with variable names? Apart from that I imagine its a fairly easy process, but, from comparing C and assembler, without the variable names, the code is impossible to read properly.
What Pete said. Seriously. Write it in C# and use any one of the (actually very good) and free converters that are available, for example, http://converter.telerik.com/[^] though you'll probably want one that can suck in a whole VS solution.
I'm not so bothered to be honest. If I do find myself being tied up in the verbosity of it all, I may do some of it in C#. I'm hoping to persuade them that C# is a better choice. But at the end they're paying the bills.