c# - .NET framework pre requisite -
hello friends need explanation regarding .net framework pre-requisite while installing published application in target machine.
as java downward compatible, mean if have installed java v1.6 , if application developed using java v1.5 (i mean classes , packages available in 1.5 used build appln.)
i sure application developed run installing latest or higher versions of jre or j2se.
similarly in case of .net platform suppose if develop application using .net framework 3.5 , in target machine have installed .net framework 4.0 (the latest) prompts install .net framework 3.5 why so?
the real time example have downloaded , tried installing mysql workbench , installed .net framework 4.0 still asks install .net framework 3.5 before running mysql installation.
my question .net framework downward compatible java or .net?
version compatibility in .net framework:
the .net framework 4 backward-compatible applications built .net framework versions 1.1, 2.0, 3.0, , 3.5. in other words, applications , components built previous versions of .net framework work on .net framework 4.
however, in practice, compatibility can broken seemingly inconsequential changes in .net framework , changes in programming techniques. example, performance improvements in .net framework 4 can expose race condition did not occur on earlier versions. similarly, using hard-coded path .net framework assemblies, performing equality comparison particular version of .net framework, , getting value of private field using reflection not backward-compatible practices. in addition, each version of .net framework includes bug fixes , security-related changes can affect compatibility of applications , components.
if application or component not work expected on .net framework 4, use following checklists.
for .net framework 2.0, 3.0, , 3.5 applications:
check .net framework 4 migration issues changes might affect application , apply workaround described.
if recompiling existing source code run on .net framework 4, or if developing new version of application or component targets .net framework 4 existing source code base, check what's obsolete in .net framework obsolete types , members, , apply workaround described. (previously compiled code continue run against types , members have been marked obsolete.)
if determine change in .net framework 4 has broken application, check runtime settings schema determine whether can use runtime setting in application configuration file restore previous behavior.
if encounter issue not documented, file microsoft connect bug , contact netfxcf@microsoft.com bug number.
Comments
Post a Comment