Welcome to Microsoft .NET Framework 3.0 Community (NetFx3)

The .NET Framework is Microsoft's managed code programming model for building applications that have visually stunning user experiences, seamless and secure communication, and the ability to model a range of business processes.

Learn More...

WCF Community Bloggers

Browse by Tags

All Tags » SOAP   (RSS)

  • How Can I Help You With Your WCF/WF/Neuron/Messaging Needs Today?

    I mentioned that I was looking for new opportunitie s but I have decided to concentrate my independent Microsoft .NET consulting on all things Connected Systems and Messaging. I see many shops around the country struggling with WCF and WF. In this area, I have been a part of the WCF and WF SDRs for 4 years now since the beginning and part of the large 2-year WCF and WF effort at Algorithmics. I am available, on a consulting basis , to help you with your WCF, WF and BizTalk needs. In addition, I believe that WCF is too low-level and difficult for many shops that are pursuing Services and SOA beyond a few causal services. To that end, I am an authorized representative for Neuron ESB and it's place in accelerating your WCF and SOA efforts.  Using my 26 years in the industry, I can help you look at your Architecture and find ways to make it better. Not only that, but I can help ensure you are on the right path for Oslo. If you are interested, please respond here or email to managedcode44 AT hotmail. Please do not use that email for unrelated questions - that's what the comments and newsgroups are for. Technorati Tags: Sam Gentile , WCF , WF , BizTalk , Software Architecture , Neuron ESB , ESB , SOA Read More...
  • SOA: Making the Paradigm Shift Part 11 of N

    Welcome to the 11th article in the series. In this article, I will take a broad detour from the abstract into the concrete with WCF. The title of this article is "Introduction to WCF: Architecture and the "ABCs" of Indigo." BTW, I have been in the Indigo SDR program for over 4 years and the term Indigo has stuck in my mind, so I will use the terms interchangeably. Plus, as I think Don Box said in a presentation, It's spelled W-C-F and pronounced Indigo. The WCF is silent." :) Hello Indigo Step by Step I am going to show you WCF step by step and make it as easy as possible. To that end, I am put both the Sender and Receiver in the same console application and I am not going to use either generated proxies or config files. You would never do this in the real world, but it makes it easy to describe the "ABCs" of WCF. So, let's start with a shell console application that should be totally familiar to you. Run VS2008 and Create a new C# Console application and replace the code with the following. using System; using System.ServiceModel; namespace HelloIndigo {     class Program     {         static   void Main()         {                     }     } }   A Service is a Set of Endpoints A WCF service is a set of endpoints that provide Read More...
  • SOA: Making The Paradigm Shift Part 3 of N

    In this episode, I get to define SOA, instantly coming into conflict with just about everyone who has ever defined it :). Right. Onward. First and foremost, Service-Oriented Architecture is an architectural style, not a framework. It's a design model, it's a way of thinking . I like to say it's not something you can buy or run a wizard for. I would also say that it is a Design model with a very strong emphasis on encapsulating application logic within Services that interact via a common communications protocol. Then there is the business aspect of SOA which I think is extremely important and relevant to the definition. I said, back here , some of this which I will repeat, " any definition of SOA must encompass the business drivers and business reasons, as SOA is not really about technology. It is about a better alignment of business and IT through business processes and services . The goal is to create a dynamic, more Agile and Dynamic IT that can respond quickly to new business opportunities and threats by quickly assembling new capabilities from putting together composite applications (and even Mash-ups) from reusable business services. Heck, people have been arguing about this definition for years, including me . I like this definition [1] "SOA establishes an architectural model that aims to embrace the efficiency, agility, and productivity of an enterprise by positioning services as the primary means through which solution logic is represented in support Read More...
  • SOA: Making the Paradigm Shift Part 1 of N

    I have been giving an SOA talk, in various forms for several years, where I concentrate on various themes. For the benefit of many who have not gone to such talks, as well as for others, I always wanted to start a written series based on these talks. Since, I can't sleep tonight, this is Part 1. In this series, I would like to discuss a lot of concepts that are not tied to any particular technology stack whatsoever . SOA requires a Paradigm Shift in thinking and I am very interested in getting people there. Chief, among these ideas is that People Drive Business Outcomes, not technology. Thus, there are people and business drivers for SOA. Doing SOA for the sake of doing SOA or for some technology exercise is very likely to fail. We will use Microsoft Infrastructure Optimization (IO) to measure, yes measure the value of the business enablers in the context of a maturity model. Rather than being vague guidelines, we will instead have ways to measure business drivers and then the services that meet them into the context of creating a more dynamic IT. However, as we delve into implementation, I will need to use a stack, and I will use Indigo. Yes, say it with me. The W-C-F is silent. It's pronounced "Indigo." Examples will be all with .NET Framework 3.5 Beta 1 and Visual Studio 2008 Beta 1. At that point, I envision the series moving more into how Indigo is a framework or platform for creating SOA. As WCF is THE one Microsoft distributed stack to rule them all (among Read More...
  • Neuron 2.0 - The WCF and SOA Enabler

    I did say we had a bigger announcement and we did. In the last post, I gave the "official" announcement. However, I have a personal and professional relationship with the product and I would like to start a series of posts on it now, as David, the Neuron Architect is doing . His post gives a detailed paragraph of major features, and indeed, there are a lot! 2.0 has over 60 new features over 1.0 and Neuron is a powerful product that enables various scenarios. In designing the product, we didn't want to get religious about what an ESB was. There are plenty of people doing that as well as whether or not an ESB is needed or not. Instead, we wanted to take a practical approach and solve our Microsoft customer problems. So Neuron came out of real customer scenarios in trying to use the .NET Framework 3.0 (WCF) and other Microsoft technologies. For the purposes One thing we saw was a lack of WCF adoption due to the steep learning curve. People like myself, find it incredibly simpler then the mess of distributed stacks we had to deal with before, but I am in the minority. Moreover, most IT shops don't have developers experienced in this kind of programming. What they have is C# and VB ASP.NET developers, who, as they should be, are focused on delivering business value. We saw similar pain points in SOA adoption. There are real benefits in SOA but people are either off on vendor exercises or writing a ton of infrastructure code. In either case, the real benefit of Business Read More...
  • SAML and Federated Identity Part 2 - Identity Management

    Last time, I talked a bit about SAML and Federated Identity . It turns out this is a subset of a general area, an area commonly referred to as Identity Management . The issue is how to protect and manage credentials across a wide array of network applications that have different authentication methods and requirements. I talked about SSO last time, mostly around SSO in browsers and web applications. As Pablo reminded me , it's not just web browsers; SAML is trying to solve the problem of SSO in general so that the user can log in once for multiple applications. This is, of course, critical in Real-World services or SOA. All of this points to an effective identity management infrastructure. The Elements of an Identity Management System Such a solution would be made up of the following capabilities as services [1]: Identity Provisioning Services - Set up users easily; Provision users and roles typically in LDAP compliant sources; Policy definition and enforcement Identity Data Synchronization Services - This is all about synchronizing identity data across a wide range of heterogeneous apps, directories, databases and other stores Access Management Services - SSO access to apps and services across heterogeneous apps, Web Services and resources running on diverse platforms local or network Federation Services - This is one place where SAML comes in to provide a federated framework and authentication -sharing mechanism that is interoperable with existing systems Directory Services Read More...
  • SAML and Federated Identity 101 (Part 1)

    I am dealing with some tough SAML issues, with Michele's help, and I thought I would put in some review notes on SAML for other people to benefit as well. Reference for this material was the book: Securing Web Services with WS-Security.   Introduction In the past, there was no real need to share identities from one organization or company to another. This has changed quite a bit with SOA, Services and the Internet with increased collaboration across trust domains. The need for federation of security attributes has become critical. Some Definitions Identity - Individual or entity (machine) representing itself for consideration Subject - Entity asserting it's identity Credentials - created when a subject's identity initially established and verified in some trust domain by some 3rd party Portable - Credentials are portable when subject's identity verified in one trust domain and wants to assert and its identity and rights in another trust domain Assertions is a claim when some subject identity wants to do something. They may be challenged and proven. Authentication is an assertion that a subject is who they say they are Authorization is an assertion that the subject identity is allowed to do something Why SAML? XML and/or SOAP has no standardized and interoperable way to communicate two different entities in two different trust domains to communicate their security properties and establish trust. Security Assertion Markup Language  (SAML) is the XML standard Read More...
  • Speaking Tomorrow Night - Northern Delaware .Net User Group

      Meeting Reminder 27 March 2008 5:30 – 7:30 pm   Diamond Technologies, Inc   Sam Gentile   Advanced WCF: Asynchronous Messaging and Event-Driven Architectures   Sponsored by:  Diamond Technologies, Inc.   Directions     Many WCF developers start and end with the Request/Response Message Exchange Pattern.  In actuality, there is a wide variety of Message Exchange Patterns cataloged by Hohpe and Woolfe in books like “Enterprise Integration Patterns” and Pattern & Practices “Integration Patterns.” In this advanced talk, that starts where most WCF talks leave off, we will show you how to build more loosely-coupled services and systems via these MEPs and with WCF. We will then focus on the powerful List-Based Publish/Subscribe Design Pattern. Upon showing how many lines of WCF code are required to implement the pattern in WCF, we will show the pattern as the basis for the Neuron ESB and achieve the same results with zero code. We will then focus on Mediation and how ESBs help mediate between disparate services.   Technorati Tags: INETA , WCF , SOA , Neudeisc , Neuron , ESB Read More...
  • Launch Into 2008...A Microsoft Geek's Timeline

    For the NuCon events we have been running with Microsoft to launch the 2008 Launch Wave, we have been giving out these Neudesic/Microsoft shirts that, IMHO, are really cool - they have this cool timeline on the back on how we see we got to here and shows a lot of the things we focus on (i.e. We use Agile/Scrum methodologies exclusively to run our projects): Simula 67 '67 Pascal '70 Internet Goes Public '92 SQL Server 4.21 Shipped '92 Scrum Created '93 SOA Coined '96 MS Released OLAP Services '98 EAI Coined '99 C# Announced '00 Web Services Coined '00 WSDL 1.0 Spec. '00 SOAP 1.1 Spec. '00 SQL Server Released '00 Neudesic Formed '01 Agile Manifesto '01 ESB Coined '02 "Indigo" Available '03 WS-Security 1.0 Spec '04 Neuron Conceived '05 .NET 3.0 RTM '06 LINQ Announced '05 C# 3.0 RTM '07 .NET 3.5 RTM '07 SOAP 1.2 Spec. '07 Neuron RTM '07 SQL Server 2008 '08 Technorati Tags: Microsoft , Neudesic , Web Services , SQL Server , LINQ , .NET Framework 3.5 , Neuron Read More...

Copyright © 2007 Microsoft Corporation. All Rights Reserved. | Terms of Use | Privacy Statement | Contact Us