Could anyone advise on whether an app that targets .NET 3.0 will work on a users machine that has .NET 2.0 and 4.0 but not 3.0? The installers for 3.0 and 3.5 crash on this particular machine.
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.
Could anyone advise on whether an app that targets .NET 3.0 will work on a users machine that has .NET 2.0 and 4.0 but not 3.0? The installers for 3.0 and 3.5 crash on this particular machine.
.NET Framework 4.0 is separate and independent from .NET Framework 2.0/3.0/3.5 (all one framework. 2.0 is the base, full, framework. 3.0 and 3.5 are extensions to 2.0.).
/EDIT
I was curious and quickly tried myself. It actually depends on whether you
build your app against 3.0/3.5 and really use 3.0/3.5 specific stuff (for
instance Linq) in the end. If you don’t use it, then it will still work of course.
But if you do, then the user will see the Microsoft error reporting dialog.
As it seems there’s “no direct targeting .NET 3.0/3.5”, because it depends
on the targeted dependencies (project references).
But finally the answer should still be: “No, because you never know!”