Nicholas Allen's Indigo Blog

.Net Services November 2009 CTP

Nicholas Allen — Fri, 06 Nov 2009 13:00:00 GMT

The .Net Services team has made a November 2009 CTP release of the SDK for their portion of the Azure Services Platform. As mentioned over the summer, .Net Services has pared down their work on routers, queues, and relays to focus on delivering the access control service and service bus. These two services are also what the team will be focusing on at PDC.

The service bus is an infrastructure piece for connecting together different components in a distributed application. The access control service, now more oriented around REST, allows integration of those connected components with identity providers. Both services have changed quite a bit as described by the breaking changes list from the previous CTP.

The announcement for the CTP also covers how the transition from a beta product to a production service will take place.

Windows Web Services Samples

Nicholas Allen — Thu, 05 Nov 2009 13:00:00 GMT

The Windows Web Services API is a native-code implementation of a subset of the SOAP web services support in WCF. This makes Windows Web Services useful when you want to build web services but need to use C or C++ instead of managed code and need to have a minimal set of dependencies.

Many of the people on the Windows Web Services team worked on Indigo before splitting off after our first release. This means that you'll see a lot of similar names and concepts between the two even though their intended users can be quite different.

I've had a few people ask what using Windows Web Services is like and personally I think that looking at examples is a good way to find out. Windows Web Services has an excellent set of samples including a nicely organized index of examples. I'd recommend browsing through the list there starting from the service model examples and then moving to some of the deeper topics.

Breaking Changes for WCF in .Net 4 Beta 2

Nicholas Allen — Wed, 04 Nov 2009 13:00:00 GMT

Available for download is the list of breaking changes between beta 1 and beta 2 for WCF and WF. To save you some time, here's my condensed version of the list.

When adding site or machine-level collections of behaviors, those behaviors will be merged with service-level behavior configurations of the same name. Previously, you would only get the behaviors configured directly by the application if there was a naming conflict.
The blob encoder was renamed to the byte stream encoder. It still works the same though. Put some bytes in one end and the exact same bytes come out the other end.
The local "in app domain" transport channel was removed. Use named pipes instead; they're just as fast and have been available for years.
A security feature involving SAML tokens that you've probably never heard of has very slightly changed its default behavior.

Visual Studio and .Net 4 Beta 2 Survey

Nicholas Allen — Tue, 03 Nov 2009 13:00:00 GMT

The Visual Studio team has set up a survey to collect additional feedback about the Beta 2 release. If you have something to say but haven't reported it on the Connect site or through other feedback channels, this would be a good opportunity to let your thoughts be known. The window of opportunity for actually addressing the feedback in this release is closing pretty rapidly.

The survey is about ten questions long and mostly along these lines:

How are you using the Visual Studio beta?
Have you encountered any weird behaviors?
Is the performance good?

You should be able to fill it out and add your own comments in less than five minutes.

Replacing Visual Studio 2010 Beta 1 with Beta 2

Nicholas Allen — Mon, 02 Nov 2009 13:00:00 GMT

I recently helped someone out with replacing Visual Studio 2010 and .Net 4 Beta 1 with the newer Beta 2 release. Here are a few things that I had to learn along the way.

I've done enough beta installations to know that having previous versions of the same release will cause endless headaches. I don't even try to install over top of a beta installation first to see if it will work. The Beta 2 release notes for Visual Studio 2010 lead off with a known issue that trying to install Beta 2 without uninstalling Beta 1 first will fail.

Unfortunately, uninstalling Beta 1 wasn't successful as the installer would ask for the setup location for the TFS Object Model and then crash. I found the solution to that in the Beta 2 installation addendum. Before uninstalling the main Visual Studio 2010 program, uninstall Microsoft Team Foundation Server 2010 Beta 1 Object Model. This ran to completion and stopped the crashing in the Visual Studio uninstaller. It looks like you only need to worry about this component if you had installed Visual Studio Team Suite.

After uninstalling Visual Studio, this left a few Beta 1 components behind. Here's the order that worked for me:

Microsoft .NET Framework 4 Extended Beta 1
Microsoft .NET Framework 4 Client Profile Beta 1
Microsoft Visual C++ 2010 Beta 1 Redistributable x64
Microsoft Visual C++ 2010 Beta 1 Redistributable x86

At that point the system was clean and installing Beta 2 of Visual Studio and .Net 4 worked on the first try.

Building a Data Contract Serializer Behavior

Nicholas Allen — Fri, 30 Oct 2009 12:00:00 GMT

In configuration there's a DataContractSerializer behavior that I can add to my service, but the class it uses is internal. How do I get the same behavior programmatically?

The DataContractSerializer behavior is a shortcut for setting the MaxItemsInObjectGraph and IgnoreExtensionDataObject options on endpoints. You can get a similar effect by looping over the operations in your service.

