this actually happens after a question I asked yesterday about problems using older DLLs in Visual C # 2010. I added a configuration file and the DLL works well. The problem I am facing is that I would like to avoid having my entire project run in legacy mode.
I got around this by creating a new console project with command line access to all the functions that I need from the DLL, and read the output in my main project. This way, it acts as a separate component, and I don’t have to worry about the obsolescence mode affecting anything in my main project.
The problem is that I feel that this will really slow down my application in the long run, and since what I am developing should be fast, I was wondering if there is another approach to this. As I mentioned in the previous question, I cannot rebuild the DLL in 4.0.
Thank,
PM
source
share