- WCF Multi-tier Services Development with LINQ
- WCF Multi-tier Services Development with LINQ
- Credits
- About the Author
- About the Reviewers
- Preface
- 1. SOA Service Oriented Architecture
- 2. WCF Windows Communication Foundation
- 3. Implementing a Basic HelloWorld WCF Service
- 4. Hosting and Debugging the HelloWorld WCF Service
- Hosting the HelloWorld WCF service
- Debugging the HelloWorld WCF service
- Summary
- 5. Implementing a WCF Service in the Real World
- 6. Adding Database Support and Exception Handling to the RealNorthwind WCF Service
- 7. Modeling a WCF Service with Service Factory
- What is the Service Factory?
- What are Guidance Packages?
- Preparing environments
- Differences between the December 2006 version and the February 2008 version
- Modeling the data contracts
- Modeling the service contracts
- Specifying the implementation technology for the models
- Generating source code
- Summary
- 8. Implementing the WCF Service with Service Factory
- 9. Introducing Language-Integrated Query (LINQ)
- What is LINQ
- Creating the test solution and project
- New data type var
- Automatic properties
- Object initializer
- Collection initializer
- Anonymous types
- Extension methods
- Lambda expressions
- Built-in LINQ extension methods and method syntax
- LINQ query syntax and query expression
- Built-in LINQ operators
- Summary
- 10. LINQ to SQL: Basic Concepts and Features
- ORM Object-Relational Mapping
- Comparing LINQ to SQL with LINQ to Objects
- LINQ to Entities
- Comparing LINQ to SQL with LINQ to Entities
- Creating LINQ to SQL test application
- Modeling the Northwind database
- Querying and updating the database with a table
- Deferred execution
- Deferred (lazy) loading versus eager loading
- Joining two tables
- Querying a view
- Summary
- 11. LINQ to SQL: Advanced Concepts and Features
- Calling a stored procedure
- Compiled query
- Direct SQL
- Dynamic query
- Inheritance
- Handling simultaneous (concurrent) updates
- Transactions support
- Adding validations to entity classes
- Debugging LINQ to SQL programs
- Summary
- 12. Applying LINQ to SQL to a WCF Service
- Creating the LINQNorthwind solution
- Modeling the data contracts
- Modeling the service contracts
- Generating the source code
- Modeling the Northwind database
- Implementing the data access layer
- Implementing the business logic layer
- Implementing the service interface layer
- Creating the host application and the test client
- Testing the GetProduct and UpdateProduct operations
- Testing concurrent update manually
- Testing concurrent update automatically
- Summary
- 13. Distributed Transaction Support of WCF
- Creating the DistNorthwind solution
- Testing the transaction behaviour of the WCF service
- Creating a client to call the WCF service sequentially
- Testing the sequential calls to the WCF service
- Wrapping the WCF service calls in one transaction scope
- Testing multiple database support of the WCF service
- Modifying the data access layer for the second database support
- Modifying the business logic layer for the second database support
- Modifying the service interface layer for the second database support
- Modifying the service host for the second database support
- Modifying the client for the second database support
- Testing the WCF service with two databases
- Enabling distributed transaction support
- Understanding distributed transaction support of a WCF service
- Testing the distributed transaction support of the WCF service
- Summary
In this chapter, we have used LINQ to SQL to communicate with the database in the data access layer, rather than use the raw ADO.NET APIs. We have used only one LINQ statement to retrieve product information from the database, and as you have seen, the updates with LINQ to SQL prove to be much easier than with the raw ADO.NET data adapters. Now, WCF and LINQ are combined together for our services, so we can take advantage of both technologies.
The key points covered in this chapter include:
- Service Factory can be used to model the service, and generate source code for the service interface layer projects.
- The data access layer should be modeled with LINQ to SQL designer.
- Business entity classes are all located inside the LINQ to SQL designer file, within the data access layer.
- The service interface layer and the business logic layer have to reference the data access layer in order to use the entity classes.
- Client applications still communicate with the service by exchanging messages. The LINQ to SQL objects are not exposed to clients, and the technology used in the data access layer is transparent to the clients.
- When updating the database in the data access layer, the updated entity has to be attached to a fresh LINQ to SQL
DataContextobject. - Concurrent updates are handled by LINQ to SQL naturally and easily. We just need to add one more column to the database, and LINQ to SQL will do the rest for us.
-
No Comment
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.