第一个重大胜利是使 Visual Basic.NET 不再向后兼容 VB 6.0。 在您的记忆中，这确实是第一次，当您购买 Microsoft 产品的升级版时，您的旧数据（即您用 VB6 编写的代码）无法完美且静默地导入。 这是 Microsoft 第一次升级不尊重用户使用先前版本产品所做的工作。
...
随着这一重大胜利的到来，MSDN 杂志阵营接管了一切。 突然间，改变事情就可以了。 IIS 6.0 推出了不同的线程模型，破坏了一些旧的应用程序。 我很震惊地发现我们的 Windows Server 2003 客户在运行 FogBugz 时遇到了问题。 然后.NET 1.1 并不完全向后兼容 1.0。 现在，秘密已经泄露，操作系统团队振奋起来，决定不再向 Windows API 添加功能，而是完全替换它。
Because Microsoft has given up on backwards compatibility of their API's. I guess they figured that using the maintenance cost for new development was a better investment.
Sometimes I agree, sometimes I disagree with their new view...
Now so you don't think its just me projecting my thought on microsoft here you have some references:
The first big win was making Visual Basic.NET not backwards-compatible with VB 6.0. This was literally the first time in living memory that when you bought an upgrade to a Microsoft product, your old data (i.e. the code you had written in VB6) could not be imported perfectly and silently. It was the first time a Microsoft upgrade did not respect the work that users did using the previous version of a product.
...
With this major victory under their belts, the MSDN Magazine Camp took over. Suddenly it was OK to change things. IIS 6.0 came out with a different threading model that broke some old applications. I was shocked to discover that our customers with Windows Server 2003 were having trouble running FogBugz. Then .NET 1.1 was not perfectly backwards compatible with 1.0. And now that the cat was out of the bag, the OS team got into the spirit and decided that instead of adding features to the Windows API, they were going to completely replace it.
ASP 中使用的内置语言是 VBScript 和 Javascript。 我不明白为什么有人会想使用“VBScript.NET”，而“JScript.NET”确实存在，尽管它有点狗晚餐。
如果您愿意，您可以使用 VB.NET 获取 ASPX 页面，可以采用 ASPEsq 方式进行编码。
Primarily because asp-classis is not a langauge. Its a very small framework of COM objects.
The builtin languages for use in ASP are VBScript and Javascript. I can't see why anyone would want to use "VBScript.NET" and "JScript.NET" does exist although its a bit of dogs dinner.
You can take a ASPX page with VB.NET can code isn ASPEsq manner if you like.
发布评论
评论（2）
因为微软已经放弃了 API 的向后兼容性。 我猜他们认为将维护成本用于新开发是更好的投资。
有时我同意，有时我不同意他们的新观点......
现在，所以你不认为这只是我将我的想法投射到微软这里你有一些参考：
Because Microsoft has given up on backwards compatibility of their API's. I guess they figured that using the maintenance cost for new development was a better investment.
Sometimes I agree, sometimes I disagree with their new view...
Now so you don't think its just me projecting my thought on microsoft here you have some references:
主要是因为 asp-classis 不是一种语言。 它是一个非常小的 COM 对象框架。
ASP 中使用的内置语言是 VBScript 和 Javascript。 我不明白为什么有人会想使用“VBScript.NET”，而“JScript.NET”确实存在，尽管它有点狗晚餐。
如果您愿意，您可以使用 VB.NET 获取 ASPX 页面，可以采用 ASPEsq 方式进行编码。
Primarily because asp-classis is not a langauge. Its a very small framework of COM objects.
The builtin languages for use in ASP are VBScript and Javascript. I can't see why anyone would want to use "VBScript.NET" and "JScript.NET" does exist although its a bit of dogs dinner.
You can take a ASPX page with VB.NET can code isn ASPEsq manner if you like.