[RESOLVED] My solution won't target the 2.0 framework

[FunkyDexter]

I've got solution that was developed in VS2005 and was going out on the .net 2.0 target framework fine. I recently updated the development enviroment to VS2008 and now it's asking for the .net 3.5 framework when it installs. I'm not sure why, there was nothing new added to the solution so it should still be fine with 2.0. It might be because I recreated the installer project but I'm not sure.

We tried upgrading the target machines (did a couple of test machines) to 3.5 but it causes us all sorts of problems. It causes other applications that still target 2.0 to fail with a bizarre error (see this thread for a discussion of that problem). It will also involve alot of legwork for the support department because the target machines don't have automatic updates switched on so they're going to have to update them all by hand.

I've therefore decided to reset the application to target the 2.0 framework but this doesn't seem to be working. I've gone through each project in the solution and made sure it's Advanced Compile Options have 2.0 set as the target framework. I've also checked the dependencies on the installer project and swapped the 3.5 dependency for 2.0. However, when I build the installer project and try to run the resulting msi on a 2.0 framework machine, I still get the pop up telling me it requires 3.5. Is there anything else I need to remove or is there a way I can investigate what is causing this dependency?

Thanks all.

[kmoorman]

FunkyDexter,

Does this article help you at all?

http://www.codeproject.com/KB/dotnet...romvs2008.aspx

Kerry Moorman

[FunkyDexter]

Absolutely spot on. My problem was exactly the one the author of that article resolved. I have to say, that's a really annoying glitch and I'd defy anyone to find that setting without knowing it was there in advance.

Thanks