Quote Originally Posted by RipVoidWinkle View Post
Last year, I migrated some old VB6 projects to VS2017.
I had the old VS versions all still installed on my Win7 PC.

1) Open in VB6.
Run project to make sure everything works and is updated.

2) Open that project in VB Express 2008. (Skipped over VS2005)
Migrate VB6 project.

3) Open the VS2008 project in VS2013. (Skipped over VS2010)
This VS2013 project is compatible with VS2015 & VS2017
Strange that you told us in post #19 that you...
So, I moved to VB 2005 and had to make a few code tweaks.
Everything in VB.NET is OOP.
Once I did that, I just kept migrating to 2008 –> 2010 –> 2013 –>2015 –>2017
which was a matter of Open/Save in each new version.
It looks like you are just trolling.

So I won't waste anyone's time by asking how the projects you moved magically became OOP just by opening them in Visual Studio.Net.