book

Learning WCF

Name: Learning WCF
Author: Michele Leroux Bustamante
ISBN: 9780596554835

by Michele Leroux Bustamante

May 2007

Intermediate to advanced

610 pages

20h 14m

English

O'Reilly Media, Inc.

Read now

Unlock full access

Learning WCF
Dedication
A Note Regarding Supplemental Files
Forewords
Preface
Who This Book Is For
How This Book Is Organized
Chapters OverviewLabs and Code Samples
Assumptions About the Reader
System Requirements
Your Working Directory

Conventions Used in This Book
Comments and Questions
Safari® Enabled
Acknowledgments
1. Hello Indigo
1.1. Service Oriented Architecture
1.1.1. From OOP to SOA1.1.2. What Is a Service?1.1.3. Tenets of SOA1.1.3.1. Service boundaries are explicit1.1.3.2. Services are autonomous1.1.3.3. Clients and services share contracts, not code1.1.3.4. Compatibility is based upon policy1.1.4. Big SOA, Little SOA
1.2. WCF Services
1.3. Fundamental WCF Concepts
1.3.1. Message Serialization1.3.2. Services1.3.3. Hosting1.3.4. Endpoints1.3.5. Addresses1.3.6. Bindings1.3.7. Metadata1.3.8. Proxies1.3.9. Channels1.3.10. Behaviors
1.4. Creating a New Service from Scratch
1.4.1. Lab: Creating Clients and Services Programmatically1.4.1.1. Creating a new service1.4.1.2. Hosting a service1.4.1.3. Creating a proxy to invoke a service1.4.2. Assembly Allocation1.4.3. Defining a Service1.4.4. Hosting a Service1.4.5. Exposing Service Endpoints1.4.5.1. Addresses1.4.5.2. Bindings1.4.5.3. Contracts1.4.6. Creating a Client Proxy
1.5. Generating a Service and Client Proxy
1.5.1. Lab: Using Tools to Generate Clients and Services1.5.1.1. Using the WCF Service template1.5.1.2. Configuring service endpoints using the Service Configuration Editor1.5.1.3. Generating a proxy with Add Service Reference1.5.1.4. Creating a WCF Service Library1.5.1.5. Generating a proxy using the Service Model Metadata Utility1.5.2. Service TemplatesService Testing Tools1.5.3. ServiceModel Metadata Utility1.5.4. Service Configuration Editor1.5.5. ServiceModel Configuration1.5.6. ServiceHost Initialization1.5.7. Enabling Metadata Exchange1.5.8. Working with Behaviors1.5.8.1. Service behaviors1.5.8.2. Endpoint behaviors1.5.9. Proxy Initialization
1.6. Hosting a Service in IIS
1.6.1. Lab: Creating an IIS Host and Browsing Metadata1.6.1.1. Creating a WCF Service web site1.6.1.2. Browsing service metadata1.6.1.3. Exporting metadata for proxy generation1.6.2. Web Site Templates1.6.3. @ServiceHost Declarations1.6.4. Message-Based Activation1.6.5. Browsing and Exporting Metadata1.6.5.1. Browsing metadata1.6.5.2. Exporting metadata
1.7. Exposing Multiple Service Endpoints
1.7.1. Lab: Hosting Multiple Services and Sharing Types1.7.1.1. Implementing multiple contracts on a service1.7.1.2. Hosting two services with multiple contracts1.7.1.3. Consuming internal services using shared contracts1.7.1.4. Consuming external services with a generated proxy1.7.2. Implementing Multiple Contracts1.7.3. Hosting Multiple Services1.7.4. Proxy Generation for Multiple Contracts and Endpoints1.7.5. Proxy Initialization and Lifetime1.7.6. Sharing Service Contracts1.7.7. Duplicating Operations
1.8. Summary
2. Contracts
2.1. Messaging Protocols
2.1.1. SOAP2.1.2. WS*
2.2. Service Description
2.2.1. ServiceDescription2.2.2. WSDL2.2.3. WS-Policy2.2.4. WS-MetadataExchange
2.3. WCF Contracts and Serialization
2.4. Service Contracts
2.4.1. Lab: Designing a Service Contract2.4.1.1. Exploring service contract compatibility2.4.1.2. Customizing message parameters2.4.1.3. Modifying service operations and dealing with version tolerance2.4.2. Mapping Services to WSDL2.4.3. Designing Service Contracts2.4.3.1. ServiceContractAttribute2.4.3.2. OperationContractAttribute2.4.3.3. MessageParameterAttribute2.4.4. Versioning Service Contracts2.4.4.1. Versioning with contract inheritance2.4.4.2. Versioning with separate contracts2.4.4.3. Strict versus non-strict versioning
2.5. Data Contracts
2.5.1. Lab: Working with Data Contracts2.5.1.1. Creating a data contract2.5.1.2. Customizing data contract serialization2.5.1.3. Consuming data contracts at the client2.5.1.4. Exploring version tolerance2.5.2. Mapping Data Contracts to XSD Schema2.5.3. Designing Data Contracts2.5.3.1. DataContractAttribute2.5.3.2. DataMemberAttribute2.5.3.3. EnumMemberAttribute2.5.3.4. CollectionDataContractAttribute2.5.4. Mapping CLR Namespace to Schema Namespace2.5.5. Configuring Known Types2.5.5.1. KnownTypeAttribute2.5.5.2. ServiceKnownTypeAttribute2.5.5.3. Declarative known types2.5.6. Versioning Data Contracts2.5.6.1. IExtensibleDataObject2.5.6.2. Explicit versioning2.5.6.3. Versioning flow diagrams2.5.7. Data Contracts As Operation Messages
2.6. Message Contracts
2.6.1. Lab: Controlling Message Serialization with Message Contracts2.6.1.1. Creating message contracts2.6.1.2. Implementing message contracts in a service2.6.1.3. Using proxies and message contracts2.6.2. Message Contracts and SOAP2.6.3. Designing Message Contracts2.6.3.1. MessageContractAttribute2.6.3.2. MessageBodyMemberAttribute2.6.3.3. MessageHeaderAttribute2.6.4. Client Message Contracts2.6.5. Versioning Message Contracts
2.7. Approaches to Serialization
2.7.1. Types Supporting Serialization2.7.2. Serialization Format2.7.2.1. Message Encoding2.7.2.2. DataContractFormatAttribute2.7.2.3. XmlSerializerFormatAttribute2.7.3. Applying the XmlSerializer2.7.3.1. Controlling serialization2.7.3.2. Proxy generation and the XmlSerializer2.7.4. Applying IXmlSerializable Types2.7.4.1. Implementing IXmlSerializable2.7.4.2. Supplying a schema
2.8. The Message Type
2.8.1. Lab: Working with Raw Messages2.8.1.1. Using untyped messages in the service contract2.8.1.2. Accessing message headers2.8.1.3. Extending the message type2.8.2. Untyped Messages and WSDL2.8.3. Working with the Message Type2.8.3.1. Creating messages2.8.3.2. Accessing message headers2.8.4. Filtering Messages
2.9. Summary
3. Bindings
3.1. How Bindings Work
3.1.1. Standard Bindings3.1.2. Binding Features3.1.3. Binding Elements3.1.4. Building the Channel Stack3.1.5. Web Service Protocols3.1.6. Bindings and Metadata3.1.7. Constraints on Binding Selection
3.2. Web Service Bindings
3.2.1. Lab: Exposing Web Services with BasicHttpBinding and WSHttpBinding3.2.1.1. Exposing multiple web service endpoints3.2.1.2. Adding a web reference for the legacy client3.2.1.3. Adding a service reference for the non-legacy client3.2.2. Choosing a Web Service Binding3.2.3. BasicHttpBinding Features3.2.3.1. BasicHttpBinding defaults3.2.3.2. Customizing BasicHttpBinding3.2.4. WSHttpBinding Features3.2.4.1. WSHttpBinding defaults3.2.4.2. Customizing WSHttpBinding3.2.5. MessageVersion3.2.6. Isolating SOAP 1.1 and SOAP 1.2 Endpoints
3.3. Connection-Oriented Bindings
3.3.1. Lab: Distributing Calls with NetNamedPipeBinding and NetTcpBinding3.3.1.1. Setting up the lab3.3.1.2. Moving from components to services3.3.1.3. Crossing machine boundaries3.3.2. Choosing a Connection-Oriented Binding3.3.3. NetNamedPipeBinding Features3.3.3.1. NetNamedPipeBinding defaults3.3.3.2. Customizing NetNamedPipeBinding3.3.4. NetTcpBinding Features3.3.4.1. NetTcpBinding defaults3.3.4.2. Customizing NetTcpBinding3.3.5. Calling Services In-Process3.3.6. Distribution of Services
3.4. One-Way and Duplex Communication
3.4.1. Message Exchange Patterns3.4.1.1. Request-reply3.4.1.2. One-way3.4.1.3. Duplex3.4.2. Working with Callbacks3.4.2.1. Duplex proxies3.4.2.2. DuplexChannelFactory<T>3.4.2.3. Callback instance3.4.2.4. Client endpoint3.4.3. Lab: Duplex Communications over TCP and HTTP3.4.3.1. Designing the callback contract3.4.3.2. Issuing callbacks3.4.3.3. Choosing a duplex-compatible binding3.4.3.4. Implementing the callback contract3.4.3.5. Issuing callbacks over WSDualHttpBinding3.4.3.6. Callbacks and one-way operations3.4.4. WSDualHttpBinding Features3.4.4.1. WSDualHttpBinding defaults3.4.4.2. Customizing WSDualHttpBinding3.4.5. Services and Callback References3.4.6. Callbacks and Concurrency
3.5. Large Message Transfers
3.5.1. Lab: Using MTOM to Handle Large Messages with Binary Data3.5.2. Lab: Enabling Streaming for Large File Transfers3.5.2.1. Streaming from the service3.5.2.2. Streaming from the client3.5.3. Handling Large Messages3.5.3.1. Controlling payload size3.5.3.2. Reducing memory consumption3.5.4. Message Size Quotas3.5.5. MTOM Encoding3.5.6. Streaming3.5.6.1. Designing a service contract for streaming3.5.6.2. Enabling streaming3.5.6.3. Who closes the stream?3.5.6.4. Alternatives to streaming
3.6. Custom Bindings
3.6.1. CustomBinding Features3.6.2. Creating a CustomBinding3.6.2.1. Binary encoding over HTTP3.6.2.2. SOAP 1.2 without addressing headers
3.7. Summary
4. Hosting
4.1. Hosting Features
4.2. ServiceHost
4.2.1. Initializing the ServiceHost4.2.2. Declarative Configuration4.2.3. Base Addresses4.2.4. ServiceHost and ServiceDescription4.2.5. Closing the ServiceHost4.2.6. Communication Events
4.3. Self-Hosting
4.3.1. Console Applications4.3.2. Windows Applications4.3.3. Windows Services
4.4. Hosting on the UI Thread
4.4.1. Windows Applications and UI Threads4.4.2. Synchronization Context4.4.3. ServiceHost Lifetime4.4.4. Lab: Working with a Windows Forms Host4.4.4.1. Configuring the ServiceHost4.4.4.2. Opening and closing the ServiceHost4.4.4.3. Calling services on a non-UI thread4.4.4.4. Calling services on the UI thread4.4.4.5. Preventing services from joining the UI thread4.4.5. Callbacks and the UI Thread4.4.6. UI Hosting Scenarios4.4.6.1. Coupling services to the host user interface4.4.6.2. Exposing a reusable service user interface4.4.6.3. Decoupling services from user interfaces
4.5. Hosting in a Windows Service
4.5.1. What Are Windows Services?4.5.1.1. Controlling service startup4.5.1.2. Runtime identities4.5.1.3. Recovery4.5.2. Creating and Installing Windows Services4.5.2.1. Extending ServiceBase4.5.2.2. Event log access4.5.2.3. Registering the Windows service4.5.2.4. Providing an installer4.5.3. Lab: Creating a Windows Service Host4.5.3.1. Creating a new Windows Service4.5.3.2. Handling start and stop events4.5.3.3. Creating a Windows service installer4.5.3.4. Generating the client proxy4.5.4. Considerations for WCF Services4.5.5. Windows Service Hosting Scenarios
4.6. Hosting in IIS 6.0
4.6.1. IIS Service Endpoints4.6.2. IIS 6.0 Hosting Architecture4.6.3. ASP.NET Compatibility Mode
4.7. IIS 7.0 and Windows Activation Service
4.7.1. WAS Hosting Architecture4.7.2. Installing IIS 7.0, WAS, and WCF Communications4.7.3. Configuring IIS 7.0 and WAS4.7.4. Hosting WCF Services with WAS
4.8. Choosing the Right Hosting Environment
4.9. Summary
5. Instancing and Concurrency
5.1. OperationContext
5.2. Instancing
5.2.1. PerCall Services5.2.2. PerSession Services5.2.2.1. Requiring sessions5.2.2.2. Session identifier5.2.2.3. Session lifetime5.2.2.4. Exception handling5.2.3. Singleton Services5.2.4. Lab: Controlling Service Instancing5.2.4.1. Working with PerCall services5.2.4.2. Working with sessions5.2.4.3. Working with singletons
5.3. Concurrency
5.3.1. Single Concurrency Mode5.3.2. Reentrant Concurrency Mode5.3.3. Multiple Concurrency Mode5.3.4. Custom Synchronization5.3.5. .NET Synchronization Techniques5.3.6. Asynchronous Proxies5.3.7. Lab: Protecting Shared Resources from Concurrent Access5.3.7.1. Generating an asynchronous proxy5.3.7.2. Allowing concurrent access to the singleton5.3.7.3. Adding manual synchronization with global locks5.3.7.4. Adding more granular synchronization for increased throughput
5.4. Instance Throttling
5.4.1. Throttling PerCall Services5.4.2. Throttling Sessions5.4.3. Throttling Singletons
5.5. Load Balancing and Failover
5.6. Summary
6. Reliability
6.1. Reliable Sessions
6.1.1. Configuring Reliable Sessions6.1.1.1. Standard bindings6.1.1.2. Custom bindings6.1.1.3. Requiring ordered delivery6.1.1.4. Client configuration6.1.2. How Reliable Sessions Work6.1.2.1. Session identifier6.1.2.2. Session lifetime6.1.2.3. Retry attempts6.1.2.4. Session throttling6.1.3. WS-ReliableMessaging Protocol6.1.3.1. Message flow6.1.3.2. CreateSequence6.1.3.3. CreateSequenceResponse6.1.3.4. SequenceAcknowledgement6.1.3.5. LastMessage6.1.3.6. TerminateSequence6.1.4. Lab: Working with Reliable Sessions6.1.4.1. Tracing reliable sessions messages6.1.4.2. Testing reliable session retries
6.2. Transactions
6.2.1. Transaction Management6.2.1.1. Two-phase commit protocol6.2.1.2. Durable versus volatile resource managers6.2.1.3. TransactionScope6.2.1.4. Lightweight Transaction Manager6.2.1.5. Kernel Transaction Manager6.2.1.6. Distributed Transaction Coordinator6.2.1.7. WS-AtomicTransaction and WS-Coordination protocols6.2.1.8. Enabling WS-AT6.2.2. Transactions and System Tiers6.2.3. Configuring WCF Transactions6.2.3.1. Enabling transaction flow6.2.3.2. Selecting a transaction protocol6.2.3.3. Transaction flow options6.2.3.4. Service operations and transactions6.2.3.5. Controlling IsolationLevel6.2.3.6. Transaction timeout6.2.3.7. Client configuration6.2.3.8. Transactions and sessions6.2.4. Lab: Configuring WCF Transactions6.2.4.1. Testing service calls without transactions6.2.4.2. Requiring client transactions6.2.4.3. Automating service transactions6.2.4.4. Rejecting client transactions
6.3. Queued Calls
6.3.1. MSMQ Overview6.3.1.1. Private and public queues6.3.1.2. Transactional queues6.3.1.3. Delivery failure6.3.1.4. Security6.3.1.5. MSMQ management console6.3.1.6. System.Messaging6.3.2. NetMsmqBinding Features6.3.3. Queued Service Contracts6.3.4. Durable Queues6.3.5. Transactional Queues6.3.5.1. Exactly once delivery6.3.5.2. Client transactions6.3.5.3. Queue-to-queue transactions6.3.5.4. Queued service transactions6.3.6. Transactions and Delivery Failures6.3.6.1. Delivery retries6.3.6.2. Time-to-live6.3.6.3. Poison messages6.3.6.4. Poison message queue6.3.6.5. Dead letter queues6.3.7. Security6.3.8. MsmqIntegrationBinding6.3.9. Lab: Creating a Queued Service6.3.9.1. Exposing an MSMQ endpoint6.3.9.2. Requiring MSMQ6.3.9.3. Testing offline messaging6.3.9.4. Testing exception handling
6.4. Summary
7. Security
7.1. WCF Security Overview
7.1.1. Security Policy7.1.2. Binding Security7.1.2.1. Default security settings7.1.2.2. Security mode7.1.2.3. Client credential type7.1.2.4. Advanced dettings7.1.3. Supplying Credentials7.1.3.1. Client credentials7.1.3.2. Service credentials7.1.4. Message Protection7.1.4.1. Protection level7.1.4.2. Algorithm suite7.1.5. Authentication, Authorization, and Identities7.1.5.1. ServiceSecurityContext7.1.5.2. Security tokens and authentication7.1.5.3. Role-based authorization7.1.5.4. Impersonation7.1.6. WCF Security Summary
7.2. Securing Intranet Services
7.2.1. Lab: Authenticating and Authorizing Windows Credentials7.2.1.1. Authenticating with Windows credentials7.2.1.2. Initializing the proxy with Windows credentials7.2.1.3. Applying Windows role-based permission demands7.2.2. NetNamedPipeBinding Security Features7.2.3. NetTcpBinding Security Features7.2.4. Windows Authentication and Authorization7.2.5. Windows Role-Based Security7.2.6. Windows Client Credentials
7.3. Securing Internet Services
7.3.1. Lab: Authenticating and Authorizing UserName Credentials7.3.1.1. Creating two service endpoints7.3.1.2. Generating the client proxy7.3.1.3. Configuring binding security7.3.1.4. Initializing proxies with UserName credentials7.3.1.5. Configuring ASP.NET authentication and authorization7.3.1.6. Applying custom role-based permission demands7.3.2. BasicHttpBinding Security Features7.3.3. WSHttpBinding Security Features7.3.4. Negotiation7.3.5. Secure Sessions7.3.6. ASP.NET Authentication and Authorization7.3.6.1. Configuring ASP.NET providers7.3.6.2. Custom password validators7.3.7. Custom Role-Based Security7.3.8. UserName Client Credentials
7.4. Working with Certificates
7.4.1. Understanding Certificates, Digital Signatures, and Encryption7.4.2. Signing and Encrypting Messages7.4.3. Service Certificates and Negotiation7.4.4. Certificate Authentication7.4.5. Certificate Authorization
7.5. Building a Claims-Based Security Model
7.5.1. Security Tokens and Claims7.5.2. AuthorizationContext7.5.3. Custom Claims7.5.4. Custom Authorization Policies7.5.5. Lab: Creating a Custom Authorization Policy7.5.5.1. Implementing IAuthorizationPolicy7.5.5.2. Authorizing custom claims7.5.5.3. Applying custom security extensions
7.6. Exploring Federated Security
7.6.1. Security Token Services7.6.2. SAML Tokens7.6.3. Windows CardSpace7.6.4. LAB: Working with WSFederationHttpBinding7.6.4.1. Configuring WSFederationHttpBinding7.6.4.2. Creating an information card in CardSpace7.6.4.3. Evaluating CardSpace claims7.6.5. WSFederationHttpBinding Security Features
7.7. Summary
8. Exceptions and Faults
8.1. SOAP Faults
8.1.1. Fault Versions8.1.2. Faults and WSDL
8.2. WCF Exception Handling
8.2.1. Fault Exceptions8.2.2. Service Exception Handling8.2.3. Client Exception Handling
8.3. Exceptions and Debugging
8.3.1. Lab: Working with Uncaught Exceptions8.3.2. Debugging Behavior8.3.3. Uncaught Exceptions and SOAP Faults8.3.4. Clients and Faulted Channels
8.4. Fault Contracts
8.4.1. Lab: Throwing Faults and Declaring Fault Contracts8.4.2. Throwing Faults8.4.2.1. FaultException8.4.2.2. FaultException<T>8.4.2.3. MessageFault8.4.3. Declared Faults8.4.4. Fault Contracts and Complex Types8.4.5. Mapping MessageFault to SOAP Fault8.4.5.1. Creating SOAP 1.1 compliant faults8.4.6. Clients and FaultContracts
8.5. IErrorHandler
8.5.1. Lab: Intercepting Uncaught Exceptions with IErrorHandler8.5.1.1. Implementing IErrorHandler8.5.1.2. Configuring an error handler8.5.1.3. Using data contracts as fault contracts8.5.2. IErrorHandler8.5.3. Configuring Error Handlers8.5.3.1. Implementing IServiceBehavior8.5.3.2. Attributes and IServiceBehavior8.5.3.3. Extending ServiceHost
8.6. Summary
A. Setup Instructions
A.1. Database Setup
A.1.1. Choosing a Database EngineA.1.2. Installing Database ScriptsA.1.3. Database Connection StringsA.1.4. Database Security
A.2. ASP.NET Provider Model Setup
A.2.1. Generating ASP.NET Provider TablesA.2.2. ASP.NET Provider Connection StringsA.2.3. Creating Sample Users and Roles
A.3. Certificate Setup
A.3.1. Sample CertificatesA.3.2. Certificates ConsoleA.3.3. Importing CertificatesA.3.4. Certificate SecurityA.3.5. Setting Up an SSL CertificateA.3.5.1. Instructions for IIS 5.1 and 6.0A.3.5.2. Instructions for IIS 7.0A.3.6. Generating Certificates
A.4. IIS Application Directories
A.4.1. Instructions for IIS 5.1 and 6.0A.4.2. Instructions for IIS 7.0
B. ASP.NET Meets CardSpace
B.1. Information Cards and CardSpace: A Brief Tour
B.2. Identity Metasystem Participants and Browser Flow
B.3. Let’s Log In with CardSpace!
B.4. Processing the Token
B.5. Associating Cards with User Accounts
B.6. Creating a Dual Purpose Login Page
B.7. Conclusion
Index
About the Author
Colophon
Copyright

