次の方法で共有

Microsoft .NET Services July 2009 CTP Release

  • [アーティクル]

The IT industry is in the midst of a computing transformation as more applications are delivered over the Web and through the browser. Today businesses and customers have the power of choice to run applications locally, in the cloud, or a combination of both.

 

The hybrid model prioritizes user and organizational experiences that rise above the level of a single computer, phone, corporate data center or Web browser, and beyond the forced choice dictated by a single deployment model, data center, or bandwidth constraint. To capitalize on these hybrid scenarios presented by cloud computing, customers need the flexibility to run their applications and services on a variety of hardware and software platforms, across a myriad of deployment scenarios.

 

In heterogeneous environments, customers need three capabilities in order to realize success:

 

(1) Connect Applications and Users – Microsoft .NET Services connects disparate applications, whether on-premises, hosted, or cloud-based, across network and organizational boundaries..

(2) Interoperability by Default – .NET Services supports Web standards and is Web addressable, enabling developers to use any programming language to connect, collaborate, and create federated applications.

(3) Federation of Data, Messages, Identity and Access - .NET Services federates data and messages, simplifying the crossing of network and organizational boundaries.  It also federates identity and access, making it easier to implement access control through a variety of identity providers, using a cloud-based service for access control. As an example, you might want to allow users to sign into your service using Live ID, a Yahoo! ID, Google, Facebook Connect, OpenID, OAuth, or any number of other standards-based ID providers.  With .NET Services, developers will find those solutions easier to build.

.NET Services includes a hosted .NET Service Bus for connecting applications and services across network boundaries, and .NET Access Control for securing applications.

 

 

Today’s news

 

Today, Tuesday July 7 2009, Microsoft will release an updated Community Technology Preview (CTP) of the .NET Services Software Development Kit (SDK). The latest .NET Services SDK CTP delivers support for Windows 7 RC, expedites the set-up experience, improves service security and reliability, and follows-through on the planned removal of the.NET Services Workflow Service.

 

As we approach commercial availability before year-end 2009, we will continue to deliver incremental improvements to the .NET Services SDK which enable loosely-coupled connections between applications and organizations, improve our by-default-interoperability across Web services standards and various programming languages, and ensure a simple, familiar experience for developers utilizing .NET Services.

 

 

Additional Detail

 

The July CTP Release for.NET Services SDK introduces the following updates:

 

(1) Windows 7 RC Support - .NET Services now supports Windows 7 RC, in addition to Windows Server 2008, Windows Server 2008 R2 and Windows Vista.  The July CTP Release SDK can be installed on machines running Windows 7 RC.

(2) Set-up - There are multiple improvements in the set-up experience, which make it quicker for developers to get started and take advantage of the benefits of .NET Services: 

   - One-click install.

   - Integrated installer (combined UI/ unattended install) for both the SDK and the Client Redistributable.

   - The SDK installer now also supports incremental upgrades.

 

Workflow Service – As announced previously, after listening to customer feedback this service is being removed from .NET Services until further notice.

 

 

You can –

 

   - download the latest SDK at www.azure.com/netservices,

   - visit the Developers Center at https://msdn.microsoft.com/azure/netservices, and

   - follow .NET Services (@dotnetservices) on Twitter at https://twitter.com/dotnetservices.

 

 

 

 

The Microsoft .NET Services Team

Comments

  • Anonymous
    July 07, 2009
    What's odd is I was able to run the previous sdk on Windows 7 RC with no problem. In addition, I was able to make a reference to the assemblies from a VS2010 Beta solution.