it DOES... just not without some tweaking... And some code does blow up as they did away with a few commands.
Microsoft.VisualBasic namespace holds a lot of compatibility commands for vb6 conversion.
I was like you for years. I just didn't want to take that leap and change. But I took a job that was based around vb.net 2005 and it was sink or swim. That was in November. Now I go back and work on some legacy vb6 stuff and wonder how the hell I managed without .net. :)
Microsoft.VisualBasic namespace holds a lot of compatibility commands for vb6 conversion.
I was like you for years. I just didn't want to take that leap and change. But I took a job that was based around vb.net 2005 and it was sink or swim. That was in November. Now I go back and work on some legacy vb6 stuff and wonder how the hell I managed without .net. :)