Migration of an Existing On-Premise ASP.NET 4.0 Web Application to Windows Azure Part – I


In this world of Cloud, it’s very necessary to run your enterprise business apps in Cloud & provide the solution of better scalability, elasticity , High Availability & 24*7 on features to your customers.

  • Windows Azure is Platform as a Service (PAAS) model which helps to upgrade us in such a service. In this article , an existing on-premise enterprise healthcare application has been migrated into cloud & hosted in Microsoft Data – Centers.
  • To start working with Microsoft Windows Azure in Visual Studio 2010, Download the Windows Azure SDK from Azure website.  http://www.microsoft.com/windowsazure/sdk
  •    Now , First load your existing enterprise asp.net 4.0 application into visual studio & then in the solution explorer of the project right click on the solution & click Add-> New Project.

  • Now Select a new Windows Azure Project & named it & save it in the same folder of your existing on-premise application.
  •  In the Roles folder of your Windows Azure Project , Right Click, select Add & choose Existing Web Role in Solution. 
  • Now, check your existing asp.net web application has been migrated as a WebRole in Windows Azure Project.  Next , Set up your Windows Azure hosting environment. During compilation of your Windows Azure application in your development machine , you may encounter the following error:
     
  • Resolution: To solve this error, Open Windows Azure SDK Command Prompt in elevated mode & run the following command.
C:\Program Files\Windows azure SDK\v1.3\bin\ DSINIT /SQLINSTANCE:YourSQLServerInstanceName /Forcecreate  
  • If you dont have .SQLEXPRESS  as default instance of your SQL Server instance then you can modify the command as
C:\Program Files\Windows azure SDK\v1.3\bin\ DSINIT/sqlInstance:. 
  •   Now , You will get the following prompt for initialization of  Azure Storage Emulator in development fabric.
  • Next , Build your complete project solution & run the Windows Azure Project with existing ASP.NET 4.0 web application. During the debugging you will see the compute emulator  & storage emulator in your local dev fabric .

  •  Check out your on-premise existing asp.net web application migrated to windows azure & running in azure compute emulator in local development fabric.

  • To deploy the application , right click on Azure Project & Click Publish & create package (.cspkg ).
    
  • Now, select the radio button of Create Service Package Only otherwise select the second option if you would like to configure your Windows Azure Hosted service details in Visual Studio.
  • Build the Azure Service Package File (.cspkg) & Service Configuration (.cscfg) in Windows Explorer.
  • Next , Log on Windows Azure Developer portal with Windows Live ID with valid Azure Subscription & continue deployment.
Advertisements

SQL Server 2012 RC Installation Step by Step


SQL Server 2012 RC(Release Candidate) published on November 17th, 2011 as official product from Microsoft. The Release candidate has several bug fixes for BI (Business Intelligence) , Data Synchronization & High Availability.

  • Compared to CTP3 Denali is more compact in release mode & available in five different forms (both x86 & x64):
  • Express
  • Express with Tools
  • SQL Server 2012 Management Studio
  • Express DB (Local DB only)
  • Express with Advance Series(With SSRS, Full Text Search).

Download Today: http://www.microsoft.com/download/en/details.aspx?id=28151&WT.mc_id=aff-n-in-loc–pd

Next the Step by Step installation guide:

Extract the Express with Advanced Series SQL Server 2012 .exe as start installation as new instance:

Check the box : I accept the licence terms.

Next put you Features installation after verifying setup rules with Windows Domain settings.

Next , put the Installation Rules with Instance name that will re required to identify your SQL Server 2012 instance in your system.

Next , after calculating  Disk Space Requirements, it will start to check Server Configuration. Put your choice to set the instance of your SQL Server with Windows  domain a/c Login or Mixed Mode(Windows + SQL Server ) with sa account mode.

Next , if you would like to provide FILESTREAM configuration with SQL Server 2012 , you can configure it here.

Similar to User Instance Configuration ,

Next , Check out the box if you would like to install SQL Server Reporting Services 2012 with SQL Server Instance with Sharepoint integration.

Next , Start your Installation process of SQL Server 2012 & Check out the progress bar.

Next , you are done with your installation , so next explore the latest updates of SQL Server 2012 denali in developer preview.

 

Explore the latest SQL Server 2012 book in evaluation mode which will be in release on Spring 2012.

Download from here: https://skydrive.live.com/?cid=7f185b0e5a1ba82e#!/?cid=7f185b0e5a1ba82e&sc=documents&uc=1&nl=1&id=7F185B0E5A1BA82E%21142!cid=7F185B0E5A1BA82E&id=7F185B0E5A1BA82E%21142

So, now Work & explore your favourite database SQL Server 2012 & provide feedback.

Sharepoint 2010 With Windows Azure Development Agenda


