<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/atom.xsl" media="screen"?><feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en-US"><title type="html">One Microsoft Voice</title><subtitle type="html">Helping developers use Microsoft&amp;#39;s platform for the Web.</subtitle><id>http://blogs.msdn.com/b/onemicrosoftvoice/atom.aspx</id><link rel="alternate" type="text/html" href="http://blogs.msdn.com/b/onemicrosoftvoice/" /><link rel="self" type="application/atom+xml" href="http://blogs.msdn.com/b/onemicrosoftvoice/atom.aspx" /><generator uri="http://telligent.com" version="5.6.50428.7875">Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><updated>2012-12-06T08:27:56Z</updated><entry><title>Screencast: Using MySQL Workbench with Windows Azure Web Sites</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/b/onemicrosoftvoice/archive/2013/01/02/using-mysql-workbench-with-windows-azure-web-sites.aspx" /><id>http://blogs.msdn.com/b/onemicrosoftvoice/archive/2013/01/02/using-mysql-workbench-with-windows-azure-web-sites.aspx</id><published>2013-01-02T19:39:00Z</published><updated>2013-01-02T19:39:00Z</updated><content type="html">&lt;p&gt;One of the great things about Windows Azure Web Sites is being able to create a web site in seconds that uses MySQL for your data. With your Azure subscription, you are entitled to a free MySQL database. You can’t manage this database within the Azure portal, but you can connect to it using MySQL Workbench.&lt;/p&gt;  &lt;p&gt;In this screencast, I demonstrate how you can connect to your MySQL database using MySQL Workbench. I also show you how to find out the size of your MySQL database.&lt;/p&gt;  &lt;div style="margin: 0px; padding: 0px; float: none; display: inline;"&gt;&lt;embed src="http://www.youtube.com/v/l-hNncIsjyQ?hd=1" type="application/x-shockwave-flash" wmode="transparent" width="448" height="252" allowFullScreen="true"&gt;&lt;/embed&gt;&lt;/div&gt;  &lt;p&gt;&amp;#160;&lt;/p&gt;  &lt;p&gt;&lt;a href="http://www.mysql.com/products/workbench/" target="_blank"&gt;Download MySQL Workbench&lt;/a&gt; free from the Internet.&lt;/p&gt;  &lt;p&gt;Here is the SQL query that I used in the screencast to determine the size of my database. You will need to change the query so that it uses your database name.&lt;/p&gt;  &lt;blockquote&gt;   &lt;p&gt;&lt;span style="font-family: courier new;"&gt;SELECT table_schema &amp;quot;&lt;em&gt;your_database_name&lt;/em&gt;&amp;quot;,         &lt;br /&gt; sum( data_length + index_length ) / 1024 / 1024 &amp;quot;Database Size in MB&amp;quot;         &lt;br /&gt; FROM information_schema.TABLES GROUP BY table_schema ;&lt;/span&gt;&lt;/p&gt;&lt;/blockquote&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10381892" width="1" height="1"&gt;</content><author><name>Jim Cheshire</name><uri>http://blogs.msdn.com/jamesche/ProfileUrlRedirect.ashx</uri></author><category term="screencast" scheme="http://blogs.msdn.com/b/onemicrosoftvoice/archive/tags/screencast/" /></entry><entry><title>Screencast: Troubleshooting Slow Requests in Windows Azure Web Sites</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/b/onemicrosoftvoice/archive/2012/12/27/screencast-troubleshooting-slow-requests-with-failed-request-tracing.aspx" /><id>http://blogs.msdn.com/b/onemicrosoftvoice/archive/2012/12/27/screencast-troubleshooting-slow-requests-with-failed-request-tracing.aspx</id><published>2012-12-27T23:53:00Z</published><updated>2012-12-27T23:53:00Z</updated><content type="html">&lt;p&gt;&lt;em&gt;This is the first in a series of Microsoft CTS Screencasts on using Windows Azure Web Sites.&lt;/em&gt;&lt;/p&gt;  &lt;p&gt;Troubleshooting performance issues in the cloud can be tough. If you are dealing with slowness for a particular page in your Windows Azure Web Sites site, you can use the Failed Request Tracing feature to find out the cause for the slow response times. If you are using an ASP.NET site, you can use additional tracing features to instrument your code and find exactly where in your code you are experiencing a performance problem.&lt;/p&gt;  &lt;p&gt;Click below to watch the screencast. For best results, use 720p HD quality and fullscreen mode.&lt;/p&gt;  &lt;p&gt;&amp;#160;&lt;/p&gt;  &lt;div style="margin: 0px auto; padding: 0px; float: none; display: block;"&gt;&lt;embed src="http://www.youtube.com/v/U1nHZKtUTNU?hd=1" type="application/x-shockwave-flash" allowfullscreen="true" wmode="transparent" width="448" height="252"&gt;&lt;/embed&gt;&lt;/div&gt;  &lt;p&gt;&amp;#160;&lt;/p&gt;  &lt;p&gt;In this screencast, I used the following XML snippet in my configuration file to configure Failed Request Tracing.&lt;/p&gt;  &lt;blockquote&gt;   &lt;p&gt;&amp;lt;!-- Tracing slow requests using Failed Request Tracing. --&amp;gt;      &lt;br /&gt;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160; &amp;lt;tracing&amp;gt;       &lt;br /&gt;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160; &amp;lt;traceFailedRequests&amp;gt;       &lt;br /&gt;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160; &amp;lt;remove path=&amp;quot;*&amp;quot; /&amp;gt;       &lt;br /&gt;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160; &amp;lt;add path=&amp;quot;*.aspx&amp;quot;&amp;gt;       &lt;br /&gt;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160; &amp;lt;traceAreas&amp;gt;       &lt;br /&gt;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160; &amp;lt;add provider=&amp;quot;ASP&amp;quot; verbosity=&amp;quot;Verbose&amp;quot; /&amp;gt;       &lt;br /&gt;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160; &amp;lt;add provider=&amp;quot;ASPNET&amp;quot; areas=&amp;quot;Infrastructure,Module,Page,AppServices&amp;quot; verbosity=&amp;quot;Verbose&amp;quot; /&amp;gt;       &lt;br /&gt;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160; &amp;lt;add provider=&amp;quot;ISAPI Extension&amp;quot; verbosity=&amp;quot;Verbose&amp;quot; /&amp;gt;       &lt;br /&gt;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160; &amp;lt;add provider=&amp;quot;WWW Server&amp;quot; areas=&amp;quot;Authentication,Security,Filter,StaticFile,CGI,Compression,Cache,       &lt;br /&gt;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160; RequestNotifications,Module,FastCGI&amp;quot; verbosity=&amp;quot;Verbose&amp;quot; /&amp;gt;       &lt;br /&gt;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160; &amp;lt;/traceAreas&amp;gt;       &lt;br /&gt;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160; &amp;lt;failureDefinitions statusCodes=&amp;quot;200-999&amp;quot; /&amp;gt;       &lt;br /&gt;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160; &amp;lt;/add&amp;gt;       &lt;br /&gt;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160; &amp;lt;/traceFailedRequests&amp;gt;       &lt;br /&gt;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160; &amp;lt;/tracing&amp;gt;&lt;/p&gt; &lt;/blockquote&gt;  &lt;p&gt;&lt;strong&gt;Note:      &lt;br /&gt;&lt;/strong&gt;Once you have used this method to troubleshoot a problem, you should turn off Failed Request Tracing in the Azure portal.&lt;/p&gt;  &lt;p&gt;We have a &lt;a href="http://social.msdn.microsoft.com/Forums/en-US/windowsazurewebsitespreview/thread/950e11be-7dd7-4890-8fbb-4edc7659353b" target="_blank"&gt;FAQ thread on the Windows Azure Web Sites forum&lt;/a&gt; that describes how to use Failed Request Tracing to capture a trace when a request takes longer than a specified time. However, I opted to use the 200 status code in this post because it allows us to see the entire request lifecycle.&lt;/p&gt;  &lt;p&gt;I hope you enjoy this screencast. There are more to come!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10381045" width="1" height="1"&gt;</content><author><name>Jim Cheshire</name><uri>http://blogs.msdn.com/jamesche/ProfileUrlRedirect.ashx</uri></author><category term="screencast" scheme="http://blogs.msdn.com/b/onemicrosoftvoice/archive/tags/screencast/" /><category term="performance" scheme="http://blogs.msdn.com/b/onemicrosoftvoice/archive/tags/performance/" /></entry><entry><title>Hosting WordPress in a Subfolder of Your Windows Azure Web Site</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/b/onemicrosoftvoice/archive/2012/12/06/hosting-wordpress-in-a-subfolder-of-your-windows-azure-web-site.aspx" /><id>http://blogs.msdn.com/b/onemicrosoftvoice/archive/2012/12/06/hosting-wordpress-in-a-subfolder-of-your-windows-azure-web-site.aspx</id><published>2012-12-06T14:27:56Z</published><updated>2012-12-06T14:27:56Z</updated><content type="html">&lt;p&gt;&lt;em&gt;This post applies to Windows Azure Web Sites. These steps do not apply if you are using a Web Role.&lt;/em&gt;&lt;/p&gt;  &lt;p&gt;Windows Azure Web Sites makes it quick and easy to create a WordPress blog hosted in Azure. However, if you create a WordPress blog using the Gallery in Windows Azure Web Sites, the blog becomes the root of your website. Many of our customers have asked about creating a WordPress blog in a sub-folder of a site so that it can be accessed with a URL such as www.mysite.com/blog. In this post, I’ll show you how you can host a WordPress blog in a subfolder of your site.&lt;/p&gt;  &lt;p&gt;Here are the steps that we’ll use to add WordPress to a subfolder of an existing site. (I’ve used Roman numerals for these steps so that I can easily refer to them elsewhere in the post without your confusing them with one of the sub-steps.)&lt;/p&gt;  &lt;blockquote&gt;   &lt;p&gt;I.&amp;#160;&amp;#160; Create a temporary WordPress site.&lt;/p&gt;    &lt;p&gt;II.&amp;#160; Download the WordPress site using FTP.&lt;/p&gt;    &lt;p&gt;III. Add the WordPress content to an existing site.&lt;/p&gt;    &lt;p&gt;IV. Delete the temporary WordPress site.&lt;/p&gt;    &lt;p&gt;V.&amp;#160; Link the MySQL database to the existing site now hosting the WordPress blog.&lt;/p&gt; &lt;/blockquote&gt;  &lt;h2&gt;&amp;#160;&lt;/h2&gt;  &lt;h2&gt;I. Create a Temporary WordPress Site&lt;/h2&gt;  &lt;p&gt;The first step in the process is to create a temporary WordPress site in Windows Azure Web Sites that you can then move to your existing site.&lt;/p&gt;  &lt;p&gt;&amp;#160;&lt;/p&gt;  &lt;blockquote&gt;   &lt;p&gt;1. In the &lt;a href="https://manage.windowsazure.com/" target="_blank"&gt;Azure Portal&lt;/a&gt;, click the New button to create a new website.&lt;/p&gt; &lt;/blockquote&gt;  &lt;ol&gt;&lt;/ol&gt;  &lt;p&gt;&amp;#160;&lt;/p&gt;  &lt;p&gt;&lt;a href="http://blogs.msdn.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-01-54-93-metablogapi/5078.NewSite_5F00_74FBF2D9.png"&gt;&lt;img style="margin: 0px 0px 0px 50px; display: inline; background-image: none;" title="NewSite" border="0" alt="NewSite" src="http://blogs.msdn.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-01-54-93-metablogapi/7142.NewSite_5F00_thumb_5F00_6D70836C.png" width="161" height="61" /&gt;&lt;/a&gt;&lt;/p&gt;  &lt;p&gt;&amp;#160;&lt;/p&gt;  &lt;ol&gt;&lt;/ol&gt;  &lt;blockquote&gt;   &lt;p&gt;2. Choose to create a new website from the Gallery.&lt;/p&gt; &lt;/blockquote&gt;  &lt;ol&gt;&lt;/ol&gt;  &lt;p&gt;&amp;#160;&lt;/p&gt;  &lt;p&gt;&lt;a href="http://blogs.msdn.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-01-54-93-metablogapi/5670.SiteFromGallery_5F00_54088032.png"&gt;&lt;img style="margin: 0px 0px 0px 50px; display: inline; background-image: none;" title="SiteFromGallery" border="0" alt="SiteFromGallery" src="http://blogs.msdn.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-01-54-93-metablogapi/6646.SiteFromGallery_5F00_thumb_5F00_734B2705.png" width="542" height="311" /&gt;&lt;/a&gt;&lt;/p&gt;  &lt;p&gt;&amp;#160;&lt;/p&gt;  &lt;ol&gt;&lt;/ol&gt;  &lt;blockquote&gt;   &lt;p&gt;3. Select WordPress from the list of apps in the Gallery.&lt;/p&gt; &lt;/blockquote&gt;  &lt;ol&gt;&lt;/ol&gt;  &lt;p&gt;&amp;#160;&lt;/p&gt;  &lt;p&gt;&lt;a href="http://blogs.msdn.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-01-54-93-metablogapi/1780.WordPressGallery_5F00_5D641B37.png"&gt;&lt;img style="margin: 0px 0px 0px 50px; display: inline; background-image: none;" title="WordPressGallery" border="0" alt="WordPressGallery" src="http://blogs.msdn.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-01-54-93-metablogapi/2656.WordPressGallery_5F00_thumb_5F00_15A29250.png" width="549" height="371" /&gt;&lt;/a&gt;&lt;/p&gt;  &lt;p&gt;&amp;#160;&lt;/p&gt;  &lt;blockquote&gt;   &lt;p&gt;4. Proceed through the wizard to create the WordPress site.&lt;/p&gt; &lt;/blockquote&gt;  &lt;p&gt;&amp;#160;&lt;/p&gt;  &lt;h2&gt;II. Download the WordPress Site Using FTP&lt;/h2&gt;  &lt;p&gt;The next step is to download all of the files for the WordPress site to your local machine so that you can transfer them to the existing site. I use &lt;a href="http://filezilla-project.org/" target="_blank"&gt;FileZilla&lt;/a&gt;, a free FTP client, to do this. &lt;/p&gt;  &lt;p&gt;To open the site using FTP, you’ll use the information contained in the &lt;em&gt;publish profile&lt;/em&gt; for the site. The publish profile is an XML file that defines the different methods that can be used to publish to the website using Visual Studio, Web Matrix, or Web Deploy. Each publish method is defined in the publish profile using a &amp;lt;publishProfile&amp;gt; section. One of these sections defines the URL, username, and password that you can use to access the site with an FTP client.&lt;/p&gt;  &lt;ol&gt;   &lt;li&gt;&lt;a href="http://blogs.msdn.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-01-54-93-metablogapi/2234.PublishProfile_5F00_02F4B42F.png"&gt;&lt;img style="float: right; display: inline; background-image: none;" title="PublishProfile" border="0" alt="PublishProfile" align="right" src="http://blogs.msdn.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-01-54-93-metablogapi/6740.PublishProfile_5F00_thumb_5F00_626D747C.png" width="239" height="251" /&gt;&lt;/a&gt;From the WordPress site’s dashboard in the Azure Portal, click the Download Publish Profile link in the Quick Glance section.&lt;/li&gt;    &lt;li&gt;Save the publish profile to your local machine.&lt;/li&gt;    &lt;li&gt;Open the publish profile in Notepad or in another text editor.&lt;/li&gt;    &lt;li&gt;Locate the FTP publish profile for your site and use the URL, username, and password to log into the site with your FTP client. (See &lt;a href="http://weblogs.asp.net/bleroy/archive/2012/06/12/azure-web-sites-ftp-credentials.aspx" target="_blank"&gt;Bertrand’s blog post&lt;/a&gt; for details on FTP credentials and where they are located in the publish profile.)&lt;/li&gt;    &lt;li&gt;Log into the WordPress site you created in step I and copy the entire contents of the site/wwwroot folder to your local machine. (You can copy these files to any folder you choose.)&lt;/li&gt; &lt;/ol&gt;  &lt;p&gt;&lt;strong&gt;&lt;font size="2"&gt;Bonus Information on Credentials&lt;/font&gt;&lt;/strong&gt;&lt;/p&gt;  &lt;p&gt;The credentials that you obtained from the publish profile are site-level credentials. They are specific to the website and if you share them with a co-administrator of your website, he or she can use them to access the site as well. In addition to the site-level credentials, you can also access the site using user-level credentials. &lt;/p&gt;  &lt;p&gt;User-level credentials are tied to your Microsoft account (the account you use to sign into Azure.) Windows Azure Web Sites calls user-level credentials &lt;em&gt;deployment credentials&lt;/em&gt;, and you can set them using the Reset Deployment Credentials link in the Quick Glance section.&lt;/p&gt;  &lt;p&gt;Since deployment credentials are user-level credentials, you can use them with any of your websites. However, you will need to precede your username with the site name and a backslash. In other words, if my deployment credentials username is &lt;strong&gt;Jim&lt;/strong&gt;, to use it to open a site named &lt;strong&gt;WordPressTest&lt;/strong&gt;, I would use the username &lt;strong&gt;WordPressTest\Jim&lt;/strong&gt;. &lt;/p&gt;  &lt;p&gt;You can read more about user-level and site-level credentials in &lt;a href="https://github.com/projectkudu/kudu/wiki/Deployment-credentials" target="_blank"&gt;David Ebbo’s entry&lt;/a&gt; in GitHub.&lt;/p&gt;  &lt;h2&gt;III. Add the WordPress Content to an Existing Site&lt;/h2&gt;  &lt;p&gt;The third step involves adding a new folder to your existing site and then copying the WordPress files into that folder.&lt;/p&gt;  &lt;blockquote&gt;   &lt;p&gt;1. Open your existing site in your FTP client. (You’ll need to use the proper FTP credentials for the site. You can obtain those using the same steps you used in step II.)&lt;/p&gt;    &lt;p&gt;2. Create a new directory to hold the WordPress blog. In this example, I’ve named that directory &lt;strong&gt;blog&lt;/strong&gt;.&lt;/p&gt;    &lt;p&gt;&amp;#160;&lt;/p&gt; &lt;/blockquote&gt;  &lt;blockquote&gt;   &lt;p&gt;&lt;a href="http://blogs.msdn.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-01-54-93-metablogapi/3618.BlogFolder_5F00_77E18231.png"&gt;&lt;img style="display: inline; background-image: none;" title="BlogFolder" border="0" alt="BlogFolder" src="http://blogs.msdn.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-01-54-93-metablogapi/2046.BlogFolder_5F00_thumb_5F00_44A548C8.png" width="572" height="409" /&gt;&lt;/a&gt;&lt;/p&gt;    &lt;p&gt;&amp;#160;&lt;/p&gt; &lt;/blockquote&gt;  &lt;blockquote&gt;   &lt;p&gt;3. Copy the WordPress files you downloaded in step II into the new folder you created in your existing website.&lt;/p&gt;    &lt;p&gt;&amp;#160;&lt;/p&gt; &lt;/blockquote&gt;  &lt;blockquote&gt;   &lt;p&gt;&lt;a href="http://blogs.msdn.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-01-54-93-metablogapi/6443.CopyFiles_5F00_5CC8B323.png"&gt;&lt;img style="border: 0px currentcolor; display: inline; background-image: none;" title="CopyFiles" border="0" alt="CopyFiles" src="http://blogs.msdn.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-01-54-93-metablogapi/7026.CopyFiles_5F00_thumb_5F00_54D110C1.png" width="584" height="533" /&gt;&lt;/a&gt;&lt;/p&gt; &lt;/blockquote&gt;  &lt;p&gt;&amp;#160;&lt;/p&gt;  &lt;h2&gt;IV. Delete the Temporary WordPress Site&lt;/h2&gt;  &lt;p&gt;You no longer need the temporary WordPress site you created in step I, so the next step is to delete that site. &lt;strong&gt;Be careful not to delete the linked MySQL database when you do this or you will break the new WordPress blog!&lt;/strong&gt;&lt;/p&gt;  &lt;p&gt;&amp;#160;&lt;/p&gt;  &lt;blockquote&gt;   &lt;p&gt;1. Select the temporary WordPress site in the Azure Portal.&lt;/p&gt;    &lt;p&gt;2. Click the Delete button to delete the website.&lt;/p&gt; &lt;/blockquote&gt;  &lt;p&gt;&amp;#160;&lt;/p&gt;  &lt;blockquote&gt;   &lt;p&gt;&lt;a href="http://blogs.msdn.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-01-54-93-metablogapi/1541.DeleteWPSite_5F00_5AABB45A.png"&gt;&lt;img style="display: inline; background-image: none;" title="DeleteWPSite" border="0" alt="DeleteWPSite" src="http://blogs.msdn.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-01-54-93-metablogapi/8078.DeleteWPSite_5F00_thumb_5F00_33053830.png" width="577" height="393" /&gt;&lt;/a&gt;&lt;/p&gt; &lt;/blockquote&gt;  &lt;p&gt;&amp;#160;&lt;/p&gt;  &lt;blockquote&gt;   &lt;p&gt;3. Make sure that the checkbox for your linked MySQL database instance is &lt;em&gt;unchecked&lt;/em&gt;. You do NOT want to delete the linked MySQL database because the WordPress blog you copied in the previous step is still using the database.&lt;/p&gt; &lt;/blockquote&gt;  &lt;p&gt;&amp;#160;&lt;/p&gt;  &lt;blockquote&gt;   &lt;p&gt;&lt;a href="http://blogs.msdn.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-01-54-93-metablogapi/7827.DeleteConfirm_5F00_003531BC.png"&gt;&lt;img style="display: inline; background-image: none;" title="DeleteConfirm" border="0" alt="DeleteConfirm" src="http://blogs.msdn.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-01-54-93-metablogapi/1641.DeleteConfirm_5F00_thumb_5F00_78A9C24E.png" width="507" height="348" /&gt;&lt;/a&gt;&lt;/p&gt; &lt;/blockquote&gt;  &lt;p&gt;&amp;#160;&lt;/p&gt;  &lt;blockquote&gt;   &lt;p&gt;4. Click the Yes button in the lower-right corner of the Delete Confirmation dialog show above to delete the site and keep the MySQL database. &lt;/p&gt; &lt;/blockquote&gt;  &lt;p&gt;&amp;#160;&lt;/p&gt;  &lt;h2&gt;V. Link the MySQL Database to the Existing Website&lt;/h2&gt;  &lt;p&gt;The final step is to link the MySQL database to the existing website that now hosts your WordPress blog. &lt;/p&gt;  &lt;blockquote&gt;   &lt;p&gt;1. From the Azure Portal, select the existing website that is hosting your WordPress blog.&lt;/p&gt;    &lt;p&gt;2. Click the Linked Resources tab.&lt;/p&gt;    &lt;p&gt;3. Click the Link a Resource link.&lt;/p&gt; &lt;/blockquote&gt;  &lt;p&gt;&amp;#160;&lt;/p&gt;  &lt;blockquote&gt;   &lt;p&gt;&lt;a href="http://blogs.msdn.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-01-54-93-metablogapi/3617.LinkedResources_5F00_7EF098DC.png"&gt;&lt;img style="display: inline; background-image: none;" title="LinkedResources" border="0" alt="LinkedResources" src="http://blogs.msdn.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-01-54-93-metablogapi/7418.LinkedResources_5F00_thumb_5F00_05376F6B.png" width="516" height="187" /&gt;&lt;/a&gt;&lt;/p&gt; &lt;/blockquote&gt;  &lt;p&gt;&amp;#160;&lt;/p&gt;  &lt;blockquote&gt;   &lt;p&gt;4. Click the Link an Existing Resource link.&lt;/p&gt; &lt;/blockquote&gt;  &lt;p&gt;&amp;#160;&lt;/p&gt;  &lt;blockquote&gt;   &lt;p&gt;&lt;a href="http://blogs.msdn.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-01-54-93-metablogapi/7180.LinkExisting_5F00_2B9952B6.png"&gt;&lt;img style="display: inline; background-image: none;" title="LinkExisting" border="0" alt="LinkExisting" src="http://blogs.msdn.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-01-54-93-metablogapi/1122.LinkExisting_5F00_thumb_5F00_6AF70646.png" width="524" height="348" /&gt;&lt;/a&gt;&lt;/p&gt; &lt;/blockquote&gt;  &lt;p&gt;&amp;#160;&lt;/p&gt;  &lt;blockquote&gt;   &lt;p&gt;5. Click the MySQL Database link.&lt;/p&gt; &lt;/blockquote&gt;  &lt;p&gt;&amp;#160;&lt;/p&gt;  &lt;blockquote&gt;   &lt;p&gt;&lt;a href="http://blogs.msdn.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-01-54-93-metablogapi/7180.LinkMySQL_5F00_75482AA6.png"&gt;&lt;img style="display: inline; background-image: none;" title="LinkMySQL" border="0" alt="LinkMySQL" src="http://blogs.msdn.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-01-54-93-metablogapi/3276.LinkMySQL_5F00_thumb_5F00_6DBCBB39.png" width="534" height="355" /&gt;&lt;/a&gt;&lt;/p&gt; &lt;/blockquote&gt;  &lt;p&gt;&amp;#160;&lt;/p&gt;  &lt;blockquote&gt;   &lt;p&gt;6. Check the checkbox to agree to ClearDB’s legal terms and then click the Yes button to link the MySQL database to your website.&lt;/p&gt; &lt;/blockquote&gt;  &lt;p&gt;&amp;#160;&lt;/p&gt;  &lt;blockquote&gt;   &lt;p&gt;&lt;a href="http://blogs.msdn.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-01-54-93-metablogapi/0243.MySQLServer_5F00_2D1A6ECA.png"&gt;&lt;img style="display: inline; background-image: none;" title="MySQLServer" border="0" alt="MySQLServer" src="http://blogs.msdn.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-01-54-93-metablogapi/7485.MySQLServer_5F00_thumb_5F00_6C78225A.png" width="540" height="343" /&gt;&lt;/a&gt;&lt;/p&gt; &lt;/blockquote&gt;  &lt;p&gt;&amp;#160;&lt;/p&gt;  &lt;p&gt;You can now browse to your WordPress blog by browsing to the URL for the folder you created in step III. For example, I can browse to my WordPress site by browsing to http://MyMvcSite.AzureWebSites.net/blog.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10375262" width="1" height="1"&gt;</content><author><name>Jim Cheshire</name><uri>http://blogs.msdn.com/jamesche/ProfileUrlRedirect.ashx</uri></author></entry></feed>