Detailed change history of .NET framework versions?

views:

answers:

+1 Q:

Detailed change history of .NET framework versions?

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.

+1 A:

I did some invfestigaion on my Dev box, here's what I found:

I have the following .NET Frameworks installed

Microsoft .NET Framwork 1.1
Microsoft .NET Framwork 2.0 SP2
Microsoft .NET Framwork 3.0 SP2
Microsoft .NET Framwork 3.5 SP1

XMLReader is located in System.XML.dll

System.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.

ParmesanCodice 2010-04-22 09:18:12

Thanks for your investigation! This is interesting. I did not think of this solution. However, it might still be that there were other changes outside of System.XML.dll which might have an effect on our scenario. But I think it might be hard to find such changes. Maybe we should actually find another bug finding strategy... :)

gehho 2010-04-22 09:37:32

@Gehho no problem. I guess the point I'm trying to make is that the problem is **most likely** not with XmlReader as your question suggests. I doubt there's any Linq involved as you say it worked on v2.0?

ParmesanCodice 2010-04-22 09:48:33

@ParmesanCodice: Yeah, maybe my question was misleading (now edited). We do not actually have problems with XmlReader, but somewhere between deserialization and display of the data. I *supposed* that it was XmlReader because this is almost the only .NET class that is used. But of course, it could also be that the source of the problem is something completely different (not even related to .NET). BTW: I will consider to accept your answer later if I do not get any better answers.

gehho 2010-04-22 10:15:44

@Gehho The only other thing I can suggest is to use .NET Reflector in the .NET portion of the code you have available, maybe that'll give you better insight.

ParmesanCodice 2010-04-22 11:14:42

@ParmesanCodice: We already did that and did not find any suspicious code fragment. However, we found out what we now know about the code, i.e. it uses XmlReader + the only .NET portion of the software is deserialization. Anyway, thanks a lot for your effort!

gehho 2010-04-22 11:39:42

ansaurus

tags:

views:

answers:

Detailed change history of .NET framework versions?

related questions