Sharing of thoughts and information is what blogging is all about. This way we can learn from each other. Post A Comment!These postings are provided "AS IS" with no warranties, and confers no rights. You assume all risk for your use.
Chris Di LulloSr. IT Pro Marketing Manager Twitter | LinkedIn Pierre Roman Twitter | LinkedIn Mitch Garvis Twitter | LinkedIn Anthony Bartolo Twitter | LinkedIn
If you’ve started reading from this post, you’ll need to go through the previous parts of this series before starting this one: Introduction Part 1: Provisioning and Configuring SQL Azure Part 2: Provisioning a Storage Account Part 3: Configuring the Service Package Part 4: Configuring the Hosted Service, Deploying the Package, and Testing
Almost done! With your testing completed, it’s now time to promote the application from the staging environment to production. With Windows Azure, promoting from staging to production can’t be any easier.
Promoting from Staging to Production
Within a few seconds, you’ll see that the deployment shows Ready and that the environment shows Production.
You’re done! Don’t believe it? Test it.
Testing the Production Application
If you get a DNS error within the first little while after you promote the solution to production, don’t worry. Nothing has gone wrong – the subdomain just hasn’t had time to propagate to the DNS servers used by your ISP. After about 5 to 10 minutes, the solution should come up with no problems.
Once you’re done testing the application and exploring all of the features and functions of the Windows Azure Management Portal, you should remove the web instance, the storage account, and the SQL Azure server and database so as to not incur any charges on your credit card. We’ll go through that next.