>If the application is well engineered and architected (even if it isn't strictly n-tier) then it should straight forward (as opposed to 'easy') to port the app to .NET. If the app is spaghetti then it will be a nightmare to port.
>
>I don't think this issue is any different than it was for porting a FoxPro for Windows/DOS app to VFP 3.0.

Oh, there's one slight difference. You didn't have to port. You could just run it. You had to port only if you wanted to take advantage of the new stuff.

which can't be said about VB6 to VB.Net port.