|We have an application that writes xml files when certain things happen.
We have an ESB that picks these files up, converts them to JMS and sticks them in a queue.
We have a Windows service written in VB.net that reads the messages from the queue, writes them into a SQL DB table, then processes the messages into other table(s).
All fairly simple stuff, but the powers that be have decided they want to remove the ESB, the woman who wrote the Windows service has just started maternity leave, no-one else in the team has any knowledge of what it does, nor the time to look at it.
So I volunteered.
I have never written, read, or looked at VB before, I have done plenty of C#, and even worked on a Windows service 6 or so years ago.
So I had a look at the existing code, quickly worked out which bit needed replacing and had a good idea what it needed replacing with. Hacked together something that looked like it should work in under half an hour, then tried to install the service on my Windows 7 box to test.
2 hours of googling, registry hacking, and swearing later I managed to install it. Started it up, dropped a file into the directory, and an error because it was in use by another process. To be fair, I had read a warning about such problems using FileSystemWatcher when I first started so began searching for a solution.
I found loads, some looked nice, some looked nasty, some just looked stupid.
But nearly all of them were in C#.
How do you VBers cope?
I'm sure that if you know C# and VB then it is simple enough to convert one to the other.
And if you do know both C# and VB, why the bloody hell not just do it in C# in the first place?
Anyway, it works now, taken me nearly 3 hours. Apparently when they had a meeting to decide what to do about the problem they thought it might take a few weeks so no-one wants the solution yet.
Some men are born mediocre, some men achieve mediocrity, and some men have mediocrity thrust upon them.