Azure Developer Task Six: Azure managed asp.net application based on Silverlight

This article focuses on how to host asp.net applications in a new Azure portal.

Windows Azure's portal has completely changed. It is now based on Silverlight. Almost all of the information is on the same page, and almost all operations can be done in one page. Now it is through the Properties window of the deployment, the Properties window of the role instance, and the Properties window of the managed service to provide various extensions, and the OS configuration for the swap VIP can now be done through the Ribbon control above. The left pane contains an online "How to" wizard and some options for doing other things.

As for the appearance of the new portal, I will discuss it in more detail in future articles. This article focuses on hosting asp.net applications in a new Azure portal.

First of all:

1, open visual Studio.

2, create a new project, under the "Cloud" tab, select the Windows Azure Project template.

3, select "ASP.net Web role" and click the arrow button to the right.

4, in order to test, make some changes in "default.aspx".
5, right click on the cloud item and choose "Publish". Select "Create Service Package only" from the two options given.

Click the "OK" button, and then you will see a successful release message, and two files will be created automatically.

1, package file (. cspkg)

2, configuration file (. csdef)

To host applications in Azure, we need to provide the full path to these files. So, you should record this path.

This application is run and started on the local creator fabric. Log on to Azure's development portal. After the login is successful, you will see an option to migrate to the new Azure portal. Select this option. You can move to a new portal without any worries, because you can switch back to the old portal at any time.

In the left pane, you can see that a managed service is listed. I created a managed service that was listed as a count next to the Hosted service option. To create a new service, you can click on the "Hosted service,storage account & CDN" option.

You can create a new managed service

I have created a managed service called "Firstapplication". Here we deploy a asp.net Web application in this managed service.

Click "Firstapplication" and click "New Staging Deployment" above.

Note that the "DebugMode" here is the name of my subscription.

After clicking on the "New staging Deployment" in the top Ribbon, the following window pops up.

We need to provide the name of the deployment, and then we need to browse to the package file and configuration file. We created and packaged a asp.net application on the local system. So we can choose the "Browse locally" option. If our profile and package files are in some memory (for example, BLOBs), then we can choose the "Browse Storage" option.

During local browsing, provide the exact path to your package file and configuration file.

The deployment name we provide is "Test1demo". When you browse to a package file and a configuration file, click the "OK" button.

When I clicked on the "OK" button, I got the following warning.

When I clicked "See More Details", I saw this warning about only one instance of the Web role.

If you want to increase the number of instances of the Web role yourself, you can ignore this warning and click Yes.

If you click OK, you can see some change information about the various deployment phases.

After a while, you will see the "Ready" message as shown below.

Your application is now hosted on Azure's staging server. Click on the deployment name (in this case, the deployment name is "Test1demo"). After clicking on the deployment name, click the URL of the DNS server in the "Properties" tab and open the ASP.net Web application hosted in Azure in a browser.

Original name: Windows Azure for developers Task 6:hosting asp.net creator in New Silverlight based Azure Portal Author: Dhananjay Kumar