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 / .NET Framework / Setup / March 2004

Tip: Looking for answers? Try searching our database.

visual studio 2002 not recognizing framework 1.1

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Mad Scientist Jr - 01 Mar 2004 14:07 GMT
I have an ASP.NET project developed on one machine in Vis. Studio
2003, and moved it to an older machine that has Vis. Studio 2002. This
older machine has been upgraded with the 1.1 framework, as well as all
the latest MS service XP and .NET service packs. I created a new
ASP.NET project on the older machine, and imported all the .ASPX, .VB
files - but when it compiles I get errors like:

'SelectedValue' is not a member of
'System.Web.UI.WebControls.DropDownList'.
'HasRows' is not a member of 'System.Data.SqlClient.SqlDataReader'.

I assume those control properties are new in framework 1.1 ?
How can I get Vis Studio .NET 2002 to recognize these new 1.1
properties?
Is the project defaulting to framework 1.0 somehow ?
How can I get Vis Sutdio .NET 2002 to use framework 1.1 ?

Thanks in advance...
Gary Milton - 09 Mar 2004 18:06 GMT
I'm not sure that VS.NET can be set to a use a version of the framework which didn't even exist when VS.NET 2002 was released but as I no longer have VS.NET 2002 on my machine I can't actually test this out

However, looking at it logically, my current installation of VS.NET 2003 can be set it to work with either version 1.1, version 1.0 or both versions of the framework but there is no option to make it work with any possible future versions of the framework.  I would assume that if a newer framework version was released then a new version of VS.NET would also be released at the same time

Can you not just upgrade the older machine to VS.NET 2003

Gary
Andrew H [MSFT] - 31 Mar 2004 00:02 GMT
Visual Studio .NET 2002 is built on the .NET Framework 1.0, while Visual
Studio .NET 2003 is built on the .NET Framework 1.1.  While the 1.0 and 1.1
Framework can exist side-by-side on a single machine, VS cannot be
reconfigured to use a different version of the Framework than the one it
natively supports.

I recommend that you upgrade your machine to VS 2003, to save you the
headache of attempting to back-port your project to an older platform.

Andrew [MSFT]
Signature

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note:  For the benefit of the community-at-large, all responses to this
message are best directed to the newsgroup/thread from which they
originated.

--------------------

>From: usenet_daughter@yahoo.com (Mad Scientist Jr)
>Newsgroups: microsoft.public.dotnet.framework.setup
[quoted text clipped - 20 lines]
>
>Thanks in advance...
Mad Scientist Jr - 31 Mar 2004 20:58 GMT
upgraded to 2003, and am glad i did.
the only thing i can say bad about it is,
pooh on ISPs that no longer support the 1.0 framework!

> Visual Studio .NET 2002 is built on the .NET Framework 1.0, while Visual
> Studio .NET 2003 is built on the .NET Framework 1.1.  While the 1.0 and 1.1
[quoted text clipped - 30 lines]
> >
> >Thanks in advance...

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.