Deploying Your App to the Cloud

by mheydt 9. November 2008 15:24 >
My previous post showed how to create a simple asp.net application that runs on the local development fabric.  This post, as promised, will follow up and show how to move your application into the azure services cloud.

The first think you need to do is go into the azure services developer portal and create a new project.



Select the 'New Project' link, and you will be taken to the new project page.  Note that you will have to have claimed your token(s) to be able to select the items on the following page:





Click on the 'Hosted Services' item, and you will be taken to a page that allows you to create a new project:


Next will take you to a form that allows you to specify the name of the service, but is really just the DNS name that will be assigned to the web app when in production:



When that is complete, you will be taken back to the main page which will have changed its look to be as follows:




What this is showing is that for the project that we just created, we have two places to run it, a staging environment, and a production environment.  This is actually quite nice to have as it will allow you to upload and test prior to going live.

So, we have a place in the cloud for our app.  Now how do we get it into the cloud?  Click on deploy underneath the staging graphic, and you will see a form as follows, that allows you to specify your two service configuration files that you used in visual studio (but after publishing them from vs.net):



The files I specified were a result of publishing from vs.net using the 'Publish' menu item.  This will create these packages, open the azure portal, and open an explorer folder where the files are located.

When pressing the deploy button, you will be presented with a dialog telling you the files are being copied:




And when the copy is complete, you will be taken back to the main page where you will be show that your package is deploying:




Upon completion of the deployment you will be presented with options for managing your staging environment.  At this point, we want to press the run button to start the application (this will spin for a few minutes):




When that is complete, you'll see something like this:





You can now run the app by clicking on the given link:




Voila!

Notice also that you now have the option to move the solution to deployment, where it can be accessed with a production URL.  We'll pass on the option for now.

Right now this app is not very useful as it has no ability to store data, either files or in a database.  My next post should be on starting to use the data storage facilities of azure to enable these features.

Tags:

Azure

blog comments powered by Disqus

about the author

I'm a .NET, XAML, and iOS polyglot that loves playing with new things and making cool and innovative stuff.  I am also a Mac junkie.

I am Principal Technologist for SunGard Global Services in NYC, in their Advanced Technologies practice, and I work extensively with SunGard's energy and financial customers.

Note the the posting on this blog are my own and do not represent the position, strategies or opinions of SGS.

twitter

I can't stop thinking big!
Sunday 1:08AM via WindowsLive
Just watched Moneyball. That's my pick for best movie this year.
Saturday 3:51PM via WindowsLive
@vincebelpiede: Report: Skype For Windows Phone Beta Imminent http://t.co/KYNjgg1L#mhtnd
Wednesday 8:39AM via Twitter for Mac
@mashable: Kinect Fusion Will Turn Gaming (and More) Into a 3D Fun House - http://t.co/Ihrq2fY2#mhtnd
Wednesday 8:39AM via Twitter for Mac
New Kinect SDK: http://t.co/57MvA5L5 #mhtnd
Wednesday 8:39AM via Twitter for Mac
Follow me on Twitter

recent comments

None

month list