There's a blog post on targeting both Whidbey and .Net 1.1 from the same build here: http://blogs.msdn.com/jomo_fisher/archive/2004/10/01/236879.aspx
I'm not sure about targeting both 1.0 and 1.1 from VS.Net 2003 (though ISTR that it's possible, if hackish; there are almost certainly component vendors doing this). Microsoft's official word[1] is that this is under serious consideration for the release after Whidbey; it *will not* be in VS.Net 2005. [1] http://lab.msdn.microsoft.com/ProductFeedback/viewFeedback.aspx?feedbackid=f97f495f-f125-4f9e-9e25-b6f9dd564565 On Mon, 7 Feb 2005 08:00:13 +0100, Chakravarty, Sarvajith <[EMAIL PROTECTED]> wrote: > Hi Guys, > > I have downloaded MS enterprise library which is probable targetting > Microsoft .NET Framework version 1.1 and requires Microsoft Visual > Studio .NET 2003 development system. > > But I don't have Visual Studio .NET 2003 development system and have > installed 2005. > Though it converted the project, I still have a few unsolved compilation > errors. > > Is it possible to target .NET Framework version 1.1 from 2005 either > selectively for the project or for all proj from 2005 without having to > install visual studio 2003? > > Thanks and appreciate for your help! > > Thanks, > Sarvajith > > =================================== > This list is hosted by DevelopMentor� http://www.develop.com > > View archives and manage your subscription(s) at http://discuss.develop.com > -- Eric Means [EMAIL PROTECTED] http://www.randomtree.org/eric/ =================================== This list is hosted by DevelopMentor� http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
