With V1.1 of the Framework shipping


I though i’d post a couple of links I have found useful..


DennisAn wrote a great whitepaper on how to target different runtime
versions… href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnnetdep/html/sidexsidenet.asp">http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnnetdep/html/sidexsidenet.asp


And if you want to know the details of what is the breaking changes in V1.1
you can check out this list:


This list we generated from beta customers, our own testing and our own “by
design” changes:
href="http://www.gotdotnet.com/team/changeinfo/Backwards1.0to1.1/default.aspx">http://www.gotdotnet.com/team/changeinfo/Backwards1.0to1.1/default.aspx


Should we have a contest to see if who can find a breaking change not
listed?  😉


Hope that helps!


 

Comments (8)

  1. In V1.1, doubles preserve leading zeros. In V1.0, they don’t. I think that counts as a breaking change.

  2. Dominic Hopton says:

    Shipping? Where? It’s not on MSDN downloads. VS.net 2003 hasnt shipped.
    Yeah, it’s in Win2k3, but it sure as hell isnt available outside of that.

  3. Brad Abrams says:

    Soon, Soon, you will see it…. We will have a redist…

  4. Gang Peng says:

    Scott, can you post a sample?

  5. Ken says:

    The new validateRequest setting was mentioned. If not set for a page (or application) you receive the following:

    A potentially dangerous Request.Form value was detected from the client (–Snippet of offending post presented here–).
    Description: Request Validation has detected a potentially dangerous client input value, and processing of the request has been aborted. This value may indicate an attempt to compromise the security of your application, such as a cross-site scripting attack. You can disable request validation by setting validateRequest=false in the Page directive or in the configuration section. However, it is strongly recommended that your application explicitly check all inputs in this case.

  6. Kay says:

    V1.1 still has the "metric bug" in System.Windows.Forms.PageSetupDialog on PCs with metric System values. It reudces the margin values by a factor of 2.54. Is this a known bug, anyway? Does someone take care of that ?

  7. Anonymous says:

    <script>