.net - Using .net3.5 assemblies and mixed-mode dlls on .net4 -


its in context of c++ application uses .net3.5 assemblies through mixed-mode (again targeted .net3.5) assemblies. native app explicitly loads .net assemblies.

i want know repercussions of using .net3.5 assemblies on .net4. found few links suggest using uselegacyv2runtimeactivationpolicy. there similar question answer suggests fine, following links make me think better recompile targeting .net4:

"...apps built versions 2.0, 3.0, , 3.5 can run on version 3.5, not work on version 4 or later." - on msdn

"some framework types have moved across assemblies between versions..." - in answer

"no idea. depends on application , apis uses. there breaking changes in .net 4 , application hitting one..." - in msdn forum answer

i want know repercussions of using .net3.5 assemblies on .net4.

in general, need set runtime activation policy force .net 4. means 3.5 assembly executed using clr 4 runtime, not clr 2 runtime.

for scenarios, things "just work". however, there edge cases there problems, there subtle changes (as you've linked) in 4.0 runtime.

in experience, these issues rare, , things typically work flawlessly. recommend thorough testing of 3.5 functionality if you're going use in 4.0 application, however, verify you're not hitting edge case problematic.


Comments

Popular posts from this blog

javascript - DIV "hiding" when changing dropdown value -

Does Firefox offer AppleScript support to get URL of windows? -

android - How to install packaged app on Firefox for mobile? -