must I upgrade asp.net to 2.0 to access SQL 2005?

[HK]

I have ASP.NET 1.1 websites. They will need to access a SQL 2005 database.
Do I have to upgrade the whole web projects to ASP.NET 2.0 in order for them
to access SQL 2005? If so, anyone have any good URLs for upgrading 1.1
websites to 2.0? I'm really worried about crashing the current websites if
I do a quick conversion to 2.0, but I don't have much time before needing to
access SQL 2005.

 

[David Browne]

I have ASP.NET 1.1 websites. They will need to access a SQL 2005 database.
Do I have to upgrade the whole web projects to ASP.NET 2.0 in order for
them
to access SQL 2005? . . .

No. .NET 1.1 Apps of all kinds can access SQL Server 2005.

David

 

[Gabriel Magaña]

Write a little app in asp.net 1.1 (vs 2003) to test to see if you can log
into the 2005 DB... I do believe I at one point had 1.1 apps accessing
sql2005, but that was for a short time.

Whatever you do, DO NOT convert your web sites to vs2005 in a hurry, MS did
an awful job on asp.net web site updates. Web project conversions need to
be well-planned, and you may need to correct/prepare your projects for
conversion before you even try to convert.

There are some docs that outline the conversion process, you may need to
re-arrange your projects, and there is also an updated conversion tool that
does not come with VS2005 (search for all of these on the web). If you have
things like a web project referencing assemblies on another web project, and
some other stuff like that will break the upgrade. Take your time on
upgrading non-trivial projects.

Your much better off getting your 1.1 web sites logging into sql2005...

 

[JT]

ASP.NET doesn't access SQL Server; but rather it interfaces with ADO.NET,
which is a wrapper for the OLEDB Provider, which accesses the database. You
will probably need to download the latest version of MDAC (Microsoft Data
Access Components).
http://www.microsoft.com/downloads/...E3-C795-4B7D-B037-185D0506396C&displaylang=en
For the most common cases, the DSN will be similar to that for connecting to
SQL Server 2000.
http://www.connectionstrings.com/

 

[Learnicus]

Absolutely do not "upgrade" to ASP.Net 2.0 without doing some major level of
reading. MS has completely cocked this up and in some very important
respects ASP.Net 2.0 may as well be from mars.

Lenny

 

[David Browne]

ASP.NET doesn't access SQL Server; but rather it interfaces with ADO.NET,
which is a wrapper for the OLEDB Provider, which accesses the database.
You will probably need to download the latest version of MDAC (Microsoft
Data Access Components).
http://www.microsoft.com/downloads/...E3-C795-4B7D-B037-185D0506396C&displaylang=en
For the most common cases, the DSN will be similar to that for connecting
to SQL Server 2000.
http://www.connectionstrings.com/

Although accessing SQL through OleDB is possible, the .NET SqlClient is the
preferred method, and doesn't use any of the MDAC components.

And a DSN is only for ODBC.

David

 

[JT]

Meant to say connection string instead of DSN.

Although accessing SQL through OleDB is possible, the .NET SqlClient is
the preferred method, and doesn't use any of the MDAC components.

And a DSN is only for ODBC.

David