c# - Assembly compiled in older .NET version running in newer .NET version, will behavior change? -


i have assembly compiled .net 3.5. cannot recompile in .net 4.5 since used in other applications still running .net 3.5. when use assembly in apps running .net 4.5 assembly treated if running in .net 4.5 instead of .net 3.5? have winforms app , webforms app both in .net 4.5. if there changes in behavior between .net 3.5 , .net 4.5, assembly return 4.5 results?

usually .net frameworks backward-compatible, executing assembly developed in .net 3.5 shouldn't problem on 4.5.

you should see: version compatibility in .net framework

the .net framework 4.5 backward-compatible applications built .net framework versions 1.1, 2.0, 3.0, 3.5, , 4. in other words, applications , components built previous versions of .net framework work on .net framework 4.5.

but there problems 1 mentioned in article :

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.

the best way make sure test cases pass after including dll 3.5.


Comments

Popular posts from this blog

Perl - how to grep a block of text from a file -

delphi - How to remove all the grips on a coolbar if I have several coolbands? -

javascript - Animating array of divs; only the final element is modified -