Creating an On Premise Database and MVC Web Application and Migrating to Windows Azure and SQL Azure-Step 8 of 10

Previous Posts that you should review Step 1 https://blogs.msdn.com/b/brunoterkaly/archive/2010/06/12/creating-an-on-premise-database-and-mvc-web-application-and-migrating-to-windows-azure-and-sql-azure-step-1-of-10.aspx Step 2 https://blogs.msdn.com/b/brunoterkaly/archive/2010/06/11/creating-an-on-premise-database-and-mvc-web-application-and-migrating-to-windows-azure-and-sql-azure.aspx Step 3 https://blogs.msdn.com/b/brunoterkaly/archive/2010/06/27/creating-an-on-premise-database-and-mvc-web-application-and-migrating-to-windows-azure-and-sql-azure-step-3-of-10.aspx Step 4 https://blogs.msdn.com/b/brunoterkaly/archive/2010/06/28/creating-an-on-premise-database-and-mvc-web-application-and-migrating-to-windows-azure-and-sql-azure-step-4-of-10.aspx Step 5 https://blogs.msdn.com/b/brunoterkaly/archive/2010/06/28/creating-an-on-premise-database-and-mvc-web-application-and-migrating-to-windows-azure-and-sql-azure-step-5-of-10.aspx Step 6 https://blogs.msdn.com/b/brunoterkaly/archive/2010/06/30/creating-an-on-premise-database-and-mvc-web-application-and-migrating-to-windows-azure-and-sql-azure-step-6-of-10.aspx Step 7 https://blogs.msdn.com/b/brunoterkaly/archive/2010/07/01/creating-an-on-premise-database-and-mvc-web-application-and-migrating-to-windows-azure-and-sql-azure-step-7-of-10.aspx

This Blog Post is about…

Steps in the this blog post Copying the controller code from the on-premise MVC application to the cloud-based MVC application Copying the view code from the on-premise MVC application to the cloud-based MVC application Copying the connection string code (may be a duplicate step) Running the cloud-based MVC application locally on the development fabric

This is a simple copy and paste effort  Our on-premise application is the sourceWe will copy from MvcOnPremise to MvcAzure_WebRole

Connection String  Update Web.configA simple copy and paste operation is all that is required here.

The Development Fabric  What is it? The development fabric simulates the Windows® Azure™ fabric on your local computer so that you can run and test your service locally before deploying it. The development fabric allows you to debug and fine-tune the behavior of your service before it is deployed. It provides a user interface for observing and managing local service deployments. There are a few differences between the development environment and Windows Azure that may affect how your service runs in one or the other. You can attach a debugger to a role instance running in the development fabric. It's not possible to attach a debugger to a role running in Windows Azure; any live debugging information must be written to the logs. A role instance running in the development environment has access to the local Global Assembly Cache (GAC), the registry, machine configuration file, and other local system components. These components are not available to a role instance that is running in Windows Azure. Developers should use care to avoid relying on local system components from code running in a role.

Getting close…Almost fully deployed to the cloud

 

Next blog post

Uploading your application to the Azure Portal The "Publish" command The Azure Web Portal Understanding the Deployment Package The Publish command creates 2 files: (1) the packaged application; (2) the configruation file Adding a new Hosted Web Service Defining a "Service Label" Defining the "Public Service Name," which is the URL of your hosted service Selecting the data center that will hosted your service (MVC Application)