In this tutorial we are going to see how to deploy our application ASP.Net Web Application to the Virtual Machine which we created newly in our earlier article (Windows Azure Virtual Machines – Meet Azure Edition). We are going to take the newly created F5debug Metro Website and deploy it to the new Virtual Machine which we have created. Let us start the step by step process to see how we can achieve this task. [more]
Step 1 : Open the project in Visual Studio 2010 and publish the website to a folder. We will get the published files as shown in the screen below.
Now right click on the folder and you can see the option Open the website with Microsoft WebMatrix if the WebMatrix is installed on the system as shown in the screen below. Believe me WebMatrix is very much powerful tool which Microsoft provided to the developers manage and manipulate the website easily.
Now WebMatrix will open the website and the respective files in the that are should be deployed to the hosting environment as shown in the screen below.
Now run the application by Clicking on the Run button at the top ribbon, this is to just check if the published files are working good in the WebMatrix application. WebMatrix has an inbuilt webserver which is used to run the application easily in a preferred browser as shown in the screen below.
Now we can see that the application is running good in local server (notice that it runs in localhost). Now we zip the application and keep it ready to transfer the files to the new Virtual environment. We can use FTP or normal file transfer protocols that are used to transfer the application files to the hosting environment. Connect to the virtual machine by connecting from the portal using the Connect button at the bottom as shown in the screen below.
Now we are in the Virtual machine and its like the server which we are going to use to deploy our application. Unzip the package and put it on a particular folder where we are going to make the virtual directory as shown in the screen below.
The environment is a raw infrastructure where we will not have anything installed. To run our application we need basically IIS as a web server and .Net framework 4.0. Download the latest build of .Net Framework 4.0 using the link and install on the Virtual Machine using the link http://www.microsoft.com/en-in/download/details.php?id=17718
Once downloaded and installed now go to the Control panel –> Turn Windows Features ON/OFF and enable the IIS Webserver configuration as shown in the screen below. This will take quite some time to install the features and get it published, just restart the machine once which will be very effective in setting up the environment.
Once all the required softwares and packages are installed now we are well set to configure the application. To start with first open IIS and create your own website in IIS Manager (Delete the Default WebSite and create one on your own). Now create a new WebSite as shown in the screen below.
New Website requires some basic details, enter as shown in the screen below. If you want a separate Application Pool then create on your own and map it with the new Website which we are going to create now.
Once we configured with the above changes, click on OK to complete the setting and restart the Web Server once by clicking on the restart the right side menu. Now right click on the website and select Manage Website and click on Browse as shown in the screen below.
We can see our application is loaded in the default browser as shown in the screen below. These are the steps to required to deploy our application over the Virtual machine on the cloud.
Now set the default page in the IIS Manager, by selecting the Default Document option from the Feature view and adding Home.php as the primary default page as shown in the screen below.
Now run the application by clicking on Browse Website and we can see the home page which we selected as shown in the screen below.
Let us see in our next article how to configure Azure to access this website from the outside environment as this website is not accessible with in the server.