Content preview from Learning WCF

IIS 7.0 and Windows Activation Service

On Windows Vista and Windows Server 2008 machines you can host your WCF services with Windows Activation Service (WAS). WAS is a process activation service installed with IIS 7.0 that decouples the activation architecture from IIS in order to support non-HTTP protocols such as named pipes, TCP, and MSMQ. Like IIS 6.0, WAS also provides features for idle-time management, health monitoring, process recycling, and management tools for configuring application pools among other things. Although supported by Windows Vista, hosting in the WAS is not incredibly useful for client deployments.

In this section, I’ll explain how WAS hosting works, show you how the hosting architecture compares to IIS 6.0 hosting, and provide you with some tips for getting started with the WAS.

WAS Hosting Architecture

IIS 7.0 introduces some architectural changes necessary to expand support for named pipes, TCP, and MSMQ protocols. The new architecture relies on protocol listeners, listener adapters and protocol handlers to process requests.

Protocol listeners: A protocol listener is responsible for receiving requests for a particular protocol. There is a protocol listener provided for HTTP, named pipes, TCP, and MSMQ. For HTTP, the listener is http.sys (same as IIS 6.0). Listeners for other protocols are provided by their respective listener adapter service.
Listener adapters: A listener adapter is responsible for bridging requests between the WAS and the ASP.NET worker process ...

Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.

Read now

Unlock full access

More than 5,000 organizations count on O’Reilly

O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.

Julian F.

Head of Cybersecurity

I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.

Addison B.

Field Engineer

I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.

Amir M.

Data Platform Tech Lead

I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.

Mark W.

Embedded Software Engineer

Professional WCF 4: Windows Communication Foundation with .NET 4

Publisher Resources

ISBN: 9780596101626Errata Page

Cloud Computing

Data Engineering

Data Science

AI & ML

Programming Languages

Software Architecture

IT/Ops

Security

Design

Business

Soft Skills

Learning WCF

by Michele Leroux Bustamante

IIS 7.0 and Windows Activation Service

WAS Hosting Architecture

Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.