First, if the DataContractSerializer behavior is supplied as a service behavior, it applies to all of the non-metadata endpoints in your service. To check whether an endpoint is a metadata endpoint, we look for the following things:

The endpoint has a ServiceMetadataBehavior in its description
The endpoint service type is IMetadataExchange
The endpoint contract name is IMetadataExchange in the namespace http://schemas.microsoft.com/2006/04/mex

Assuming that we've found a non-metadata endpoint, or the DataContractSerializer behavior is supplied as an endpoint behavior instead of a service behavior, we now scan through all of the operation descriptions on the endpoint contract. For each operation description we scan through all of its behaviors to find a DataContractSerializerOperationBehavior. The operation behavior is what stores the settings for the operation.

Finally, if the settings on the DataContractSerializerOperationBehavior were not already explicitly set, we change them to the values from the DataContractSerializer behavior. By doing this check, you can apply the behavior to an endpoint without overriding any values you set manually. This is the only step that you can't duplicate as the flag to tell where the value came from is internal. If you explicitly set the MaxItemsInObjectGraph or IgnoreExtensionDataObject options on an operation, then you'll need to explicitly exclude those operations in the behavior you write as well.

Federating from Silverlight

Nicholas Allen — Thu, 29 Oct 2009 12:00:00 GMT

I've had a few people ask whether the WCF subset in Silverlight supports message-level security. The answer currently is not very much. The security support is limited to basically the facilities that you'd expect to have for any other browser based application, primarily HTTPS and common browser HTTP authentication modes.

Dominick Baier though has put together a set of workarounds to enable basic support for federation from a Silverlight client. The method uses some customization of the token service to simplify the protocol required and pick one of the supported authentication types plus some customization of the client application to manually insert the security headers into messages. This gives you a simple form of bearer tokens in messages for a service implemented across two different security domains.

Ten More PDC 2009 Talks for Web Service Developers

Nicholas Allen — Wed, 28 Oct 2009 12:00:00 GMT

I covered earlier the WCF and WF PDC talks that the team is doing, but there are many other groups coming to PDC to talk about web services. Here is a sample of ten of those other talks that I think WCF developers may find interesting.

Developing REST Applications with the .NET Framework by Don Box and Henrik Nielsen

Come hear an overview of the REST principles and why REST is becoming popular beyond traditional Web applications. Learn how to write applications that produce and consume RESTful services using the .NET Framework 4 and the improvements we have planned for future versions of the .NET Framework.

Building Amazing Business Applications with Microsoft Silverlight and Microsoft .NET RIA Services by Brad Abrams

Learn how to build n-tier Rich Internet Applications (RIA) on Silverlight by tapping the power of .NET RIA Services. Walk through an example of building an application from scratch using the pattern run-time components and tools provided by .NET RIA Services. See how it helps you write application logic to expose data and operations in a carefully controlled fashion using tools integrated into Visual Studio with support for validation, authentication, authorization and handling units of work.

Queuing and Publish/Subscribe in a Heterogeneous Environment by David Ingham and John O'Hara

Queuing and publish/subscribe are common patterns for building loosely-coupled, distributed applications. Learn how to use Microsoft Windows Communication Foundation (WCF) the new Microsoft ASP.NET 4.0 routing service, the Microsoft .NET Service Bus, and Microsoft BizTalk Server to easily connect heterogeneous systems. We then introduce AMQP (the Advanced Message Queuing Protocol), an important new open standard for interoperable message-oriented middleware, which will reduce the friction in connecting heterogeneous clients. A real-world scenario shows AMQP in action, connecting WCF, Microsoft Excel, and Java-based clients.

REST Services Security in Windows Azure using the Access Control Service by Justin Smith

Come hear how easy it is to secure REST Web services with the Access Control Service (ACS). Learn about ACS fundamentals including how to request and process tokens, how to configure ACS, and how to use ACS to integrate your REST Web service with Active Directory Federation Services. Also see how to apply ACS in a variety of scenarios using a few popular programming models including the Windows Communication Foundation and Microsoft ASP.NET Model-View-Controller (MVC).

Microsoft ASP.NET MVC 2: The New Stuff by Stephen Walther

Come learn about the new features being introduced with ASP.NET MVC 2. Templated helpers allow associating edit and display elements with data types automatically. Areas provide a means of dividing a large Web application into multiple projects. Data annotations allows attaching metadata attributes on a model to control validation. Client validation enables form field validation without the need to perform a roundtrip to the server. Learn how these new features enable you to be more productive when building ASP.NET MVC applications.

Mastering Microsoft .NET RIA Services by Dinesh Kulkarni

