|
|||||||||||
|
|
|||||||||||
|
|
![]() |
Presentations Cloud Computing Presentations Service Oriented Architecture and Web Services Presentations Windows Workflow Presentations Introductory .NET Presentations
Do Relational Databases Belong in the Cloud?
A Lap Around Windows Azure and the Azure
Platform
SOA and Web Services Presentations
Software as a Service in the Cloud
Windows Workflow and WCF Help Make “Software + Services” a Reality
Speaking a
Common Language: The OASIS Reference Model for Service Oriented
Architecture
Developers often have trouble understanding Service
Oriented Architecture (SOA) because it is frequently talked about in
very abstract terms. This is unfortunate because corporate economics
and technology improvements are driving the use of service
orientation to develop modern business applications. This talk explains in very clear and concrete terms what a SOA is, why it is
important, and what it means to develop a SOA application.
Windows Communication Foundation (WCF) is Microsoft's
new technology for building all kinds of distributed applications.
This introductory talk explains the basic concepts of the Indigo
programming model and relates them to how to build a service
oriented application. Since this is a pre-release version of the
technology, the code samples were built with the September 2005 CTP
build. Windows Workflow Presentations
Workflow
Services Using WCF and WF Using workflow to build services is one of the fundamental building blocks of service-oriented systems. Version 3.5 of the .NET Framework simplifies the building of workflow enabled services using Windows Workflow Foundation (WF) and Windows Communication Foundation (WCF). The new framework classes reduce the amount of plumbing code that has to be written as well as providing new templates to help build these kinds of scenarios. This talk will not only illustrate the new features, but demonstrate them with a realistic scenario.
Using the Windows Workflow Rules Engine Outside of a Workflow Windows Workflow Rules Engine can be used as a standalone rules engine. This talk explains how to use the Windows Workflow Rules Engine as part of an application without invoking a workflow. You have to understand how to design and code the integration and connection of the Rules Engine with your application. You have to understand how to incorporate modified rule sets into your application without having to rebuild the application. You have to understand how to architect and build an application that allows you to edit the rules outside of your application. You will have to build your own, and decide how you want to handle the versioning of rule sets. Understanding WWF is helpful for this talk, but it is not a prerequisite.
State Machine Workflows When modeling workflows involve human interaction, there are often long periods of time before a response is made to a request. In this environment, modeling the workflow as a series of states and transitions is often the best model. This session will demonstrate how to incorporate a state transition model into a workflow. Advanced Topics in Windows Workflow Foundation
Download Code Samples
Building Business Applications Using Microsoft Windows Workflow
Foundation Microsoft Windows Workflow (WF) will arrive with
.NET Framework 3.0, and offers a programming solution that lets you
focus on writing business workflows immediately without having to
solve the difficult problems of workflow plumbing. In this session,
I will enhance the application built in the introductory session by
introducing more advanced features of workflow in order to
demonstrate how to build real world workflows. This will require
overcoming some difficult challenges. Businesses have complex
policies that are difficult to express. Workflow Foundation allows
you express these business policy constraints as rules which may
vary depending on the specific business conditions. Most real life
workflows run for long periods of time, this talk will show how to
use compensation, rather than the classic ACID transaction model to
build workflows. In addition, I will demonstrate how these long
running workflows can communicate asynchronously with other people
and software. What do email, meeting planning, document
approval, budgeting, manufacturing processes, resource planning, and
product lifecycle management have in common? Work flow: long
running, complex business processes that interact with human
decision making. But traditional, conventional programming
techniques require you to spend an enormous amount of time building
your workflow infrastructure before you write a line of application
code. Fortunately, there’s a solution: Microsoft Windows
Workflow (WF) will arrive with .NET Framework 3.0, and offers a
programming solution that lets you focus on writing business
workflows immediately without having to solve the difficult
problems of workflow plumbing. In this session, I will introduce the
fundamentals of building workflow applications. Using an example of
a simple business process, I will show you how to build a simple
workflow application. I will also explain the fundamental parts of
WF such as hosts, workflow, the activities and the basic workflow
patterns.
How to Partition and Layer a Software Application How do you make your software adaptable to changing
technologies? Everyone answers: use layering. But
exactly how do you develop software layers? How do you create
application interfaces that allow you to change the underlying
technology? This is especially crucial as we begin to think about
cloud computing and realize that parts of applications may migrate
to the cloud, while others stay on desktops and local servers. With the introduction of assemblies, the Global Assembly Cache, strong names, and version policy, .NET developers need not suffer with the "DLL Hell" that has plagued Windows development for years. While that is a gigantic step in the right direction, a large, but manageable problem has emerged: "Version Hell". "Version Hell" arises from two facts of .NET life
if you use assembly versions to build bullet-proof installations and
deinstallations. First, strongly named executables must call into
strongly named class library assemblies. Second, change the version
of an assembly, and you have a different version of the types in
that assembly.
Application Domains And Contexts and Threads, Oh My!
Stopping the Barbarians at the Gate: .NET Code Access Security
Introductory .NET
Presentations Microsoft .NET revolutionizes software development on the Windows platform. The C# language provides a particularly clear way of working with .NET’s Common Language Runtime, and the extensible .NET Framework class library. This session will leverage your existing programming skills from other languages such as Java, Visual Basic, or C++ to help you understand how to use C# to develop on the .NET platform. The topics covered include attributes, metadata, interface-based programming, memory management, type safety, and the basics of the framework class library. This talk was given at the SYSCON Edge 2004 East Conference. Microsoft .NET revolutionizes software development on the Windows platform to provide one programming development paradigm. .NET is made up of a virtual execution environment, the Common Language Runtime, and the extensible .NET Framework class library. While understanding this technology is imperative for people who develop on Microsoft platforms, other developers need to understand this technology so that they can build applications for heterogeneous platform environments. |
![]() |
|
| All Content (c) 2000 - 2009 Reliable Software, Inc. All rights reserved. | |||