.NET框架版本的详细变更历史?
我正在寻找所有 .NET Framework 版本的详细更改历史记录(包括错误修复),尤其是 2.0 和 3.5 SP1 之间的更改。
我知道 v2.0 和 v1 存在类似的东西.1,以及 v4.0。但是,我找不到 v3.0 和 v3.5/SP1 的历史记录。
背景:(稍作编辑)我们在某些 XML 数据的反序列化(使用 XmlReader)和 UI 中的数据显示之间遇到了问题。这些问题在我们使用.NET 3.5 SP1时出现,但在v2.0中没有。现在,我想知道这是否与框架中的某些更改/错误修复有关,或者是否与其他一些差异有关。不幸的是,我们没有该软件的源代码,并且除了反序列化部分是.NET之外,大部分软件都是使用本机C++/MFC编写的。
I am looking for a detailed change history (including bugfixes) of all .NET framework versions, especially the changes between 2.0 and 3.5 SP1.
I know that something like that exists for v2.0 and v1.1, and for v4.0. However, I could not find a history for v3.0 and v3.5/SP1.
Background: (slightly edited) We are having issues somewhere between deserialization of some XML data (using XmlReader) and the display of the data in the UI. These problems appear when we use .NET 3.5 SP1, but we did not have them in v2.0. Now, I would like to know if this is related to some change/bugfix in the framework, or if this is related to some other difference. Unfortunately, we do not have the source code of that piece of software, and most of the software is written using native C++/MFC, except for the deserialization part which is .NET.
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
我在我的开发盒上做了一些 invfestigaion,这是我发现的:
我安装了以下 .NET Framework
XMLReader< /code> 位于 System.XML.dll
System.XML.dll 仅在两个地方找到:
%SYSTEMROOT%\Microsoft.NET\Framework\v1.1.4322
%SYSTEMROOT%\Microsoft.NET\Framework\v2.0.50727
我通过将 3.5 Framework 加载到 .NET Reflector 并搜索
XMLReader
来验证这一点,它引用了 2.0 System.XML.dll。这让我相信 v2.0 和 v3.5 SP1 之间这一点没有改变。
I did some invfestigaion on my Dev box, here's what I found:
I have the following .NET Frameworks installed
XMLReader
is located in System.XML.dllSystem.XML.dll is only found in two places:
%SYSTEMROOT%\Microsoft.NET\Framework\v1.1.4322
%SYSTEMROOT%\Microsoft.NET\Framework\v2.0.50727
I verified this by loading the 3.5 Framework into .NET Reflector and searching for
XMLReader
, it was referencing the 2.0 System.XML.dll.This leads me to believe that this hasn't changed between v2.0 and v3.5 SP1.