C# - different .NET framework versions

Question

Did anybody encounter portability issues when performing .NET runtime upgrade (e.g switching from 2.0 -> 3 -> 3.5 -> 4 -> 4.5)?

I couldn't find any proof for the fact that upgrading to a higher version of the runtime wouldn't affect the behavior of my application (I guess this should be so, but, well, there are always hidden caveats).

You can never prove a negative.

Preet Sangha
– Preet Sangha

2012-06-05 09:32:59 +00:00
Commented Jun 5, 2012 at 9:32 — Preet Sangha
– Preet Sangha, Commented Jun 5, 2012 at 9:32

Hiren Visavadiya · Accepted Answer · 2012-06-05 09:30:07Z

2

Refer following link: http://msdn.microsoft.com/en-us/library/ee941656.aspx

answered Jun 5, 2012 at 9:30

Hiren Visavadiya

4951 gold badge3 silver badges16 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

Botz3000 · Accepted Answer · 2012-06-05 09:35:58Z

1

There are always a few changes that could change the behavior of existing code, but these are in most cases rare edge cases and are kept to a minimum. You can find a list of breaking changes for recent releases of Visual Studio:

Visual C# 2012 RC Breaking Changes
Visual C# 2010 Breaking Changes
Visual C# 2008 Breaking Changes

answered Jun 5, 2012 at 9:35

Botz3000

39.8k8 gold badges107 silver badges128 bronze badges

Comments

Garrett Fogerlie · Accepted Answer · 2012-06-05 09:40:19Z

1

Some features may be deprecated and if you are jumping more than one update, the feature could be removed all together, causing a bit of hassle.

What's Obsolete in the .NET Framework

answered Jun 5, 2012 at 9:40

Garrett Fogerlie

4,4583 gold badges41 silver badges56 bronze badges

Collectives™ on Stack Overflow

C# - different .NET framework versions

3 Answers 3

Comments

Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

3 Answers 3

Comments

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related