ASP.NET Core 3.0 开发指南：从A到Z

需积分: 9 78 浏览量更新于2024-07-16 收藏 12.18MB PDF 举报

"ASP.Net Core3.0-AZ-EBook.pdf" 是一本关于ASP.NET Core 3.0 Web应用程序开发的详尽指南，涵盖了26个关键主题。作者通过一系列深入的博客文章，对每个主题进行了全面的探讨，包括示例、边缘情况和相关参考，旨在提供当前互联网上关于ASP.NET Core的最优质信息。本书的创作过程充满热情和深思熟虑，作者在2018年完成前一个大型博客系列后，就开始策划这个A到Z的ASP.NET Core系列。他精心安排每周的主题，甚至与重大会议如Build 2019同步，确保内容的新颖和时效性。每周发布的不仅是一篇关于计划主题的博客文章，更是一个深入的研究，包括详细的实例、边缘情况分析以及相关引用。作为ASP.NET社区站台的每周精选文章审查者，作者的系列帖子始终处于顶尖水平。这些帖子多次被选中在节目中分享，因为它们的质量和投入的努力得到了广泛认可。这本书的每一篇都如同作者之前写的书一样，充满了深度和实用性，是ASP.NET开发者不可或缺的参考资料。 ASP.NET Core 3.0是一个强大的框架，用于构建高性能、跨平台的Web应用程序。在这个系列中，读者可以期待学习到以下方面的知识： 1. **基础概念**：了解ASP.NET Core 3.0的基本架构，包括依赖注入、中间件、路由和HTTP上下文。 2. **开发环境**：设置Visual Studio或Visual Studio Code进行ASP.NET Core开发，理解项目结构和配置文件。 3. **MVC框架**：学习如何使用Model-View-Controller模式构建应用程序，包括控制器、视图和模型的创建与交互。 4. **Razor Pages**：探索Razor Pages这一更简洁的页面开发方式，了解其与MVC的区别和应用场景。 5. **数据库集成**：掌握Entity Framework Core，进行数据访问和实体关系映射。 6. **身份验证与授权**：学习如何实现用户认证和授权，使用Cookie认证、OAuth2.0等机制。 7. **API开发**：创建RESTful API，处理HTTP请求，实现JSON序列化和反序列化。 8. **测试与调试**：了解单元测试、集成测试以及调试ASP.NET Core应用的方法。 9. **部署与发布**：学习将应用程序部署到Azure、AWS或其他云平台，以及本地IIS的配置。 10. **性能优化**：了解如何提高应用程序性能，包括缓存策略、性能监控和代码优化。 11. **错误处理与日志记录**：设置异常处理和日志记录，确保应用程序的健壮性。 12. **持续集成与持续部署(CI/CD)**：实现自动化构建和部署流程，如使用Jenkins或GitHub Actions。 13. **Blazor**：如果涵盖，将介绍这个新颖的客户端Web开发框架，允许使用C#在浏览器中编写富交互式UI。通过这26个主题的深入学习，开发者不仅可以掌握ASP.NET Core 3.0的核心技术，还能了解到最佳实践和最新趋势，从而提升开发效率和应用质量。无论是初学者还是经验丰富的开发者，这本书都将为他们的技能树增添宝贵的分支。

GIF Source: https://wakeupandcode.com/wp-content/uploads/2019/01/blazor-dice.gif

Entry Point and Configuration

Let’s start with Program.cs, the entry point of your application. Just like any ASP .NET Core web

application, there is a Main method that sets up the entry point. A quick call to CreateHostBuilder() in

the same file ensures that two things will happen: The Blazor Web Assembly Host will call its own

CreateDefaultBuilder() method (similar to how it works in a typical ASP .NET Core web application) and

it will also call UseBlazorStartup() to identify the Startup class where the application is configured.

public class Program

{

public static void Main(string[] args)

{

CreateHostBuilder(args).Build().Run();

}

public static IWebAssemblyHostBuilder CreateHostBuilder(string[]

args) =>

BlazorWebAssemblyHost.CreateDefaultBuilder()

.UseBlazorStartup<Startup>();

}

Note that the Startup class doesn’t have to be called Startup, but you do have to tell your application

what it’s called. In the Startup.cs file, you will see the familiar ConfigureServices() and Configure()

methods, but you won’t need any of the regular MVC-related lines of code that set up the HTTP pipeline

for an MVC (or Razor Pages) application. Instead, you just need a minimum of 1 line of code that adds

the client side “App”. (This is different for server-hosted apps.)

public class Startup

{

public void ConfigureServices(IServiceCollection services)

{

}

public void Configure(IBlazorApplicationBuilder app)

{

app.AddComponent<App>("app");

}

Note that the Configure() method takes in an app object of type IBlazorApplicationBuilder, unlike the

usual IApplicationBuilder we see in regular ASP .NET Core web apps. When it adds the App component,

it specifies the client-side app with the name “app” in double quotes.

The HTML in the index page has two things worth noting: an <app> tag with some placeholder text,

followed by a <script> tag with a reference to the Blazor JavaScript code that allows you to run your

.NET code in the browser via WebAssembly.

Blazor’s page components can be used to create the UI and interaction, starting with one or more

@page directives that define the page routes, followed by HTML elements and C# code to interact with

those elements. Take, for example, the Index.cshtml file in the Pages folder:

@page "/"

<h1>Hello, Developers!</h1>

Get ready to roll the dice!

</NavLink>

In the above code for Index.cshtml, the @page directive indicates that this this is a Page (a type of

Blazor component) and the “/” single slash character indicates that this is the root page for your

application. A component can have multiple routes if desired.

The <NavLink> tag is a helper class that generates an <a> tag hyperlink for your browser. In this case,

the href attribute points to another route “dice” in the application, defined in Dice.cshtml (shown

below).

@page "/dice"

... HTML elements

@functions {

// client-side C# code

}

In the above code for Dice.cshtml, once again the @page directive defines a route “/dice” that defines

how you can arrive on this page. There are a couple of <button> elements that generate client-side

HTML buttons, yet can trigger C# code with onclick handlers. The rest of the file contains C# code

wrapped in a @functions{} block to be loaded in the browser.

The @ symbols in the onclick handlers allow you to call C# code from the HTML buttons, to reset the

dice and roll a new set of dice:

<button class="btn btn-primary" onclick="@ResetDice">Reset

Dice</button>

The <div> elements that follow contain placeholder images for six dice images, with src attributes

defined by a C# array of strings. The dice images are named dice1.png through dice6.png.

剩余312页未读，继续阅读

sinat_31853197

粉丝: 0
资源: 1

ASP.NET Core 3.0 开发指南：从A到Z

timing-jitter-tutorial-and-measurement-guide-ebook.pdf

Wrox.ASP.NET.2.0.Website.Programming.Problem.Design.Solution.May.2006.eBook-BBL.part2.rar

MATLAB-Control-Systems-Engineering-Cesar-Lopez(www.ebook-dl.com).pdf

给几个QT开源项目的链接

中文阅读图书网站有哪些

txt转epub工具下载

Spark SQL参考文献

在Linux环境下，如何使用命令行工具操作PDF文件？请提供常见的PDF处理命令。

ubuntu ebook

最新资源