Re: Can you target 1.1 with Visual Studio 2005

On 11/8/05 5:50, in article
2B46B44A-798B-4976-9AA0-08B8230EB373@xxxxxxxxxxxxx, "John Bailey"
<JohnBailey@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

> It is amazing how little Microsoft seems to know about their own build
> environments. This is the second time I have had to point out where a
> feature in Visual Studio 2003 is located. In Visual Studio 2003 under
> project settings in the Build settings there is a section for supported
> runtimes. There is a button to change the runtime. The default is 1.1, but
> you can change the setting to 1.0, 1.1 or both. So yes, Visual Studio 2003
> DOES support targetting 1.0, and I used this feature for about the first year
> this product was released. This feature was implemented in the app.config,
> but the result was still an app developed in Visual Studio 2003 that would
> run on the 1.0 framework.
>
> Of course you would have to limit your language and component use to that
> supported in the previous runtime, but is still preferable to having to take
> up a couple extra gig on your development machine to provide support for the
> 1.1 version of the framework.
>
>
> "Carlos J. Quintero [VB MVP]" wrote:
>
>> VS.NET 2003 could target only .NET Framework 1.1. Another thing is that it
>> could generate a .config file that would allow the executable to run on top
>> of .NET Framework 1.0 and even that was not recommended because you could
>> use inadvertently some functions only in .NET 1.1 and the app would crash
>> when run on .NET 1.0...
>>
>> So, the best approach is to install VS.NET 2003 and VS 2005 side by side,
>> they work fine, and no virtual machine is needed now that VS 2005 is no
>> longer a beta.
>>
>> --
>>
>> Best regards,
>>
>> Carlos J. Quintero
>>
>> MZ-Tools: Productivity add-ins for Visual Studio .NET, VB6, VB5 and VBA
>> You can code, design and document much faster.
>> Free resources for add-in developers:
>> http://www.mztools.com
>>
>> "John Bailey" <JohnBailey@xxxxxxxxxxxxxxxxxxxxxxxxx> escribió en el mensaje
>> news:BFB35D44-E062-4BD3-B495-484C0433F706@xxxxxxxxxxxxxxxx
>>> I am a consultant and I have some clients upgrading to .Net 2.0, but many
>>> clients that will continue to use 1.1 for some time. Can you target the
>>> 1.1
>>> version of the framework with Visual Studio 2005?
>>>
>>> Visual Studio 2003 did allow you to target the 1.0 version of the
>>> framework,
>>> so I would think that VS 2005 would provide similar support, but I am
>>> unable
>>> to determine how this would work. It seems like a very large footprint to
>>> have to have both Visual Studio 2003 and Visual Studio 2005 installed.
>>
>>
>>
Targeting output and fully supporting 1.0 are quite different things.
Although you can specify 1.0 target, when you are working in VS 2003, 1.1
framework is loaded and all intellisense comes from 1.1 framework. Hence you
have to be careful not to use something available in 1.1 but not in 1.0.
Now, 1.1 is not much different from 1.0 so the danger is low. 2.0 is
significantly different from 1.1, so one can use, say, generics, and then
get build errors because 1.1 target does not support them. Very confusing,
imho. Full cross version support requires the entire VS feature set to scale
back when you target 1.1 and do not offer any features available in 2.0.
Basically this means maintaining much larger code base and increasing QA
coverage significantly and managing two distinct code paths.

As I mentioned in my earlier post, cross-version support is important since
many customers request it, but it requires major CLR redesign. Eventually it
will happen, but obviously I don't know exactly when.

Thanks
Mikhail Arkhipov (Microsoft)
-- This post is provided 'AS IS' with no warranties and confers no rights

.