This advanced-level .NET RIA Services session provides an "under-the-covers" view of how the technology works. Come learn about common architectural patterns, key design principles, and tools to work with a variety of data access layers, application logic patterns and client-usage scenarios. Examine query and unit of work patterns, custom methods, validation, authentication and authorization metadata, authoring custom validations, and using asynchronous operations effectively on the client. Hear tips and tricks to help you get the most out of .NET RIA Services in advanced scenarios. This session assumes existing experience with .NET RIA Services.

It's All about the Services: Developing Custom Applications for Microsoft SharePoint Server 2010 Using Microsoft ASP.NET, WCF, and REST by Maxim Lukiyanov

Many developers use services to build and integrate applications and line-of-business systems with SharePoint. With SharePoint 2010, developers now have a wider array of options that include ASP.NET, Windows Communication Foundation (WCF), and RESTful services. Come get a demo-rich walkthrough of each option and discuss where each of the services might be appropriate and what you stand to gain by using them.

ADO.NET Data Services: What's New with the RESTful Data Services Framework by Pablo Castro

Join this code-heavy session to discuss the upcoming version of ADO.NET Data Services, a simple, standards-based RESTful service interface for data access. Come see new features in action and learn how Microsoft products are using ADO.NET Data Services to expose and consume Data Services to achieve their goals around data sharing.

Evolving ADO.NET Entity Framework in Microsoft .NET Framework 4 and Beyond by Shyam Pather and Chris Anderson

Come see how the ADO.NET Entity Framework enables new capabilities to leverage multiple development approaches, for example the use of code-first, model-first, and database-first. Hear how, regardless of the development approach, developers will benefit from the Entity Framework and the deep integration with the rest of the Microsoft .NET Framework 4, such as the Microsoft ASP.NET MVC, Dynamic Data, and Windows Presentation Foundation.

Networking and Web Services in Microsoft Silverlight by Yavor Georgiev

This session presents an overview of how to expose data to a Silverlight application by accessing SOAP Windows Communication Foundation (WCF) services and REST services. In the WCF space, we cover Silverlight 3 approaches for securing services and improving their performance and maintainability. We also cover a specific message pattern called server push, which allows you to implement scenarios such as email clients and real-time chat. In the REST space, we walk through the Silverlight 3 client HTTP stack and new functionality it offers around HTTP verbs, headers, responses, and cross-domain access and talk about future plans for networking and Web services in Silverlight.

Finding CLR Types from Schema

Nicholas Allen — Tue, 27 Oct 2009 12:00:00 GMT

How can I found out what CLR type a particular XML schema definition will map to when using data contracts?

Ask the type system what type it thinks the schema will map to.

static string ClrTypeForXmlType(XmlQualifiedName xmlType)
{
    return new XsdDataContractImporter().GetCodeTypeReference(xmlType).BaseType;
}

static void Main(string[] args)
{
    Console.WriteLine(ClrTypeForXmlType(new XmlQualifiedName("duration", "http://www.w3.org/2001/XMLSchema")));
    Console.WriteLine(ClrTypeForXmlType(new XmlQualifiedName("token", "http://www.w3.org/2001/XMLSchema")));
    Console.WriteLine(ClrTypeForXmlType(new XmlQualifiedName("dateTime", "http://www.w3.org/2001/XMLSchema")));
    Console.WriteLine(ClrTypeForXmlType(new XmlQualifiedName("anyURI", "http://www.w3.org/2001/XMLSchema")));
    Console.WriteLine(ClrTypeForXmlType(new XmlQualifiedName("decimal", "http://www.w3.org/2001/XMLSchema")));
    Console.WriteLine(ClrTypeForXmlType(new XmlQualifiedName("positiveInteger", "http://www.w3.org/2001/XMLSchema")));
    Console.WriteLine(ClrTypeForXmlType(new XmlQualifiedName("QName", "http://www.w3.org/2001/XMLSchema")));
}

This produces the following list of types.

System.TimeSpan

System.String

System.DateTime

System.Uri

System.Decimal

System.Int64

System.Xml.XmlQualifiedName

Application Auto Start in IIS

Nicholas Allen — Mon, 26 Oct 2009 12:00:00 GMT

Application auto start is the ability for an application to be automatically started up before receiving any requests. In addition to priming the application for the first request, application auto start is also a way to have applications that start automatically and run continuously. One example where this is useful is service discovery, where an initial listener needs to be running to allow other services to be found.

Windows services have supported automatically starting when the machine is booted, but web services hosted in IIS have used a message-based activation model. There are workarounds for automatically starting and keeping an IIS service running, such as creating a second service to regularly ping your real service. However, an integrated solution would clearly be preferable.

The IIS Application Warm Up module is a beta extension for IIS 7.5 that adds the application auto start ability. You can get the module for Windows 7 and Windows Server 2008 R2.

WCF Samples for .Net 4 Beta 2

Nicholas Allen — Fri, 23 Oct 2009 12:00:00 GMT

