Note I say web site – rather than web application.
If you have a web site, which is just a folder of files and stuff rather than a full blown VS project, you can easily deploy into Windows Azure without having to convert to a web app. (Of course you should really think about converting it because you get a better tool experience, debugging etc.)
I’m going to assume you have the Windows Azure SDK installed.
So the first thing is to get your files laid out on disk correctly. For our purposes I have a really simple web site containing a single default.aspx file. This is in a folder named ASPNetRole.
Next you need to create the cscfg and csdef files that Windows Azure requires to build a package. In the folder above I created the 2 files:
ServiceConfig.cscfg looks like this:
ServiceDefinition.csdef looks like this
Make sure the role names match what you want to call your role.
Now you have these 2 files you are all ready to go!
There are 3 tasks you may want to do.
1. Package the web site to run in the local developer fabric.
2. Run the local developer fabric package:
3. Package ready to deploy to Windows Azure.
When you run the last script it will generate the package you need to deploy to Windows Azure. I usually pop the above into 3 script files named prefabric.cmd, runfabric.cmd and buildpackage.cmd.
THIS POSTING IS PROVIDED “AS IS” WITH NO WARRANTIES, AND CONFERS NO RIGHTS