The Sharepoint 2010 with Windows Azure Training kit consists of  useful hands on labs , presentations & Video presentations.

The hands on labs mainly focuses on :

  • Windows Azure Marketplace DataMarket
  • Introduction to SQL Azure
  • Windows Azure Overview
  • Sharepoint 2010 development with Visual Studio 2010.
  • Consuming Windows Communication foundation services from Sharepoint 2010 & Infopath 2010.
  • Integrating Windows Azure with Office 2010.
  • Geospatial applications using Sharepoint 2010 , SQL Azure & Bing Maps.
  • Securing Sharepoint 2010  with Azure.
  • Sharepoint 2010 with Blob Storage.
  • Sharepoint with Windows Azure Hosted services.
  • Sharepoint with Windows Azure Event Handlers.
  • Windows Azure with Sharepoint workflow using Azure Worker role with TCP endpoints.

Transient Fault Handling Framework for SQL Azure, Azure Storage Services


SQL Azure databases is a distributed system in which each physical server hosts many databases. This sharing of resources leads to capacity constraints on operation throughput. SQL Azure handles these capacity by throttling operations & closing connections that are using too many resources. SQL Azure also closes connections when it alleviates operational hot spots by switching from a primary  SQL Azure database to one of its two backup databases.

One of the cloud development strategy is “Design for Failure” . It’s important that applications using SQL Azure being designed to handle failures appropriately.

There are two kinds of error:

1. Permanent Error: Indicating failure of a part of the system.

2. Transient Error: Existing only a brief time.

Permanent errors may be the indicate the logical problem with the application – and handle transient errors gracefully by retrying the operation that led to the error in hope that it does not recur. A dropped connection should be regarded as transient and application should respond to a dropped connection by opening new connection and retrying the operation.

There remains the problem of distinguishing permanent from transient errors. This can be done by comparing the error returned from a failed operation with known list of transient errors. An application can therefore include a retry mechanism that checks the status of operations and retries any operations that experienced a transient error.

 

The Windows Azure Appfabric Customer Advisory team has made available on MSDN code gallery the source code & pre-compiled assemblies for Transient Fault Handling Framework for SQL Azure , Azure Storage Services , Azure Appfabric Service Bus & Caching Services.

Download Here:  http://code.msdn.microsoft.com/Transient-Fault-Handling-b209151f              (C# Code)

  • Features of the framework:
  • Provides the foundation for building high extensible logic for handling a variety of transient conditions, not limited to SQL Azure.
  • Supports a range of pre-defined retry policies (Fixed retry interval, Progessive retry interval)
  • Supports seperate retry policy for SQL  connections & SQL Commands for adding flexibility.

 

 

 

Windows Azure Toolkit for Social Gaming !!!


The Windows Azure toolkit for social games helps to build social games in Azure.  The platform enhances the future of gaming industry in cloud & also proving support for compute, storage , on demand content delivery & networking capabilities.  The future of Azure platform focuses on HTML5 with core support in out of browser enhancements.

Tankster

The Windows Azure Toolkit for Social Games also comes with a new proof-of-concept game called Tankster from industry innovator Grant Skinner and his team atgskinner.com.

image

Tankster is built with HTML5 and comes complete with reusable server side code and documentation. It also supports a variety of social interactions including messaging, wall posts, and comments while player achievements and game stats are presented on a live leaderboard so gamers can interact with each other—what’s a social game without being able to talk trash?

Build games with Windows Azure & make it operate on Windows Phone. Enhance XNA gaming !!!

Download : http://watgames.codeplex.com/

 

Windows Azure Toolkit for Windows 8


The Windows Azure Toolkit for Windows 8 is released to make development easy for Windows Metro style application that can harness the power of Windows Azure Compute and Storage. The template is based on Windows Push Notification services existing with Windows Phone 7 applications.

Technologies:

  • ASP.NET MVC 3
  • Windows Azure SDK 1.4.1 Refresh
  • Windows Metro style Javascript application project

The process of sending a notification requires few steps:

  1. Request a channel. Utilize the WinRT API to request a Channel Uri from WNS. The Channel Uri will be the unique identifier you use to send notifications to an application instance.
  2. Register the channel with your Windows Azure cloud services. Once you have your channel you can then store your channel and associate it with any application specific data (e.g user profiles and such) until your services decide that it’s time to send a notification to the given channel
  3. Authenticate against WNS. To send notifications to your channel URI you are first required to Authenticate against WNS using OAuth2 to retrieve a token to be used for each subsequent notification that you push to WNS.
  4. Push notification to channel recipient. Once you have your channel, notification payload and WNS access token you can then perform an HttpWebRequest to post your notification to WNS for delivery to your client.

This slideshow requires JavaScript.

%d bloggers like this: