Geek Answers Handbook

.net (or what works?)

OK, this is a fairly broad question, but ... Is there a chart that says which version of the framework will work?

So, I think it slows down two questions

1 - are the frames 100% compatible back? I had a Framework 2.0 site to work with 1.1 DLLs, so I assume 2.0 will work with 1.1. Will this work for a windows application? Will it work for all versions?

2 - Is the framework ever compatible? I know that the opposite will not work, but will it work for any set of versions?

So, how important is it that the versions on your customers' computers are synchronized with your build version?

Is there a better assessment in the .net community how to get your software to work for most clients without forcing non-technical users to download new / different versions of the .net framework?

+5
source share
3 answers

As a rule, if the version of .NET X is installed side-by-side with the .NET version of Y, then the version of .NET X is not compatible (back or forward) with the version of .NET Y. We’ve used this rule for quite some time (since the release .NET 2.0) This is probably too safe for small applications, but it's better to be safe than sorry.

Here are some specific examples:

  • .NET 4.0 will not work properly with .NET 3.x or earlier applications
  • .NET 3.5 .NET 3.0 .NET 2.0, .NET 1.1
  • .NET 3.0 .NET 2.0, .NET 1.1

  • .NET 2.0 .NET 1.1

  • .NET 4.0 .NET 3.5/3.0/2.0 .NET 1.1

  • .NET 3.5, 3.0 2.0 .
  • .NET 3.5/3.0/2.0 .NET 1.1

, .

+4

IMO, "" :

  • 1.0
  • 1.1
  • 2.0, 3.0, 3.5 ( , - #)
  • 4,0

; , , , - .

.NET Windows - . (. http://support.microsoft.com/lifecycle/search/?alpha=.NET+Framework&sort=PN). , .NET. .

, 1.0 <supportedRuntime>: http://msdn.microsoft.com/en-us/library/w4atty68.aspx

, # , .

+1

, , . , - , .

, .NET Outlook.

0

More articles:


All Articles