1.1 framework

G

Gabriele G. Ponti

Visual Studio .NET 2002 doesn't support the .NET Framework 1.1, you have to
upgrade.
 
S

Sam Gentile [MVP - C#/.NET]

This is completely incorrect. You can target multiple versions of the
framework and force an app to use either version through the use of Version
Policy files for assemblies.

For a complete discussion of this please see
http://www.3leaf.com/resources/articles/SBS.aspx

--
--------------------------------------------------------------
Sam Gentile [C#/.NET MVP]
..NET Blog http://samgentile.com/blog/
MSDN Column:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dndotnet/html/bridge.asp
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
---------------------------------------------------------------
 
H

HB

after ver. 1.1 framework, I can C that the ver 1 framework is the current
framework ( from the Help->about dialog)

How Can I enforce framework 1.1 to be in use instead of the old one?

Thanks
 
P

Patrick O'Gorman

Sam, could you please elaborate. The originator seems to be having trouble
targeting 1.1 from vs.net 2002. if this is not the case then you are
correct. from 2003 you can target 1.0 or 1.1 but i do not see how you can
target 1.1 from 2002.

please explain. your link does not address this particular issue from what
i have seen.

Sam Gentile said:
This is completely incorrect. You can target multiple versions of the
framework and force an app to use either version through the use of Version
Policy files for assemblies.

For a complete discussion of this please see
http://www.3leaf.com/resources/articles/SBS.aspx

--
--------------------------------------------------------------
Sam Gentile [C#/.NET MVP]
.NET Blog http://samgentile.com/blog/
MSDN Column:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dndotnet/html/bridge.asp
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
---------------------------------------------------------------
Patrick O'Gorman said:
as far as i know you cannot target 1.1 with 2002. you have to upgrade.
 
P

Patrick O'Gorman

ok....let me be more clear...you can target the 1.1 via an app compiled for
1.0 by altering config file... does this also allow you to debug an app via
vs 2002 using 1.1??

Sam Gentile said:
This is completely incorrect. You can target multiple versions of the
framework and force an app to use either version through the use of Version
Policy files for assemblies.

For a complete discussion of this please see
http://www.3leaf.com/resources/articles/SBS.aspx

--
--------------------------------------------------------------
Sam Gentile [C#/.NET MVP]
.NET Blog http://samgentile.com/blog/
MSDN Column:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dndotnet/html/bridge.asp
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
---------------------------------------------------------------
Patrick O'Gorman said:
as far as i know you cannot target 1.1 with 2002. you have to upgrade.
 
S

Sam Gentile [MVP - C#/.NET]

Your original question was:
I can C that the ver 1 framework is the
The answer to that is configuration files and versioning policies. The chart
in the article shows this:
Application compiled against
Frameworks Installed
Outcome

1.0 Framework




1.0 only
Runs against the 1.0 Framework

1.0 and 1.1
Runs by default against the 1.0 Framework. Can be directed to use the
1.1 Framework instead via a configuration file.

1.1 only
Runs by default against the 1.1 Framework. There are no warnings that
the app is running against a different version of the Framework than it was
compiled against.


1.1 Framework




1.0 only
Fails to run, with an error, unless a configuration file is included
that points to the 1.0 runtime.

1.0 and 1.1
Runs by default against the 1.1 Framework. Can be directed at the 1.0
Framework via a configuration file.

1.1
Runs against the 1.1 Framework .



I don't know if your question is what you wrote and whether it's really how
do I force VS.NET 2002 to use 1.1 of the framework? Because if the question
is what you wrote, the answer is above. *Any* application compiled against
the 1.0 framework automatically gets uplifted to run by default against the
1.1 framework if 1.1 in installed and 1.0 if both are installed. You can
direct it to use 1.0 by changing the configuration file with:
<startup>

<supportedRuntime version="v1.1.4322"/>

<supportedRuntime version="v1.0.3705"/>

<requiredRuntime version="v1.0.3705"/>

</startup><runtime>


If this isn't your question, please write the exact question so we don't
have to guess. I don't believe you can force VS.NET 2002 to use 1.1 but why
should you? You shouldn't be using VS.NET 2002 and 1.0 of the framework
anymore. The upgrade to 2003 is only $29 and been available since last
February.



--
--------------------------------------------------------------
Sam Gentile [C#/.NET MVP]
..NET Blog http://samgentile.com/blog/
MSDN Column:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dndotnet/html/bridge.asp
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
---------------------------------------------------------------
Patrick O'Gorman said:
ok....let me be more clear...you can target the 1.1 via an app compiled for
1.0 by altering config file... does this also allow you to debug an app via
vs 2002 using 1.1??

Sam Gentile said:
This is completely incorrect. You can target multiple versions of the
framework and force an app to use either version through the use of Version
Policy files for assemblies.

For a complete discussion of this please see
http://www.3leaf.com/resources/articles/SBS.aspx

--
--------------------------------------------------------------
Sam Gentile [C#/.NET MVP]
.NET Blog http://samgentile.com/blog/
MSDN Column:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dndotnet/html/bridge.asp
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
 
S

Sam Gentile [MVP - C#/.NET]

This MSDN article
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnnetdep/html/sidexsidenet.asp
should also be helpful.

HTH,

--
--------------------------------------------------------------
Sam Gentile [C#/.NET MVP]
..NET Blog http://samgentile.com/blog/
MSDN Column:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dndotnet/html/bridge.asp
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
---------------------------------------------------------------
Patrick O'Gorman said:
ok....let me be more clear...you can target the 1.1 via an app compiled for
1.0 by altering config file... does this also allow you to debug an app via
vs 2002 using 1.1??

Sam Gentile said:
This is completely incorrect. You can target multiple versions of the
framework and force an app to use either version through the use of Version
Policy files for assemblies.

For a complete discussion of this please see
http://www.3leaf.com/resources/articles/SBS.aspx

--
--------------------------------------------------------------
Sam Gentile [C#/.NET MVP]
.NET Blog http://samgentile.com/blog/
MSDN Column:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dndotnet/html/bridge.asp
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
 
P

Peter van der Goes

Sam Gentile said:
Your original question was:
If this isn't your question, please write the exact question so we don't
have to guess. I don't believe you can force VS.NET 2002 to use 1.1 but why
should you? You shouldn't be using VS.NET 2002 and 1.0 of the framework
anymore. The upgrade to 2003 is only $29 and been available since last
February.
Unfortunately, the $29 upgrade expired on September 30, 2003.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top