Using old DLLs in C# .Net 4.0 -


this follow question asked yesterday problems using older dlls in visual c# 2010. have added configuration file , dll runs well. issue i'm having avoid having entire project run in legacy mode.

i have gone around creating new console project command line access functions need dll , read output in main project. way acts separate component, , don't have worry legacy mode affecting in main project.

the problem feel though slow down application in long run, , since developing needs fast, wondering if there approach doing this. mentioned in previous question, cannot rebuild dll in 4.0.

thanks,

pm

sounds misunderstand setting means. doesn't mean project "runs in legacy mode", exact opposite. .net 4.0 clr version used old dll setting. instead of new policy available in 4.0 allows run old version of clr. known in-process side-by-side feature. new policy doesn't support mixed-mode assemblies, that's why complained.

you really don't want run in separate .exe command line redirection, that's horrible. not slow, make app unreliable when 'host' process dies on unhandled exception main app doesn't notice. hard diagnose.


Comments

Popular posts from this blog

asp.net - repeatedly call AddImageUrl(url) to assemble pdf document -

java - Android recognize cell phone with keyboard or not? -

iphone - How would you achieve a LED Scrolling effect? -