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.
We have old .net 1.1 project that is using a third party component. Aparently that component is not working properly with new requirements, and there is no support from the provider. Provider proposed to use new component that is working properly. The problem is that this component requires .net 2.0.
The project is big and it will be costly to move this project to 2.0.
What other alternatives we can have? How 1.1 assembly can call 2.0 assembly?
.NET 1.1 can’t load .NET 2.0 assemblies, because the internal format changed. Your app will basically think that the assembly isn’t a .NET assembly.
Long term, it would be a good idea to update your application to use .NET 2.0 (if not something newer, since there are multiple versions of .NET since 2.0 now). However, if that is not an option, you could create a .config file for your executable, and tell the CLR to always use .NET 2.0 when running your app. This should allow for the .NET 2.0 assembly to load, however any breaking changes between .NET 1.1 and 2.0 that your app makes use of will cause errors.