Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / Visual Studio.NET / IDE / February 2005

Tip: Looking for answers? Try searching our database.

Use VS.NET 2003 to target/use framework 1.0

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Peter Row - 04 Feb 2005 09:56 GMT
Hi,

I just started on a different project that requires me to use VS.NET 2002
instead of VS.NET 2003 because the client base has hundreds (maybe
thousands) of framework 1.0 installs.

However 2002 is like a dam with a crack in it - it is possible for it to
leak
memory up to 260MB with me never having run the (windows) application
once just with the 3-project solution open. All of which causes massive
slowdown on a 512MB machine which is also running a SQL Server
amongst other things for development.

Then, as your probably all aware, there are all the other niggling little
bugs.

So to conclude is there any way for me to use VS.NET 2003 such that
it will actually compile code to run against version 1.0 of the framework
INSTEAD OF 1.1, for this single application only?

Regards,
Peter
Scott M. - 04 Feb 2005 13:57 GMT
Open the project in 03, right click on the project in the Solution Explorer
and choose properties.  Then, choose the "Build" category and click the
"Change" button at the bottom.

> Hi,
>
[quoted text clipped - 18 lines]
> Regards,
> Peter
Carlos J. Quintero [.NET MVP] - 04 Feb 2005 15:03 GMT
Notice that is a big dangerous, because that only changes the app.config to
allow the execution of the app on .NET Framework 1.0 instead of the default
.NET Framework 1.1 of VS.NET 2003, but since VS.NET 2003 ALWAYS uses and
compiles against .NET Framework 1.1 and can not use .NET Framework 1.0, if
you use some feature of 1.1 not present in 1.0 it won?t be detected at code
or compilation time but at run-time when tested on a machine with .NET
Framework 1.0 alone... so, if you want to play safe, you have to use VS.NET
2002.

Signature

Carlos J. Quintero

MZ-Tools 4.0: Productivity add-ins for Visual Studio .NET
You can code, design and document much faster.
http://www.mztools.com

> Open the project in 03, right click on the project in the Solution
> Explorer and choose properties.  Then, choose the "Build" category and
> click the "Change" button at the bottom.
Peter Row - 07 Feb 2005 09:21 GMT
Hi,

Thanks for the warning.
Curse, blast and mega-annoyance!%&:

MS if you are reading this:
RELEASE A PATCH FOR THE VS.NET 2002 IDE

Regards,
Peter
> Notice that is a big dangerous, because that only changes the app.config
> to allow the execution of the app on .NET Framework 1.0 instead of the
[quoted text clipped - 8 lines]
>> Explorer and choose properties.  Then, choose the "Build" category and
>> click the "Change" button at the bottom.

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.