In Deutsch, klicken Sie hier
Day 1
Service-Orientation
Modeling and writing applications in a service-oriented way is said to be a good thing', but what does this mean? And what are the technical implications of following this uber design pattern? This first module introduces you to service orientation which is the key to understand why technologies like Windows Communication Foundation (WCF) and Windows Workflow Foundation (WF) work the way they do.
WCF - Overview and Architecture
In this module, we learn what a WCF service is. We learn the basics of servicesendpoints, addresses, bindings, contract, hosting, metadata, and proxies.
WCF - Design by Contract
WCF offers many means to design our services, operations, messages and data. Having a strict and explicit design is the key to interoperability and contract evolvement. In this module we learn about the recommended ways to design contracts for services, including one-way operations and streaming operations. We also learn about the accompanying contracts for messages and data.
Day 2
WCF - Instances, Concurrency and Session Management
Here we learn to manage instances on the service-side. First we look at the built-in modes: per call, singleton, and per session. We examine how these modes interact with concurrent requests and clients. We'll also learn how to use sessions, when they make sense, and the big responsibilities for the client and service developers that come with them.
WCF - Security
We learn to secure the communication between clients and services. We'll discover when to use transport versus message security. And learn to secure a binding and specify level of protection, as we learn about the different credential types like user names, certificates, and Windows. Finally, we'll cover how authorization works in WCF, including impersonation and role-based security.
WCF - Hosting
We learn about the different options for hosting a WCF service: IIS/WAS, Windows Services, and Smart Client applications. We discuss the pros and cons of these options for specific scenarios.
Day 3
WF Services
Windows Workflow Foundation (WF) 4.0 is a ground-up rewrite of workflow that offers a powerful new way to write applications that provided an infrastructure for long-running processing and the increased transparency on what that processing was doing. In this module, we'll learn about how to use the new engine and library, with a focus on the integration between WF and WCF.
WCF REST
REST is another architectural style for building services often also called RESTful services. REST embraces HTTP as an application protocol and uses URIs to address pieces of functionality in a service. Starting with .NET 3.5, WCF includes the Web Programming Model , which allows building RESTful services with an easy to use API. And finally, we'll learn the fundamentals of REST, as well as why and when RESTful services make sense.
Azure Services Architecture
Azure Services is a multi-layered architecture for running applications and services in Microsoft hosted data centers and leverage the power of the Cloud. In this module, we will look at the different pieces of Azure and how they are layered on top of each other.
Day 4
Windows Azure - Development and Hosting
In this module, we look in detail about what is involved in the Windows Azure development process. We will examine the Development Fabric that gives you a local implementation of the data center hosting environment to allow Windows Azure development without the need to have the data center accessible. We'll then look at how you deploy into the cloud and what facilities are available to control your execution environment.
Windows Azure - Storage
Running applications in a hosted infrastructure presents its own challenges. Windows Azure's approach is not to provide a dedicated machine but rather to provide services that your application consumes. This means that your application can make no assumptions about the machine on which it executes, which presents an issue with where do you store state. Windows Azure storage services provide storage for blobs, structured data, and queues. In this module, we will look at how these work and how you use them from your applications.
Identity Management
The requirements for digital identity have moved beyond the traditional username and password. This provides a relatively insecure and non-scalable solution when using multiple systems. The idea of modeling identity in a more flexible way has led to the idea of using federation for authentication, and the concept of claims for authorization. Microsoft has encapsulated this infrastructure in a project called Geneva which provides both an API and a server that we'll cover in this model, and discuss how this can be used in both WCF and ASP.NET.
