Breaking Changes in Asp.Net 4

I upgraded an app to .net just for fun and a bunch of things broke.

Turns out there are quite a few things that are officially broken between anything and .Net 4.0…

http://www.asp.net/%28S%28ywiyuluxr3qb2dfva1z5lgeg%29%29/learn/whitepapers/aspnet4/breaking-changes/

more later – joel

Published Wednesday, May 05, 2010 3:22 PM by joelvarty
Filed under: ,

Comments

# re: Breaking Changes in Asp.Net 4

Wednesday, May 05, 2010 4:40 PM by zoldello

I do not mean to appear rude but, DUH! It happens on every version; especially if you went from .NET 1.0/1 to 2.0. What would be of interest are things like how you fixed code-breaking changes, errors you see, effectiveness of correction etc.

# Twitter Trackbacks for ASPNET #Weblog: Breaking Changes in Asp.Net 4: I upgraded an app to .net just for fun and a bunch of things broke... [asp.net] on Topsy.com

Wednesday, May 05, 2010 5:04 PM by Twitter Trackbacks for ASPNET #Weblog: Breaking Changes in Asp.Net 4: I upgraded an app to .net just for fun and a bunch of things broke... [asp.net] on Topsy.com

Pingback from  Twitter Trackbacks for                 ASPNET #Weblog: Breaking Changes in Asp.Net 4: I upgraded an app to .net just for fun and a bunch of things broke...         [asp.net]        on Topsy.com

# re: Breaking Changes in Asp.Net 4

Thursday, May 06, 2010 8:11 AM by joelvarty

Not true, zoldello, with VS 2008 I was able to update my app from 2.0 to 3.5 without and changes whatsoever.  Understandably, the underlying runtime was the same for .net 2 and 3.5, but the point is that breaking changes should be more front and center as part of the upgrade process.  Also, if you were to look at the article I referred to, workarounds are available for most of the breaking changes.

Leave a Comment

(required) 
(required) 
(optional)
(required)