| |
| |
|
|
|
| |
|
Best practices to decrease coupling and to raise cohesion
|
|
|
.NET Framework
|
|
March 1, 2008 01:00 PM - 02:15 PM Room: International B/C
|
|
Mario Cardinal, DotNet Expertise
|
|
This presentation presents simple but well proven design principles to simplify managing dependencies between elements composing a .Net program. At the end of this presentation you will understand how to design for testability using service locator, dependency injection, IoC container, dependency inversion and single responsibility principle.
|
|
|
Building Workflow Foundation Enabled Windows Communication Foundation Services in .NET 3.5
|
|
|
.NET Framework
|
|
March 1, 2008 09:00 AM - 10:15 AM Room: International B/C
|
|
Bill Brockbank, Navantis Inc.
|
|
With the availability of Windows Workflow Foundation (WF), Microsoft is introducing workflow capabilities to the .NET developer platform. These capabilities allow developers to build workflows to meet a wide number of scenarios, from simple sequential workflows to complex state machine-based workflows with sophisticated human interactions.
At the same time, there is a move towards promoting business capabilities to be exposed through encapsulated service endpoints allowing reuse and composition of business functions and processes giving rise to Service-Oriented Architectures. Windows Communication Foundation (WCF) has been made available to help provide developers with capabilities to develop connected systems easily by providing a consistent developer API, a robust hosting runtime, and a flexible configuration-driven solution to aid deployment.
Visual Studio 2008 provides a simple way to integrate both technologies using the built-in activities: ReceiveActivity and SendActivity. Making the analogy with WCF conventional services; in WCF you create a service interface (ServiceContract) and then you implement it with a regular class. With Workflow Services you create the interface but the implementation is the workflow itself.
|
|
|
Introduction to Language Integrated Query (LINQ)
|
|
|
.NET Framework
|
|
March 1, 2008 04:00 PM - 05:15 PM Room: International B/C
|
|
Rob Windsor, ObjectSharp
|
|
Language Integrated Query is the most compelling new feature in Visual Studio 2008 (.NET 3.5, VB9, C#3.0). LINQ’s ability to dramatically simplify data access logic with LINQ 2 SQL and its uniform syntax to also manipulate object collections and XML with LINQ to XML combine together to change the way we write software on the .NET Platform. In this session we’ll explore the framework components and language syntax additions in C# 3.0 and VB 9.0 to enable LINQ without the need for changes in the core CLR. LINQ provides typical query operations for filtering, sorting, grouping transforming and partitioning data. We’ll examine how things work under the covers and explore debugging techniques so you can really understand what’s going on. We’ll delve into LINQ to SQL to see how updates can be persisted in the database, understanding transactions and optimistic concurrency concerns. We will also point out potential gotchas with features like query composition and delayed execution.
|
|
|
SOA and Enterprise as business enablers – The Microsoft way
|
|
|
.NET Framework
|
|
March 1, 2008 02:30 PM - 03:45 PM Room: International B/C
|
|
Anthony Bonaventure D’Costa , OnCorp Direct INC.
|
These days whenever a developer writes a single line of code, it is very critical that he understands the dependencies between business and the underlying technologies. Neglecting the business context can result in a project in which SOA infrastructure is pursued for its own sake, or where investments are made that do not line up well with the needs and priorities of the business. Todays enterprise developers should be thinking "SOA". Everything should be services.
For developers working with the Microsoft technology stack, using .NET, BizTalk, IIS etc. we have everything we need to create sophisticated distributed applications. However, there are a lot of moving parts. Most of us now work in heterogenous environments, where distributed applications span a variety of technologies, and possibly business partners and customers.
It takes a lot of skill to blend all the pieces into a cohesive whole and it takes time. SOA is not a product, it is a way of thinking about software development. When faced with a functional requirement, think how that can be decomposed into a set of services. When done properly these services will not only solve the current requirements, but will
also be the building blocks that can be aggregrated to meet future needs.
Microsoft's stack of technologies ( WS*- specs, BizTalk Server R2, WCF,
WF, WPF ... have the potential to improve our productivity and agility.
|
|
|
SOA using WCF & WF
|
|
|
.NET Framework
|
|
March 1, 2008 10:30 AM - 11:45 AM Room: International B/C
|
|
Peter Madziak, ObjectSharp Consulting
|
|
In the world of SOA it is useful to classify your services into two types: Business Activity Services and Resource (or sometimes Entity) Services. In this demo-centric session we’ll look at how Windows Communication Foundation (WCF) and Windows Workflow (WF) can be used within this classification system. More specifically we’ll look at how WF is an ideal choice to use “inside the boundary” of your Activity Services to carry out the long-running work the service represents.
|
|
|
|
|
 |
|
|
|
|
| |
|
|
|
|