In-Depth

Books: Master C# Database Programming

Database Programming with C# explains the essentials of database programming to those familiar already with C#. Learn to exploit the VS.NET IDE to access data, and more.

There's no doubt C# is here to stay. Countless organizations and individuals are investing their time and money into mastering this new standard language, and as with most languages, understanding how to access data is a requirement in becoming a proficient application developer. Carsten Thomsen's Database Programming with C# helps shed some light on this foundational topic.

The book is divided into three sections. The first is a brief introduction to C# itself. The second part comprises the heart of the book; Thomsen covers high-level database programming concepts, including how to use ADO.NET in both a connected and disconnected state, how to use the Visual Studio IDE to help access data, and how to manage data exceptions. The book centers on using SQL Server and details the use of stored procedures, views, and triggers. Thomsen also spends time demonstrating how to connect to hierarchical databases, such as Active Directory, and he provides insight into working with Microsoft Message Queue Server.

The third section of the book uses a sample application to give you insight into data access with C#. Thomsen provides an appendix with further information on the use of XML with SQL Server 2000.

Overall, this book has a lot of breadth, and is great for those who are fluent already in C# and have little to no experience with database programming.


Database Programming with C#
by Carsten Thomsen
Apress
ISBN: 1590590104
Price: $54.95
Quick Facts: Covers a wide range of topics, including basic consumption of ADO.NET, accessing LDAP data, working with message queues, creating data wrappers, and using data-bound controls.
Pros: Provides introductory information on many data-access subjects; covers the complete spectrum of data-access techniques.
Cons: Not written for seasoned developers or those looking for data-access design-pattern information. Doesn't cover many different databases, such as DB2 or Oracle.

About the Author

Joel Semeniuk is a founder of Imaginet Resources Corp., a Canada-based Microsoft Gold Partner. Currently, Joel is also serving as an Executive VP of Agile Project Management Tools at Telerik. He is also a Microsoft Regional Director and MVP Microsoft ALM, with a degree in Computer Science. With more than 18 years of experience, Joel specializes in helping organizations around the world realize their potential through maturing their software development and information technology practices. Joel is passionate about Application Lifecycle Management tooling, techniques and mindsets, and regularly speaks at conferences around the world on a wide range of ALM topics.

comments powered by Disqus

Featured

  • Compare New GitHub Copilot Free Plan for Visual Studio/VS Code to Paid Plans

    The free plan restricts the number of completions, chat requests and access to AI models, being suitable for occasional users and small projects.

  • Diving Deep into .NET MAUI

    Ever since someone figured out that fiddling bits results in source code, developers have sought one codebase for all types of apps on all platforms, with Microsoft's latest attempt to further that effort being .NET MAUI.

  • Copilot AI Boosts Abound in New VS Code v1.96

    Microsoft improved on its new "Copilot Edit" functionality in the latest release of Visual Studio Code, v1.96, its open-source based code editor that has become the most popular in the world according to many surveys.

  • AdaBoost Regression Using C#

    Dr. James McCaffrey from Microsoft Research presents a complete end-to-end demonstration of the AdaBoost.R2 algorithm for regression problems (where the goal is to predict a single numeric value). The implementation follows the original source research paper closely, so you can use it as a guide for customization for specific scenarios.

  • Versioning and Documenting ASP.NET Core Services

    Building an API with ASP.NET Core is only half the job. If your API is going to live more than one release cycle, you're going to need to version it. If you have other people building clients for it, you're going to need to document it.

Subscribe on YouTube