It doesn't go down like that, dude. Sorry.
You gotta get VS2005.
Open up your project/solution VS2005.
It'll "convert" to 2.0.
THen you compile, and hope nothing broke (deprecated calls perhaps).
..
AFter you do that, you make sure 2.0 framework is on the Server, and you
redeploy it.
..
It it ain't broke, don't fix it.
> how to force a .net application to use .net 2.0 ?
> this windows service is about 4 years old and im pretty sure is using
> .net 1.x runtime. Is there soem setting in the installer that says to use
> .net 2.0 instead of .net 1.0? this windows service is developed in visual
> studio 2002
Alvin Bruney [MVP] - 27 Oct 2007 02:45 GMT
Actually, it can work like that, well sort of.
You can add a configuration file with the appropriate configuration
elements, see http://msdn2.microsoft.com/en-us/library/a5dzwzc9.aspx. But
you need to be aware of the issues, see:
http://support.microsoft.com/default.aspx?scid=kb;en-us;556035.
As Sloan pointed out, your best bet (foolproof approach) is to recompile the
app in 2.0.

Signature
Regards,
Alvin Bruney
------------------------------------------------------
Shameless Author Plug
OWC Black Book 2nd Edition
Exclusively on www.lulu.com/owc
$24.99
> It doesn't go down like that, dude. Sorry.
>
[quoted text clipped - 20 lines]
>> .net 2.0 instead of .net 1.0? this windows service is developed in visual
>> studio 2002