New revamped Windows Azure released and new Windows Azure SDK v1.7(JUNE 2012)

June 8, 2012 .NET, .NET Framework, All, AppFabric, ASP.NET MVC, Azure, Azure SDK, Cloud Computing, Cloud Services, Media Services, Microsoft, Microsoft SDKs, SQL Azure, ToolKits, Visual Studio SDK, VisualStudio, VS11, VS2010, VS2012, WCF, Windows 2008 R2, Windows 7, Windows 8, Windows Phone, Windowz Azure No comments

Microsoft has made significant changes to existing Windows Azure to make it more user friendly and customer friendly. The new Windows Azure was officially released in an online event Meet Windows Azure (MeetWindowsAzure.com) , in this event ScottGu(Microsoft VP)  has walked us through the new Windows Azure features.

You can have a quick look at ScottGu’s blog for interesting features available in new Windows Azure.

Visit http://www.windowsazure.com to have a quick look at the features of new Windows Azure website.

Development Tools and How to’s for different programming languages

You can download necessary tools for development at http://www.windowsazure.com/en-us/develop/downloads/

Recommend reading Phani Kumar’s blog on Windows Azure http://allthingsazure.com/ ,  is a good repository of latest information on Windows Azure.

That’s all for now.


Visual Studio 2012 RC(Release Candidate) is released

June 1, 2012 .NET, .NET Framework, All, ASP.NET, ASP.NET MVC, C#.NET, Microsoft, VB.NET, VisualStudio, VS11, VS2012, WCF, WPF No comments

Microsoft has released Visual Studio 2012 RC  and is available for download through MSDN as well.

Visual Studio Ultimate 2012 RC is the state-of-the-art development solution that empowers teams of all sizes to design and create compelling applications to delight users. You can use flexible agile planning tools—like capacity planning, taskboards, and backlog management—to enable incremental development techniques and agile methodologies, at your own pace. Use advanced modeling, discovery, and architecture tools to describe your system and help ensure that your architecture vision is preserved in the implementation. Bring development and operation teams together by using IntelliTrace in production, Operations Manager Connector, and Preemptive Analytics. Improve quality and reduce time to resolution by generating actionable bugs from deployed software, and effectively partner with the operation staff to provide data that gives developers greater insight into production issues.


Read these blogs for more details






Microsoft Visual Studio Professional 2012 RC

Microsoft Visual Studio Premium 2012 RC

Microsoft Visual Studio Ultimate 2012 RC

Microsoft Visual Studio Test Professional 2012 RC 

Microsoft Visual Studio Team Foundation Server 2012 RC

Microsoft Visual Studio Team Foundation Server Express 2012 RC 

ASP.NET MVC 4 Release Candidate for Visual Studio 2010 SP1 and Visual Web Developer 2010 SP1


Courtesy: Microsoft Download Center

Visual Studio 11 User Interface Updates Coming in Visual Studio 11 RC(Release Candidate)

May 15, 2012 .NET, .NET Framework, All, ASP.NET, ASP.NET MVC, C#.NET, Microsoft, Microsoft SDKs, Silverlight, Updates, VisualStudio, VS11, WCF No comments

Go through this Visual Studio Team blog about upcoming improvements to Visual Studio 11 User Interface. This will be included as part of Visual Studio 11 RC(Release Candidate) and probably will be released soon by end of May or in June 2012.

For more updates visit the Official blog link below


Kudos to Visual Studio 11 Team

Windows Phone Development–Choosers and Launchers

April 17, 2012 .NET, All, C#.NET, Microsoft, Microsoft SDKs, Mobile-Development, Silverlight, Silverlight SDK & Tools, VisualStudio, VS11, VS2010, Windows, Windows 7, Windows Phone, Windows Phone "Mango", Windows Phone 7, Windows Phone 7.0, Windows Phone 7.5, Windows Phone Development, Windows Phone SDK No comments

While doing windows phone application programming you will come across some requirements such as:

a. “Selecting a contact from contact book”

b. “Open up Camera, take a photo and upload or use the photo”

c.  “Open a link in Web Browser”

How you can achieve these typical tasks?

Answer is pretty simple Windows Phone SDK provides a set of API’s or classes you can use to perform these tasks easily.

You can use Launchers and Choosers in your Windows Phone applications to enable users to perform common tasks. By using Launchers and Choosers, you help provide a consistent user experience throughout the Windows Phone platform.

1. Launchers – are certain task API’s that would invoke a built in Application on Windows Phone.

For Example: ‘opening a link on Phone Browser’. Launchers API available with Windows Phone SDK will simplifies the task of implementing such a feature from the scratch.

Some of the Launchers provided by Windows Phone SDK are:

  • Bing Maps Direction Task
  • Bing Maps View Task
  • Connection Settings Task
  • Compose Email Task
  • Market Place Details View Task
  • Market Place Hub Task
  • Market Place Review Task
  • Market Place Search Task
  • Media Player Task
  • Phone Call task
  • Search Task
  • Share a Link Task
  • Share Status
  • SMS Compose
  • Web Browser Task

[More detailed reference use MSDN on Reference on Launchers for Windows Phone]

