>>You can check the version with:
>>
>> Environment.Version
>
>Ah. Cool.
>
>>As a general principal I think it's a good idea to speciify a specific version of the CLR that's required with your app and require that. It gets to be a hassle real quick if a version feature isn't supported especially since it's hard to tell what belongs to what version.
>
>Sounds like *very* sound advice. Is it possible for multiple versions of the .NET framework to co-exist? Alternatively, can an app built, say, for version 1.0 run under 1.1? Just thinking ahead to the day when I have a client with existing 1.0 apps, that doesn't want us to deliver a 1.1 app for fear of breaking their existing apps.

Yeah that works just fine. If you don't have signed controls the controls will automatically upgrade to the newer framework with no problems as long as behavior hasn't changed. All my 1.0 apps ran just fine on 1.1 when it first came out without recompiling.

Conversely if you go with backwards compatibility you can get good results with the features provided by VS.Net 2003 which sticks the appropriate redirects into the config file.

+++ Rick ---