.NET Enterprise Design with Visual Basic .NET and SQL Server 2000

Series
Sams
Author
Jimmy Nilsson  
Publisher
Sams Publishing
Cover
Softcover
Edition
1
Language
English
Total pages
355
Pub.-date
December 2001
ISBN13
9780672322334
ISBN
0672322331
Related Titles


Product detail

Product Price CHF Available  
9780672322334
.NET Enterprise Design with Visual Basic .NET and SQL Server 2000
61.30 approx. 7-9 days

Description

In this book you'll learn the most up-to-date information on .NET component services and T-SQL stored procedure programming, as well as the strategies for solving the key problems developers encounter when designing enterprise applications.

Table of Contents

(NOTE: Each chapter concludes with What's Next and a Reference Section.)

1. Introduction.

The History of COM, MTS/COM+, VB, and SQL Server. The New World of .NET. COM+ 1.5 Component Services. Visual Basic .NET. C#. SQL Server 2000.



2. Factors to Consider in Choosing a Solution to a Problem.

Type of Consumer. Physical Restrictions and Possibilities. Performance. Scalability. Other “-abilities” (Such as Maintainability, Reliability, Reusability, Testability, Debuggability, and Interoperability). Security. Farm- and Cluster-Enabling.



3. Testing.

A Short Introduction to Testing. Support for Automatic Testing with a Standardized Test Bed. Assertions. The Diagnose/Monitor Tool. Miscellaneous Tips. Evaluation of Proposals.



4. Adding Debugging Support.

Tracing. Error Logging. Reflection, Interception, and Attributes to Your Service. Configuration Data. Evaluation of Proposals.



5. Architecture.

Three Examples of Architectures. Sample Application: Acme HelpDesk. My Architecture Proposal: A .NET-Adjusted Version of DNA. New Concepts to Consider When Creating a New Architecture Today. Physical Partitioning. Proposals for Standardized Code Structures. Evaluation of Proposals.



6. Transactions.

Choosing a Transaction Technique. Transactions in the Proposed Architecture. A Flexible Transaction Design. New Possibilities to Consider with .NET. Tips on Making Transactions as Short as Possible. Tips on Decreasing the Risk of Deadlocks. Obscure Declarative Transaction Design Traps. Evaluation of Proposals.



7. Business Rules.

A Short Introduction to Business Rules. Location and Solutions of Business Rules. Proposal for Where to Locate Different Business Rules. Business Rule Tips. Evaluation of Proposal.



8. Data Access.

My Proposal for a Data Access Pattern. The Data Access Proposal in the Architecture. Saying More in Fewer Words When Calling Stored Procedures. Server-Side Caching. Dealing with Schema Changes. Evaluation of My Proposal.



9. Error Handling and Concurrency Control.

My Proposal for How to Handle Errors. Exceptions to Be Prepared For. Approaches to Concurrency Control for Disconnected Scenarios. Evaluation of Proposals.



Appendix A. Suggestions for Further Reading.


Index.

Back Cover

This book discusses factors and opinions developers should consider in order to create higher quality designs and applications. The author uses one large-scale business application throughout the book as the basis for all examples to clearly illustrate concepts being discussed.

Coverage also includes:

  • a variety of aspects about design in the world of .NET;
  • explanations of the business and data access layers of application design;
  • solutions for problems such as code structure, solid error trapping, and how to build in debugging support;
  • discussion of how to design larger projects with more robust systems and reusable components;
  • comparison of component solutions to stored procedure solutions.

Author

Jimmy Nilsson is the owner of the Swedish consulting company JNSK AB. He has been working with system development for 13 years (with VB since version 1.0) and, in recent years, he has specialized in component-based development, mostly in the Microsoft environment. He has also been developing and presenting courses in database design, object-oriented design, and so on at a Swedish university for six years. Jimmy is a frequent speaker at Fawcette and Wrox Conferences and has written numerous technical articles. Even so, he considers himself to be mainly a developer.