I'm doing that right now. I got hired to fix some VB6 stuff and then write a connected app in webforms .net. After that they kept me on to do support and maintenance. As time allows, I re-write the VB6 to vb.net. Anything new is vb.net. In a couple of instances I needed some of the VB6 functionality in vb.net to do some quick and dirty work. I copied the VB6 to a vb.net module and just went through line by line to make it compile in vb.net. It was surprisingly easy. I'd not recommend that for anything that is going to be maintained long term, but it might get you "over the hump" while port/re-write. Someone else posted link her the tools and instructions to get VB6 to work on Windows 10. It actually works pretty well! Also the are a couple of project underway to build IDEs and compilers for VB6. Twin BASIC looks pretty impressive. Here is a link to learn more: https://www.vbforums.com/showthread.php?890181-TwinBasic[^] Good luck. PS: Ask for a raise. They going have a tough time finding some who wants that job!

The ones with an 'e' at the end require and internet connection. Without the 'e' cost about $50 more but works offline. I found this out the hard way.

Reminds me of an old joke: Q: How many programmers does it take to change a light bulb? A:That's a hardware issue.

I wish companies would stop abandoning perfectly good development tools when they pursue the next big thing.