.NET Services Portal address

Description

.NET Services Portal URL is changed

Pre-Release Behavior

.NET Services Portal can be accessed at http://portal.ex.azure.microsoft.com

Post-Release Behavior

.NET Services Portal can be accessed at https://netservices.azure.com

Subscription migration

Description

Exiting Subscription name in the July 2009 CTP will be automatically migrated as Project name in the November 2009 CTP

Pre-Release Behavior

“Azure CTP Project” is the default value for the existing Subscription

Post-Release Behavior

“Azure CTP Project” is the default value for the existing Project.  Users can assign arbitrary names to newly created projects in the November 2009 CTP

Solution migration

Description

Solutions in the July 2009 CTP will be automatically migrated as Service Namespaces in the November 2009 CTP

Pre-Release Behavior

Solution is the basic entity of a Subscription

Post-Release Behavior

Service Namespace is the basic entity of a Project

Solution region migration

Description

Existing solutions might be migrated to different sub-regions within the United States

Pre-Release Behavior

Solutions are located in a sub-region within the United States

Post-Release Behavior

Existing Service Namespaces will be automatically migrated and reassigned to North Central or South sub-region within the United States. 

Queues changes

Description

The Service Bus Queues feature has been changed due to customer feedback and is renamed to “Message Buffer” in order to better reflect the associated capabilities.  Message Buffers will be introduced with temporary caching functionality in the November 2009 CTP and the long term goal of providing comparable functionality to queues.

Pre-Release Behavior

Queues provide persistent message storage.   Microsoft.ServicesBus.dll provides APIs such as QueueClient, QueueManagementClient, QueuePolicy for interaction with Queues

Post-Release Behavior

Message Buffers provide message caching.  Queues related APIs will be removed from Microsoft.ServicesBus.dll.  MessageBufferClient APIs will be provided in Microsoft.ServicesBus.dll for interaction with the new Message Buffers

Recommended Post-Release Action

References to Queues should be removed from applications.  For some applications, Message Buffers may be substituted for Queues.  Where durability requirements exist, solutions employing Azure storage features may be preferred.

Routers removal

Description

Service Bus Routers feature will be removed.  A November 2009 CTP sample will be provided to demonstrate how to implement an ‘anycast’ message distribution model similar to the Router’s respective capability

Pre-Release Behavior

Routers push messages to a subscription list.    Microsoft.ServicesBus.dll provides APIs such as RouterClient, RouterManagementClient, RouterPolicy etc… for interaction with Routers

Post-Release Behavior

Routers functionality as well as related Microsoft.ServiceBus.Router APIs are removed

Recommended Post-Release Action

Router API calls should be removed from applications.  For some applications, the approach suggested in the LoadBalance sample may provide sufficient message routing functionality.  Other approaches are possible but are likely to require more client code.

RelayBinding Security Default

Description

All RelayBindings are secured by default in the November 2009 CTP

Pre-Release Behavior

Some RelayBindings have RelaySecurity.Mode set to EndToEndSecurityMode.None

Post-Release Behavior

All RelayBindings have RelaySecurity.Mode set to EndToEndSecurityMode.Transport which is secured by default

Recommended Post-Release Action

User code using any RelayBinding should be updated to use HTTPS transport in service and endpoint addresses.  As an alternative, the RelayBinding RelaySeucirty.Mode can be set to EndToEndSecurityMode.None.  Note that setting EndToEndSecurityMode.None allows message contents to travel in clear text, considered a security risk for many applications

Service Namespace replaces Solution name

Description

Solution name is replaced as Service Namespace in the November 2009 CTP

Pre-Release Behavior

Solution is the basic naming for a .NET Services solution i.e.  http://<solution>.servicebus.windows.net

Post-Release Behavior

Service Namespace is the basic naming for a .NET Services application i.e.

http://<service_namespace>.servicebus.

windows.net

TransportClientCredentialType update

Description

TransportClientCredentialType such as AutomaticRenewal, CardSpace, ClientCertificate, FederationViaCardSpace and UserName will be removed in the November 2009 CTP release.  They will be replaced by credential types that are supported by the new Access Control Service

Pre-Release Behavior

Service Bus authentication type includes CardSpace, X509Certificate, FederationViaCardSpace and UserNamePassword and are reflected in TransportClientCredentialType

Post-Release Behavior

Service Bus authenticated type includes SharedSecret, Simple Web Tokens and Saml which are reflected in TransportClientCredentialType

Recommended  Post-Release Action

User code using TransportClientCredentialType in the July 2009 CTP should be updated to use the authentication types employed in the November 2009 CTP..  Sample code will be provided in the November 2009 CTP SDK to illustrate how to use the new authentication type

EndToEndWebHttpSecurityMode.

TransportCredentialOnly is removed

Description

EndToEndWebHttpSecurityMode.

TransportCredentialOnly is removed

Pre-Release Behavior

EndToEndWebHttpSecurityMode.

TransportCredentialOnly option exists

Post-Release Behavior

EndToEndWebHttpSecurityMode.

TransportCredentialOnly option is removed as it is not supported

Recommended  Post-Release Action

User code using EndToEndWebHttpSecurityMode.

TransportCredentialOnly should use EndToEndWebHttpSecurityMode.Transport instead

HttpBufferClient is not public

Description

