Database Reference
In-Depth Information
You could have created the same project as a regular ASP.NET application and obtained the same
result. However, because you're about to deploy this project on Windows Azure, you must create a cloud
project.
■
Note
This chapter assumes you've configured the SQL Azure firewall correctly. Also, connecting from a
Windows Azure service requires you to set the “Allow Microsoft Services access to this server” option in the
firewall configuration. If you get a connection error stating that you aren't allowed to connect from a specific IP
address, see Chapter 3 for detailed information about how to properly set up the SQL Azure firewall.
Deploying an ASP.NET Application in Windows Azure
You're almost there. In this section, you walk through the steps of deploying the ASP.NET application in
the cloud:
1.
You need to publish your project. Right-click AzureExample, and click Publish.
This action, upon success, opens two windows:
•
Windows Explorer
. This window contains the two files you need to deploy in
Windows Azure. You need this window soon, so don't close it.
•
Internet Explorer
. The Windows Azure Portal is automatically shown as well,
because you need to deploy the binaries there. You may be prompted to sign
in first.
2.
When you've logged in, the Internet Explorer window shows you the home
page for your Windows Azure projects. Click the Windows Azure project under
which you previously created the AzureExample service.
3.
You should see the page shown in Figure 9-1 at the beginning of this chapter.
Click AzureExample, which should bring you to what you saw earlier in Figure
9-4.
4.
On the right side of the browser page is a vertical bar with a left-pointing
triangle. Click the triangle to open a split page with both Production and
Staging sections, as shown in Figure 9-15. Deploying in staging creates a
temporary service that you can use to test before promoting to the final public
URL. This way, you can test that your application is working as desired before
deploying it.