2. Choosers – are certain task API’s that would invoke a built in Application on Windows Phone and after completing the task it would return the result through application call back methods.  When the new application appears, the user can choose to complete or cancel the task. When the user closes the new application, the calling application is usually reactivated and supplied with data and status.

 For Example: “Selecting a contact from Address book and sending a mail to it”. or “Launching camera application and taking a photo and stores it back on the application”.

Some of the Choosers provided by Windows Phone SDK are:

  • Address Chooser Task
  • Camera Capture Task
  • Email Address Chooser Task
  • Game Invite Task
  • Phone Number Choose Task
  • Photo Chooser Task
  • Save Contact Task
  • Save Email Address Task
  • Save Phone numbers task
  • Save Ringtone Task

Using Choosers and Launchers

Implementing Launchers and Choosers are pretty simple. Most of the launchers and choosers are available within namespace “Microsoft.Phone.Tasks“.

a. To use a Launcher follow the below general steps:

  1. Create an instance of the task type for the Launcher.
  2. Set any required and optional properties of the task object. These determine the behavior of the task application when it is invoked.
  3. Call the Show method of the task object.


The below example will open a Phone Web Browser with url https://google.com

  private void TestWebBrowserChooser()
            WebBrowserTask webBrowserTask = new WebBrowserTask();
            webBrowserTask.Uri = new Uri("https://www.google.com");

b. To use a Chooser follow the below general steps:

  1. Create an instance of the task type for the Launcher.
  2. Identify the callback method to run after the user completes the task.
  3. Set any required and optional properties of the task object.
  4. Call the Show method of the task object.
  5. Implement the completed event handler to capture data and status after the user completes the task.

Example: (Below example will launch address book and when user completes selecting an address, the call back will happen and data will be passed on to your application)

 private void TestAddressBookChooser()
            AddressChooserTask addressChooserTask = new AddressChooserTask();
            addressChooserTask.Completed += new EventHandler<AddressResult>(addressChooserTask_Completed);

        void addressChooserTask_Completed(object sender, AddressResult e)
            //throw new NotImplementedException();

Pretty simple isn’t it.

But there are few important concepts you need to understand when implementing launchers and choosers.

  1. When using Launchers and Choosers, is that the calling application is either put into a dormant state or tombstoned when another application is launched.
  2. When the new task application is launched, your application is deactivated and is no longer running.
  3. Usually, your application is put into a dormant state by the operating system.
  4. After completing the task, the user can return to your application that was preserved in memory, and it resumes in the same state as before the new application was launched.
  5. However, it is also possible that your application may be terminated by the operating system. In this case, if the user returns to your application, it is a new instance, and the state of your application is not automatically restored.

Hope you enjoy this post. Will write more soon, keep reading it.





April 2012 Update for Microsoft Visual Studio 11 Beta

April 6, 2012 .NET, .NET Framework, All, HotFixes, Microsoft, Updates, VisualStudio, VS11 No comments

Microsoft has released an Update for Visual Studio 11 BETA. April 2012 Update for Visual Studio 11 Beta is a small patch that provides fixes and improvements for the Visual Studio development environment.

For more information about the update, see the Visual Studio 11 Beta Readme File

Download April 2012 Update for Microsoft Visual Studio 11 Beta

Reference Source: Microsoft Download Center

WebSockets endpoint/transport support with WCF 4.5 *New*

April 1, 2012 .NET, All, Communication, HTML5, Microsoft, VisualStudio, VS11, WCF, Web, Web Services, Web Sockets No comments

WebSocket is a web technology providing for bi-directional, full-duplex communications channels, over a single Transmission Control Protocol (TCP) socket. The WebSocket API is being standardized by the W3C, and the WebSocket protocol has been standardized by the IETF as RFC 6455.

WebSocket is designed to be implemented in web browsers and web servers, but it can be used by any client or server application. The WebSocket protocol makes possible more interaction between a browser and a web site, facilitating live content and the creation of real-time games. This is made possible by providing a standardized way for the server to send content to the browser without being solicited by the client, and allowing for messages to be passed back and forth while keeping the connection open. In this way a two-way (bi-direction) ongoing conversation can take place between a browser and the server. A similar effect has been done in non-standardized ways using stop-gap technologies such as comet.

In addition, the communications are done over the regular TCP port number 80, which is of benefit for those environments which block non-standard Internet connections using a firewall. WebSocket protocol is currently supported in several browsers including Firefox and Google Chrome. WebSocket also requires web applications on the server to be able to support it.  [ information reference: Wikipedia ]

Web Sockets endpoint support in WCF 4.5 and .NET Framework 4.5

With upcoming WCF 4.5 – Microsoft has added support for exposing your WCF Services over Web Sockets. Two new bindings have been added to support communication over a WebSocket transport.

1. NetHttpBinding   – A binding designed for consuming HTTP or WebSocket services that uses binary encoding by default.

2. NetHttpsBinding  – A secure binding designed for consuming HTTP or WebSocket services that uses binary encoding by default.

* Using the above bindings now we can create Services listening over Web Sockets using WCF 4.5.

** Web Sockets hosting support has been introduced with IIS 8.0 in Windows 8 and Windows Server 8 beta.

[ information reference: MSDN ]

More References: