ADO.NET 2.0 and VS 2003

[Guest]

We would like ADO.NET 2.0 but don't want to upgrade to VS2005 yet. We would
like this for automatic failover in the connection string in ADO.NET 2.0 for
database mirroring. Does anyone know if we can upgrade to ADO.NET 2.0
without upgrading Visual Studio and how to go about doing this?

 

[clintonG]

Whenever I used to ask unrealistic questions my father would respond by
saying "people in hell want ice water."
Was he a smart @ss or what?

You'll have to use HomeSite or some other editor to write your ADO.NET 2.0
code and learn how to debug using a command line -- or -- why not consider
using Visual Web Developer 2005 Express for the time being noting I don't
know how that would work out but its a suggestion to consider ainna?

<%= Clinton Gallagher
METROmilwaukee (sm) "A Regional Information Service"
NET csgallagher AT metromilwaukee.com
URL http://metromilwaukee.com/
URL http://clintongallagher.metromilwaukee.com/

 

[Cowboy \(Gregory A. Beamer\)]

To bind to the UI? Not a chance in hell.

To bind to business? Possibly.
Without Visual Studio 2005? Once again, not a chance in hell.

You could, potentially, write an "interop" to use 2.0 assemblies in 1.x
code, but the amount of time kludging would be better spent selling
management on the switch.

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

***********************************************
Think Outside the Box!
***********************************************

 

[Sahil Malik [MVP C#]]

The automatic failover doesn't really work yet - even in ADO.NET 2.0/VS2005.
Maybe in the next SP it will.
Also, you are much better off upgrading to VS2005.

- Sahil Malik [MVP]
ADO.NET 2.0 book -
http://codebetter.com/blogs/sahil.malik/archive/2005/05/13/63199.aspx
__________________________________________________________

 

[Cor Ligthert [MVP]]

Jones,

Maybe you can build a windowService in Net 2.0 using one of the Express
editions.
(I don't know enough from those to know if that is possible)

However, that will probably cost you much more than going to VS2005.

Just a thought,

Cor