The Windows SDK samples for WCF and WF are now available updated for .Net 4 Beta 2. These are only the samples that are new or changed in .Net 4. If you want the complete set of existing samples as well you'll need to pick those up from the platform SDK.

You can also get online documentation for the new .Net 4 samples from MSDN. Note that many of the navigation pages are missing or out of date. If the documentation for a sample doesn't appear to be included in a section, look at the navigation menu on the left hand side to see if more topics are listed for the section there. The individual sample documentation is available even though the section summaries haven't been updated yet.

.Net 4 Beta 2 Really Released

Nicholas Allen — Thu, 22 Oct 2009 12:00:00 GMT

Although available for download by subscribers the last few days, the second beta release of .Net 4 is now available to everyone. You will see a number of new WCF features changed or moved around since the first beta release, but what you see now is almost everything planned for .Net 4.

If you're planning to test .Net 4 for compatibility, then I highly recommend doing that as soon as possible using this beta, preferably in the next few weeks. It's virtually impossible to address any but the most severe issues once the release date gets close. Waiting to test can delay getting your feedback addressed for years until the next service pack or release comes out. Use the Connect link to the right as the best way to make sure any issues you find get recorded.

Here are the resources available.

There's one significant known issue that affects WCF services hosted in IIS.

ASP.NET and WCF applications might fail to start in IIS 7 Integrated mode

If new configuration sections are added to the application web configuration file of an ASP.NET or WCF application, the application will fail to start when it is running in IIS 7 Integrated mode. For example, if a configuration section is added to the web configuration file of a WCF application, the application will not start when it is running in IIS 7 Integrated mode. Instead, IIS 7 will return a configuration validation error, because the new configuration section is not recognized by the IIS 7 configuration system. To resolve this issue you can download and install a hotfix. This fix was included in Windows Vista and Server 2008 SP2.

There are several other minor known issues with IIS and ASP.NET so check the readme if you're having problems with web hosted services after upgrading.

Visual Studio and .Net 4 Training Kit October Update

Nicholas Allen — Wed, 21 Oct 2009 12:00:00 GMT

The training kit of materials for Visual Studio 2010 and .Net 4 has now been updated with the latest for beta 2. The contents of the training kit include presentations, hands on labs, and demos related to the new features in the release. Here's some of what you should expect to get for web services:

Presentations

What’s New in .NET Framework 4
What’s New in Visual Studio 2010
Introduction to ASP.NET MVC
Introduction to .NET RIA Services
Introduction to “Velocity”
What’s New in Windows Workflow 4

Labs

Introduction to ADO.NET Data Services
ASP.NET AJAX 4
Creating Plan My Night – ASP.NET MVC Application
Enhancing Plan My Night – ASP.NET MVC Application
Introduction to Workflow 4
Introduction to “Velocity”
WCF Service Discovery

ASP.NET MVC 1 Scripts on AJAX Delivery Network

Nicholas Allen — Tue, 20 Oct 2009 12:00:00 GMT

Last week the AJAX script files included for ASP.NET MVC applications were added to the AJAX content delivery network. The content delivery network is a free service that provides caching support for some of Microsoft's AJAX libraries. As a developer you benefit from a network by not having to host the files yourself. As a user you benefit from a network by having access to widespread local mirrors and cached access to script files across different sites you might visit.

The script locations to include for ASP.NET MVC 1 are:

Equivalent debug versions of the scripts are also available.

Order Best Practices

Nicholas Allen — Mon, 19 Oct 2009 12:00:00 GMT

Why is setting the Order property on data members recommended when adding fields in a new version of the contract?

The data contract versioning best practices recommend taking three steps when adding fields in a new version of a contract.

The first recommendation is to set the IsRequired property on the new field to false. Since older applications will not know about the new field, you obviously can’t require that the field always be present.

The second recommendation is to provide an OnDeserializing callback if the default value of the new field needs to be set. The default value of the field- zero, false, null, or the other similar defaults for data types- may not be a valid or desired value for the field. If the field is not required, then you will potentially see the field initialized with the default value. Creating a callback to set the default value appropriately takes care of compatibility problems.

The third is to set the Order property on the new field so that the field appears after all of the existing data members. If you are exchanging messages with an application that models the data using member name and namespace, then the order of the members tends not to matter. At most, there might be efficiency issues if the application has optimized for a specific member order but you’ve forced it to do extra work by providing the members in a different order.

On the other hand, if you are exchanging messages with an application that models the data using the structure of the contract, then the order of the members may be a more fundamental assumption. There are many applications deployed and in use that are intolerant of changing the order of members. In this case, changing the order of members or inserting new members in between doesn’t just affect the efficiency of the application but could entirely break validation or application logic. Always adding new fields to the end even when not strictly required is a conservative measure to promote compatibility and avoid having to deal with application bugs.