I don't seem to remember any claims by MS that VB and VB.NET were compatible or ASP.NET would be compatible with classic ASP. What they provided were conversion tools instead.
It was pretty obvious from the get go that the.NET was a completely different technology from ASP/VB/COM and that your legacy apps were never gonna run without a fair bit of work either with the conversion tools or a rewrite. MS never made any noises to suggest otherwise.
"Okay, if you say so. But all releative and a contradiction for Windows on little iron boxes."
We run 15 shared hosting Windows 2003 boxes with an average of 900 sites on each box running a mix of ASP, ASP.NET and Perl and they run just fine. Windows if configured, managed and secured properly by experienced admins rather than by part time admins or the office secretary with an Office MCP does just fine. It's usually poorly written or buggy third party component libraries that cause all the grief.
Slashdot Mirror
I don't seem to remember any claims by MS that VB and VB.NET were compatible or ASP.NET would be compatible with classic ASP. What they provided were conversion tools instead.
.NET was a completely different technology from ASP/VB/COM and that your legacy apps were never gonna run without a fair bit of work either with the conversion tools or a rewrite. MS never made any noises to suggest otherwise.
It was pretty obvious from the get go that the
"Okay, if you say so. But all releative and a contradiction for Windows on little iron boxes." We run 15 shared hosting Windows 2003 boxes with an average of 900 sites on each box running a mix of ASP, ASP.NET and Perl and they run just fine. Windows if configured, managed and secured properly by experienced admins rather than by part time admins or the office secretary with an Office MCP does just fine. It's usually poorly written or buggy third party component libraries that cause all the grief.