几天前我有了这个想法，为什么不在 .net 中实现 asp-classic 作为另一种语言...
这将帮助很多人迁移到新平台......
我的意思是有 IronRuby、IronPython 等...
这对我来说是个好主意...但是，拜托，我不是天才，他们没有这样做一定是有原因的...
我只是好奇……
最佳答案
因为 Microsoft 已经放弃了其 API 的向后兼容性。我猜他们认为将维护成本用于新开发是更好的投资。
有时我同意，有时我不同意他们的新观点......
现在，你不应该认为这只是我在表达我对微软的想法，这里你有一些引用:
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.net - 你认为微软为什么没有将 asp-classic 作为 .net 中的另一种语言实现，我们在Stack Overflow上找到一个类似的问题： https://stackoverflow.com/questions/479476/