|
 
If you find an article here that helps, be sure to use the MSDN response
poll to say so. Thanks.
MSDN Online Articles
Migrating Code and Concepts from ADO "Classic" to ADO.NET
ADO.NET is becoming the new standard for data access, but what about all of that
COM-based ADO code you wrote over the last five years or so? Learn more about
design choices and decision points for migration.
Contents:
Why Aren't Folks Switching to
Visual Studio .NET?
Why Should Developers Switch to
.NET?
Can You Keep Your COM-based ADO
Code?
Converting Objects or
Operations?
Converting ADOc to ADO.NET at
the Object Level
Converting ADOc to ADO.NET
Operations
Conclusion
Related Books |
Using Secure Sockets Layer (SSL) for SQL Server 2000 Reporting Services
Creating an SSL Certificate to ensure your confidential reports remain
confidential. This is an essential step when working with SQL Server Reporting
Services--regardless of the version.
Written for our 5-star book "Hitchhiker's Guide to SQL Server 2000 Reporting
Services" (Addison Wesley) by Peter Blackburn and Bill Vaughn in February 2004.
Experiment with the security solutions presented here using SSL for SQL Server
2000 Reporting Services before implementing security on your network.
Managing an @@Identity Crisis
Discusses a strategy for returning newly created Identity values after the
INSERT is executed. Letting SQL Server generate Identity values might make your
job harder if you don't know how to retrieve the new Identity values.
Weaning Developers from the CommandBuilder
Examines the drawbacks of the ADO.NET CommandBuilder, and shows how to use the
Visual Studio .NET DataAdapter Configuration Wizard to write your own Command
queries.
Retrieving the Gazoutas: Understanding SQL Server Return Codes and Output
Parameters
Discusses how to capture, interrupt, and handle resultsets and rowsets, as well
as the extra information that they return when executing a Microsoft SQL Server
query.
.NET Data Access Architecture Guide (Building Distributed Applications)
(Bill collaborated on this article) Get guidelines for implementing an
ADO.NET-based data access layer in a multi-tier .NET application, so you can
choose the most appropriate approaches and techniques.
|