Developing .NET Enterprise Applications

1. Front Matter

   Pages i-xxii

   PDF

2. Introducing .NET and Enterprise Architecture

   • John Kanalakis

   Pages 1-21

3. Accessing Data in ADO.NET

   • John Kanalakis

   Pages 23-69

4. Using Networking Directory Services

   • John Kanalakis

   Pages 71-94

5. Applying Reliable Messaging

   • John Kanalakis

   Pages 95-128

6. Integrating Mail Services

   • John Kanalakis

   Pages 129-149

7. Automating Business Processes

   • John Kanalakis

   Pages 151-176

8. Building Web Applications

   • John Kanalakis

   Pages 177-210

9. Developing Desktop Applications

   • John Kanalakis

   Pages 211-257

10. Using XML and web Services

    • John Kanalakis

    Pages 259-300

11. Integrating Reporting Services

    • John Kanalakis

    Pages 301-332

12. Deploying .NET Applications on Wireless Devices

    • John Kanalakis

    Pages 333-376

13. Integrating .NET Applications

    • John Kanalakis

    Pages 377-413

14. Understanding .NET Security and Cryptography

    • John Kanalakis

    Pages 415-441

15. Installing .NET Applications

    • John Kanalakis

    Pages 443-465

16. Back Matter

    Pages 467-504

    PDF

APPLICATION DEVELOPMENT IS USUALLY faced with several critical factors: time to market, ever-increasing quality, and cost of development. Time to market is critical in that any project that an individual or company may have in mind is probably already in the works elsewhere. When that is the case, everything comes down to being the first to deliver . . . even if it falls short. A Gartner Research study showed that competing products offering similar features will take the most mar­ ket share if released sooner. The study further added that the product released first, even with fewer features, typically builds market share faster. The lesson of that study is that it is important to release a 1. 0 version of a new product concept as quickly as possible and then follow up with feature add-ons over time. Product consistency and quality are also critical to the success of products making their debut. Applications with modules that look differently can under­ mine the application user's confidence in the product. The lower their confidence in the application, the less they use the product and come to depend upon it. The same can be said at the code level. The more modules that are implemented con­ sistently, the easier different developers can step in to investigate and resolve problems. Cost of development is often measured by productivity, or how much code is created to accomplish specific application tasks.

• .NET
• .NET framework
• C#
• Deployment
• Desktop
• Enterprise Applications
• Scala
• Web Services
• XML
• databases
• design
• language
• security
• web applications

From the reviews:

"Developing .NET Enterprise Applications is a complete guide to building a scalable enterprise application using .NET technologies. Other available books deeply describe individual Framework components … but none tie all the technologies into a single scalable application." (DevDorado, Issue 3, 2003)

A bio is not available for this author.

Policies and ethics