I am developing an Arctools .NET 3.5 C# DLL to be loaded by a .NET 4.0 application. Will this cause problems?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I am developing an Arctools .NET 3.5 C# DLL to be loaded by a .NET 4.0 application. Will this cause problems?
Yes that should work just fine.
We had several DLLs written in c# on .NET v2.0 and deployed to v3.5 without any issues. The same has played out for v3.5 to v4.0. The side-by-side execution in .NET combined with the v3.5 information stored within your DLL when it compiles is what enables this to happen. You should always try it anyway in a test environment to ensure your v3.5 DLL is not calling into any obselete APIs that are breaking changes with v4.0. If your v3.5 DLL us using pinvoke or other similar methods to call into the Windows API directly, you may want to run specific tests there to ensure those still work as expected.