没有合适的资源?快使用搜索试试~ 我知道了~
首页掌握Azure Web App开发:最新开发者指南
"《Azure Web App开发者参考手册》是一份专为开发人员设计的权威指南,由Microsoft Azure Essentials提供。该手册汇集了来自行业专家的上百种资源,包括书籍、电子书和在线教程,旨在帮助开发者深入了解和利用Azure Web App进行高效开发。 手册覆盖的内容广泛,包括但不限于Azure Web App的基础架构、部署流程、性能优化、安全性、以及最新的技术趋势和最佳实践。无论是对于初次接触Azure的开发者,还是希望提升在云平台上应用开发技能的专业人士,这本指南都提供了详尽的指导和支持。 特别值得注意的是,手册提供的资源形式多样,支持电脑、平板、移动设备或电子阅读器等多种阅读方式,方便开发者根据自己的需求和习惯选择最适合的形式。此外,还提供了免费的美国境内配送服务,以及定期的优惠活动,如 Deal of the Week,让读者能以优惠价格获取特色图书。 订阅Microsoft Press Store的新闻通讯,用户可以第一时间了解到新书发布、特价促销和实用技巧等信息。此外,通过Microsoft Press Guided Tours应用程序,开发者还能体验作者对微软新技术的深度讲解,通过互动式游览,更好地理解和掌握技术细节。 《Azure Web App开发者参考手册》不仅是开发者提升技能的工具书,也是一个持续学习和分享的平台,旨在推动开发者社区的成长和发展。无论你是想入门Azure Web App开发,还是寻求技术进阶,这本书都是不可或缺的参考资料。立即访问Microsoft Press Store获取更多资讯和资源,开启你的Azure Web App开发之旅。"
资源详情
资源推荐
![](https://csdnimg.cn/release/download_crawler_static/10484275/bg10.jpg)
12
Chapter 1
Microsoft Azure Web Apps
Azure App Service Web Apps (formerly Azure Websites) is a platform-as-a-service (PaaS) offering that
enables developers to build secure, mission-critical, and highly scalable web applications. Developers
can choose from languages such as C#, HTML5, PHP, Java, Node.js, and Python to write their code and
use familiar tools such as Visual Studio and platform-specific Azure SDKs to get started quickly.
This chapter will introduce you to essential knowledge to get started building Azure web apps. This
text will present topics with the ASP.NET developer in mind and, therefore, will use C# for code
samples and Visual Studio 2013 with the Azure SDK for .NET installed.
This book focuses exclusively on Azure Web Apps, not on essential aspects of the Microsoft Azure
platform or the Azure portal. Therefore, it is recommended that the reader have some knowledge of
the Microsoft Azure platform. An excellent resource to gain this knowledge is
which you can download for free from
http://blogs.msdn.com/b/microsoft_press/archive/2015/02/03/free-ebook-microsoft-azure-essentials-
fundamentals-of-azure.aspx.
Introduction to Azure Resource Groups
When you create any resource in Azure, you will associate that resource with a new or existing resource
group. Therefore, before creating a resource such as an Azure web app, it is important to understand
Azure Resource Groups.
An Azure Resource Group is a logical container for grouping Azure resources. As an example,
consider a typical website implementation that has a web front end with which users interact and a
database in which to store data. The web front end and the database are individual resources that
comprise the full website solution. An Azure Resource Group gives you a natural way to manage and
monitor resources that comprise a solution. Figure 1-1 is an example of what an Azure Resource Group
could look like for a web application consisting of an Azure web app, Redis Cache, SQL database,
DocumentDB, and an Azure Storage account.
![](https://csdnimg.cn/release/download_crawler_static/10484275/bg11.jpg)
13
FIGURE 1-1 A hypothetical representation of an Azure Resource Group.
Grouping resources this way helps simplify the implementation, deployment, management, and
monitoring of resources in the resource group. From a billing perspective, it gives you a way to view
costs for the resource group rather than for individual resources, eliminating the need to figure out
which resources are related. You can think of an Azure Resource Group as a unit of management.
The resources in a resource group can span regions if needed. For example, you may have a web
app that is deployed in two or more regions for high availability in the unlikely event that an entire
datacenter were to go down where your app is deployed. In this scenario, each web app could be part
of the same resource group.
A single resource may exist in only one resource group. But it is possible for resources from different
resource groups to be linked. These are referred to as resources in the Azure portal. An example
of this could be a SQL database that is shared between web apps in different resource groups. Assume
you have a SQL database named “sqldb1” that is a resource in a resource group named “resgrp1.”
Now, assume you have a second resource group named “resgrp2” with a web app resource that will
use “sqldb1.” In this example, “sqldb1” will appear as a linked resource in “resgrp2.”
Introduction to App Service Plans
An App Service Plan provides a way for you to define the region and pricing tier (capacity and features)
that can be shared across the app service types, which are Web Apps, Mobile Apps, Logic Apps, and
API Apps. There are five pricing tiers available for Azure App Services:
Free The Free tier is intended for evaluation purposes; this is why it is free. Web apps in this
tier share machine resources with other web apps from other Azure subscribers. Because the
resources are shared, you have limited daily compute and network bandwidth limits.
Shared The Shared tier also shares machine resources with other web apps, but the daily
compute and network bandwidth limits are increased. This tier is intended for low-traffic sites
and enables support for a few features, such as custom domains and the ability to scale out to
![](https://csdnimg.cn/release/download_crawler_static/10484275/bg12.jpg)
14
multiple shared instances.
Basic The Basic tier gives you dedicated machine instances to host your web app and,
therefore, has no daily resource limits. In this tier, you are able to scale up the size of your
dedicated virtual machine to increase the number of cores and RAM. This tier enables
additional Azure Web App features and also is backed by a service level agreement (SLA).
Standard The Standard tier has all the features of the Basic tier, and it enables all features
available to Azure Web Apps. Features such as autoscale, deployment slots, automated backups,
support for Microsoft Azure Traffic Manager, and more are enabled in this tier.
Premium The Premium tier (in preview) provides the same set of features as the Standard tier
but with some extra capacity for features such as the number of deployment slots, storage, and
backups. It also enables BizTalk integration capabilities.
For details on the capacity, features, and costs associated with each pricing tier, see
http://azure.microsoft.com/en-us/pricing/details/app-service/.
An Azure web app may exist in a single App Service Plan at any given time. Or when needed, a web
app may be moved to another App Service Plan. This gives you the flexibility of starting your web app
development in an App Service Plan configured for the Free tier and then upgrading to an App Service
Plan configured for a higher pricing tier as your application and development requirements expand.
An App Service Plan can be used for multiple Web Apps, Mobile Apps, Logic Apps, and API Apps.
For example, you may have a plan that you use for development and testing your web apps that is
configured with less capacity and fewer features. Or you may have a plan that you use for a common
set of customer web apps in a specific region.
At any time, you can change the pricing tier for your App Service Plan. So it is not necessary to
create a new one if you need to move to a higher or lower pricing tier.
Important Changing the pricing tier for an App Service Plan will change the tier for all web apps in
the plan. For example, if you have five web apps running in a plan configured for the Basic tier and
later change the pricing tier to Standard, then all five web apps will be upgraded to run on Standard
Virtual Machines instead of Basic Virtual Machines.
An App Service Plan is a component of Azure Resource Groups, discussed in the previous section. At
first, this may not seem intuitive, but if you think of an Azure web app as a resource in a resource
group and an App Service Plan as a way to define the features and capacity available to your web app,
then the relationship between the two is easier to comprehend. For more information on the
relationship between Azure Resource Groups and App Service Plans, see
http://azure.microsoft.com/en-us/documentation/articles/azure-web-sites-web-hosting-plans-in-
depth-overview/.
![](https://csdnimg.cn/release/download_crawler_static/10484275/bg13.jpg)
15
Create an Azure Web App using the Azure portal
The Azure portal at https://portal.azure.com provides a rich user interface to provision and manage
resources in your Azure subscription. In this section, you will create an Azure web app with a SQL
database and then add an Azure Redis Cache to the resource group. After completing the steps, you
will have an Azure web app to which you can publish a web application. Publishing a web
application such as an ASP.NET MVC application is covered later in this chapter.
Create a Web App and SQL Database
After signing in to the Azure portal, click the +NEW button in the lower-left corner of the page. In the
Create blade, select the Web + Mobile option. In the Web + Mobile blade, you will see options for
creating various resources in Azure App Service, such as Web Apps, Mobile Apps, Logic Apps, and API
Apps.
Note If your goal is to create just an Azure web app, then you could select the option for Web Apps
where you would have the opportunity to specify an Azure Resource Group and App Service Plan for
the web app.
At the bottom of the Web + Mobile blade, click Azure Marketplace. In the Azure Marketplace,
additional options are available for creating common Azure Web App environments, such as a web
app with a SQL database or a web app with a MySQL database, as shown in Figure 1-2.
FIGURE 1-2 Web App solutions in the Azure Marketplace.
Tip There are many options for Web Apps you can choose from in the Azure Marketplace that
provide solutions for popular configurations such as blogging sites, frameworks, ASP.NET Starter apps,
and more. The full selection of solutions can be found in the Web Applications section of the
Marketplace at http://azure.microsoft.com/en-us/marketplace/web-applications/. To create a web app
using one of the solutions, click the solution. You will be redirected back to the Azure portal where
you can configure the solution settings for your needs.
Select the Web App + SQL option, which will open a blade describing the resources that this
solution will create and also provides links to relevant resources. Next, click the Create button at the
bottom of the blade to begin configuring the web app and SQL database.
![](https://csdnimg.cn/release/download_crawler_static/10484275/bg14.jpg)
16
In the Web App + SQL blade, the first thing you must do is specify the Azure Resource Group name
to create a new resource group. After entering a resource group name, select the Web App (Configure
Required Settings) option to open the Web App blade.
Configure required Web App settings
In the Web App blade, you must specify a globally unique URL for the web app. All web apps are
created in the *.azurewebsites.net domain and, therefore, must be unique to this domain. Later, you
can configure a custom domain you own to map to this URL. For information on configuring custom
domains, see http://azure.microsoft.com/en-us/documentation/articles/web-sites-custom-domain-
name/.
Next, you need to specify an App Service Plan. You can choose an existing plan or create a new one.
To create a new App Service Plan, enter a name in the text box. Creating a new App Service Plan will
unlock the Pricing Tier and Location options in the Web App blade so you can configure those settings.
Click the Pricing Tier option and change it to D1 Shared. If you don’t see the D1 Shared option, then
click the View All link in the upper-right corner to show all the pricing tiers.
Click the Location option and select a region close to you.
Tip You can use http://azurespeedtest.azurewebsites.net/ to find the lowest latency region for your
client. The Web App + SQL and Web App blades will look similar to Figure 1-3.
FIGURE 1-3 Web App + SQL blade and Web App blade.
剩余125页未读,继续阅读
![zip](https://img-home.csdnimg.cn/images/20210720083736.png)
![docx](https://img-home.csdnimg.cn/images/20210720083331.png)
![](https://csdnimg.cn/download_wenku/file_type_ask_c1.png)
![](https://csdnimg.cn/download_wenku/file_type_ask_c1.png)
![](https://csdnimg.cn/download_wenku/file_type_ask_c1.png)
![](https://csdnimg.cn/download_wenku/file_type_ask_c1.png)
![](https://csdnimg.cn/download_wenku/file_type_ask_c1.png)
![](https://csdnimg.cn/download_wenku/file_type_ask_c1.png)
![](https://csdnimg.cn/download_wenku/file_type_ask_c1.png)
![](https://csdnimg.cn/download_wenku/file_type_ask_c1.png)
![](https://csdnimg.cn/download_wenku/file_type_ask_c1.png)
![](https://csdnimg.cn/download_wenku/file_type_ask_c1.png)
![](https://csdnimg.cn/download_wenku/file_type_ask_c1.png)
![](https://csdnimg.cn/download_wenku/file_type_ask_c1.png)
![](https://csdnimg.cn/download_wenku/file_type_ask_c1.png)
![](https://csdnimg.cn/download_wenku/file_type_ask_c1.png)
![](https://csdnimg.cn/download_wenku/file_type_ask_c1.png)
![](https://csdnimg.cn/download_wenku/file_type_ask_c1.png)
![](https://csdnimg.cn/download_wenku/file_type_ask_c1.png)
![](https://profile-avatar.csdnimg.cn/0e53e5cfdd854d8ebc8ba77df7aa604e_weixin_38382105.jpg!1)
IAMITPRO
- 粉丝: 43
- 资源: 7
上传资源 快速赚钱
我的内容管理 展开
我的资源 快来上传第一个资源
我的收益
登录查看自己的收益我的积分 登录查看自己的积分
我的C币 登录后查看C币余额
我的收藏
我的下载
下载帮助
![](https://csdnimg.cn/release/wenkucmsfe/public/img/voice.245cc511.png)
最新资源
- Vue实现iOS原生Picker组件:详细解析与实现思路
- Arduino蓝牙小车:参数调试与功能控制
- 百度Java面试精华:200页精选资源涵盖核心知识点
- Swift使用CoreData填坑指南:CoreData在Swift 3.0的变化
- 微距离无线充电器创新设计及其实验探索
- MTK Android平台开发全攻略:44步详解流程
- RecyclerView全面解析:替代ListView的新选择
- Android开发:自动适配中英文键盘解决方案
- Android调用WebService接口教程
- Android开发:BitmapUtil图片处理全解析与实例
- Android多线程断点续传实现详解
- PCA算法在人脸识别会议签到系统中的应用
- EventBus 3.0:Android事件总线详解与实战应用
- Android FileUtil:全面解析文件操作实用技巧与实例
- RecyclerView添加头部和尾部实战教程
- Android实现微博滑动固定顶部栏实战与优化
资源上传下载、课程学习等过程中有任何疑问或建议,欢迎提出宝贵意见哦~我们会及时处理!
点击此处反馈
![](https://img-home.csdnimg.cn/images/20220527035711.png)
![](https://img-home.csdnimg.cn/images/20220527035711.png)
![](https://img-home.csdnimg.cn/images/20220527035111.png)
安全验证
文档复制为VIP权益,开通VIP直接复制
![](https://csdnimg.cn/release/wenkucmsfe/public/img/green-success.6a4acb44.png)