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 have a project with few dlls. I would like to change one of them to framework 4.0, but not the other ones. The result will be that a framework 2.0 dll is using a framework 4.0 dll.
Is that ok, or problematic?
Thanks.
No – a project which targets .NET 2 can’t refer to a library targeting .NET 4. Imagine you tried to deploy it on a machine which only supported .NET 2 – you couldn’t actually use your .NET 2 assembly anyway, so what’s the point of making it target .NET 2 in the first place?
It makes sense to target a .NET 2 library from a .NET 4 project, but not the other way round.