Microsoft.ServiceBus.HttpBufferClient is removed from public APIs

Pre-Release Behavior

Microsoft.ServiceBus.HttpBufferClient is public

Post-Release Behavior

Microsoft.ServiceBus.HttpBufferClient is no longer public

Recommended  Post-Release Action

User code using HttpBufferClient may be replaced by MessageBufferClient

TcpRelayConnectionMode.Direct is removed

Description

Microsoft.ServiceBus.

TcpRelayConnectionMode.Direct is removed

Pre-Release Behavior

Microsoft.ServiceBus.

TcpRelayConnectionMode.Direct exists

Post-Release Behavior

Microsoft.ServiceBus.

TcpRelayConnectionMode.Direct is not supported; Direct Connection is supported in Hybrid mode only.

Recommended  Post-Release Action

User code using TcpRelayConnectionMode.Direct may be replaced by TcpRelayConnectionMode.Relayed or TcpRelayConnectionMode.Hybrid

Service publishing feed address aligns with service transport

Description

Service publishing feed address aligns with service transport

Pre-Release Behavior

Service publishing feed address used HTTP transport i.e. http://<mysolution>.servicebus.windows.net/

<mycalculatorservice> regardless of the transport being used in the service i.e. service is accessed at “sb://<mysolution>.servicebus.windows.net/

<mycalculatorservice>” when NetTcpRelayBinding is used

Post-Release Behavior

Service publishing feed address is now aligned with the service transport i.e. the feed will be accessed at “sb://<mysolution>.servicebus.windows.net/

<mycalculatorservice>” when service is accessed at “sb://<mysolution>.servicebus.windows.net/

<mycalculatorservice>”

Recommended  Post-Release Action

User code referencing service publishing feed address may be updated with matching service transport

WSHttpRelayBinding is removed

Description

WSHttpRelayBinding is no longer supported

Pre-Release Behavior

WSHttpRelayBinding is supported

Post-Release Behavior

WSHttpRelayBinding is no longer supported

Recommended  Post-Release Action

User code using WSHttpRelayBinding should be changed to use another supported binding such as WS2007HttpRelayBinding or user-constructed custom binding

WS2007FederationHttpRelayBinding is removed

Description

WS2007FederationHttpRelayBinding is no longer supported

Pre-Release Behavior

WS2007FederationHttpRelayBinding is supported

Post-Release Behavior

WS2007FederationHttpRelayBinding is no longer supported

Recommended  Post-Release Action

User code using WS2007FederationHttpRelayBinding should be changed to use another supported binding such as WS2007HttpRelayBinding  or user-constructed custom binding

Solution credentials replaced with Issuer credentials

Description

Windows Cardspace, Certificates, Username/Password credentials are replaced with Issuer credentials (Issuer Name and Issuer Key) to request tokens from the Access Control Service STS

Pre-Release Behavior

Windows Cardspace, Certificates, Username/Password are supported credentials for requesting tokens from the Access Control Service STS, including tokens to authorize access to Service Bus endpoints

Post-Release Behavior

Requesting a token from the Access Control Service STS requires an Issuer credential which is consisted of an Issuer Name and an Issuer Key.  A 32 byte random base-64 encoded string should also be provided in the token request.  For Shared Secret and Simple Web Token requests, the Issuer must be configured in Access Control Service.  In addition, X509 certificate for SAML requests must be uploaded to Access Control Service

Recommended  Post-Release Action

Applications that previously used solution credentials should be ported to use Issuer credentials.

WS-Trust STS replaced with Web Resource Authorization Protocol (WRAP) STS

Description

The WS-Trust and WS-Federation STS endpoints have been replaced with a REST-based STS that accepts REST token requests

Pre-Release Behavior

Access Control Service STS accepted SWS-* security token requests

Post-Release Behavior

Access Control Service STS is now REST-based

Recommended  Post-Release Action

Application using the WS-Trust or WS-Federation capability of Access Control Service should be ported to use the new REST-based protocol and format

Access Control Service data will not be migrated

Description

All Access Control Service data such as scope, rules, certificate, Username and password, Windows Cardspace will not be migrated to the new release

Pre-Release Behavior

Access Control Service data can be accessed through public APIs or .NET Service Portal

Post-Release Behavior

Access Control Service data will not be migrated and will not be available for access through public APIs or .NET Services Portal.  Note that the Service Bus scope and rules will not be migrated either.

Recommended  Pre-Release Action

To facilitate post release configuration, you may choose to save a copy of existing data through Access Control management interface.  To learn more on how to obtain Access Control data through management interface, see the ACS Management AtomClient sample from the .NET Service July 2009 CTP SDK

Recommended  Post-Release Action

You will need to recreate Access Control Service data i.e. scope, rules etc… in order to restore your application using Service Bus or Access Control Service. 

Access Control Management Portal replaced with a SDK Command-line Tool (acm.exe)

Description

The Access Control Management Portal will be removed from the November 2009 CTP .NET Services Portal

Pre-Release Behavior

Users can manage Access Control Service objects (scopes, token policies, issuers and rules) through web user interface at the .NET Services Portal

Post-Release Behavior

A command line tool (acm.exe) will be available in the November 2009 CTP SDK for users to manage Access Control Service objects.  The .NET Services Portal will contain the Management Key which will be used to authenticate calls from the tool