What's the concern about using a later version of the framwork? Are your clients complaining about upgrading? Remember that you can have all 3 versions on the same machine without conflict. And, they are free, so cost shouldn't be an issue.
One suggestion: consider putting the code that requires a later framework into a webservice. Then, only the web server needs to have a specific version of the framework. HTH. On 12/21/05, Geoff Taylor <[EMAIL PROTECTED]> wrote: > One reason is that there are some pretty significant breaking changes in the > COM layer. The COMVisible attribute now works differently, and the > difference is particularly problematic with datasets. If you used datasets > in COM with .NET 1.1, your code probably won't run in .NET 2. > > (Or so I'm told.) > > Geoff > > > -----Original Message----- > > From: Discussion of advanced .NET topics. [mailto:ADVANCED- > > [EMAIL PROTECTED] On Behalf Of Ted Neward > > Sent: 21 December 2005 00:01 > > To: [email protected] > > Subject: Re: [ADVANCED-DOTNET] runtime framework targeting > > > > Why would an assembly want to change the version of the runtime it wants > > to > > target anyway? What's your use case here? I'm curious. > > > > Ted Neward > > Author, Presenter, Consultant > > Java, .NET, XML services > > http://blogs.tedneward.com > > =================================== > This list is hosted by DevelopMentor(r) http://www.develop.com > > View archives and manage your subscription(s) at http://discuss.develop.com > -- ______________________________ - David Lanouette - [EMAIL PROTECTED] =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
