So, I have an interview for a VB.Net gig. They are willing to pay to get me up to speed (last few jobs were C# and current is C). So I guess the question is: Should the remittance be good enough, would making the switch be worth it?

I thought that VB.NET is dead :) Probably will be same as Clipper soon. With those language agressors like Swift and Go there is no future for that except legacy jobs.

It is mostly legacy work. Upside it gets me into the commercial domain.

@DevotedSniper yeah that's true. I'll sleep on it. But honestly I am working in old proprietary C at the moment so I don't think my brain is functioning correctly?

I bet C has a brighter future than VB.Net, lol... Honestly, I would reject the offer, but that's up to you.

Do both.

actually there are a lot of projects in enterprise sector that is build on vb and for obvious reasons they don't gonna change soon. Also this type of companies tend to keep their developers for years, because stability is more important than "new technologies" and shit.
So it is just a question about if you want to work with vb, which is like a toy for a serious developer.

I am a C# dev but I can do VB.Net too. They are the same framework and much is the same in terms of libraries and functionality. I would take the VB job and see if you can move stuff to C#. The dlls are compatible too so you can interchange. And when you get lost you can do a C# to VB conversion ;)

@manFrame that's what I figured. Their main product is used by hundreds and was written many years ago. I figure if I can modernize it some then we're golden. If not, shoot, I can do most anything for a year.