Convert Old Visual Basic Program to .Net
- 
 As a result of our server migration, some smaller issues are starting to appear. One of them is a small VB program that our accountant uses. Somewhere in it's code, it looks to the old server and it was coded and compiled long before I got here. I have Visual Studio 2013 and it looks like this was done in a much older version of VB. It has VBP and VBP files but I cannot open them in VS 2013. I tried CONVERT but didn't have any conversion tools. I've searched and found a few converter tools but they've not resolved the problem. Any suggestions? Thanks... 
- 
 That's VB6 or older. A completely different language. No simple "convert" button. This is where CNAMEs help for legacy app support. Chances are, just tricking the app with a hosts file entry will work. Long term you can't keep running something you can't fix. This is going to break. 
- 
 How to fix? Write it fresh. You could just use C# and make the tool again as it is. But this time keep the code. Or consider it a chance to approach the problem differently. 
- 
 @scottalanmiller said: That's VB6 or older. A completely different language. No simple "convert" button. This is where CNAMEs help for legacy app support. Chances are, just tricking the app with a hosts file entry will work. Long term you can't keep running something you can't fix. This is going to break. @scottalanmiller said: How to fix? Write it fresh. You could just use C# and make the tool again as it is. But this time keep the code. Or consider it a chance to approach the problem differently. Lord have Mercy, I just found VB 6 on our server...I almost feel "dirty" installing it just do handle this...He needs it TODAY, so quickest way to do it...but I do need to get into this code to see what it does and then as you said, re write it. This old junk will soon crawl out of the woodwork...  
- 
 VB is just an awful language. We had a huge production system written in VBScript server side and VB6 client side for nearly a decade. That was just painful. 
- 
 @scottalanmiller said: VB is just an awful language. We had a huge production system written in VBScript server side and VB6 client side for nearly a decade. That was just painful. I can agree...the plethora of VBA (which I know, isn't VB but is still VB ) projects we have drives me insane... 

