ASP.NET学习资源：从入门到进阶的PDF教程

需积分: 20 3 浏览量更新于2024-07-18 收藏 29.19MB PDF 举报

"ASP.NET学习PDF提供了一系列关于ASP.NET技术的教程，涵盖了从入门到进阶的多个方面，包括创建Web应用、Web API、Razor Pages等，还涉及了数据访问与实体框架核心（EF Core）的使用，以及跨平台开发的教程。资源对初学者和有一定经验的开发者都有价值，通过阅读可以深入理解ASP.NET的核心概念和技术实践。" 本文将详细介绍ASP.NET的学习路径和关键知识点，帮助读者构建全面的ASP.NET知识体系。首先，"Get started"章节引导读者快速了解ASP.NET的基础知识，包括安装必要的开发环境和工具，如Visual Studio或Visual Studio Code，以及如何配置项目设置。这部分内容旨在让新手能够快速上手，搭建第一个ASP.NET Web应用程序。 "Create a web app"和"Create a Razor Pages web app"章节讲解了如何创建传统的MVC应用和使用Razor Pages的现代Web应用。Razor Pages是一种更简洁、更直观的方式来构建页面驱动的Web应用，特别适合处理简单的CRUD操作。这些章节会介绍如何定义路由，编写控制器和视图，以及如何使用C#和HTML混合语法的Razor模板。 "Create a Web API"章节则转向了服务端API的开发，包括在ASP.NET中创建RESTful API的方法，这在构建前后端分离的应用或者移动应用的后端时非常有用。这部分会介绍HTTP方法、路由、模型绑定以及如何返回JSON或XML数据。 "Data access with EF Core"部分涵盖了使用Entity Framework Core进行数据访问的教程。EF Core是微软的轻量级、高性能的对象关系映射框架，允许开发者以面向对象的方式操作数据库。这部分内容将讲解如何创建数据库上下文、定义实体、执行数据库查询、实现数据库迁移，以及如何在Web应用中集成EF Core。 "Cross-platform tutorials"章节针对跨平台开发，提供了在macOS、Linux或VS Code上开发ASP.NET应用的指导，这对于希望在非Windows环境下工作的开发者来说非常有价值。此外，"Middleware"章节讲解了ASP.NET Core中的中间件概念，这是处理HTTP请求和响应的关键组件。读者将学习如何编写自定义中间件，以及如何使用工厂模式来管理中间件实例。 "Dependency injection (services)"章节介绍了依赖注入，这是ASP.NET Core中实现松耦合和可测试代码的重要机制。读者将学习如何注册和使用服务，以及如何实现依赖注入容器。 "Controller methods and views"和"Add search, add a new field, add validation"等章节则进一步深化了对MVC模式的理解，讲解了控制器的行为、视图的渲染，以及如何实现搜索功能、添加新字段和验证用户输入。 "Upload files"章节涵盖了文件上传的处理，这对于构建支持用户上传内容的Web应用是必不可少的。最后，"Build Web APIs"和"Create backend services for native mobile apps"章节探讨了如何为原生移动应用创建后端服务，使开发者能够构建出功能强大的跨平台解决方案。这份ASP.NET学习PDF提供了全面而深入的教程，覆盖了从基础到高级的ASP.NET开发各个方面，无论是初学者还是经验丰富的开发者都能从中受益。通过系统学习，读者可以掌握ASP.NET的核心技术和实践技巧，从而更好地构建高效、可靠的Web应用程序。

using System.Threading.Tasks;

using Microsoft.AspNetCore.Mvc;

using Microsoft.AspNetCore.Mvc.RazorPages;

using RazorPagesContacts.Data;

namespace RazorPagesContacts.Pages

{

public class CreateModel : PageModel

{

private readonly AppDbContext _db;

public CreateModel(AppDbContext db)

{

_db = db;

}

[BindProperty]

public Customer Customer { get; set; }

public async Task<IActionResult> OnPostAsync()

{

if (!ModelState.IsValid)

{

return Page();

}

_db.Customers.Add(Customer);

await _db.SaveChangesAsync();

return RedirectToPage("/Index");

}

public async Task<IActionResult> OnPostAsync()

{

if (!ModelState.IsValid)

{

return Page();

}

_db.Customers.Add(Customer);

await _db.SaveChangesAsync();

return RedirectToPage("/Index");

}

By convention, the PageModel class is called <PageName>Model and is in the same namespace as the page.

The PageModel class allows separation of the logic of a page from its presentation. It defines page handlers for

requests sent to the page and the data used to render the page. This separation allows you to manage page

dependencies through dependency injection and to unit test the pages.

The page has an OnPostAsync handler method, which runs on POST requests (when a user posts the form). You can

add handler methods for any HTTP verb. The most common handlers are:

OnGet to initialize state needed for the page. OnGet sample.

OnPost to handle form submissions.

The Async naming suffix is optional but is often used by convention for asynchronous functions. The OnPostAsync

code in the preceding example looks similar to what you would normally write in a controller. The preceding code is

typical for Razor Pages. Most of the MVC primitives like model binding, validation, and action results are shared.

The previous OnPostAsync method:

public class CreateModel : PageModel

{

private readonly AppDbContext _db;

public CreateModel(AppDbContext db)

{

_db = db;

}

[BindProperty]

public Customer Customer { get; set; }

public async Task<IActionResult> OnPostAsync()

{

if (!ModelState.IsValid)

{

return Page();

}

_db.Customers.Add(Customer);

await _db.SaveChangesAsync();

return RedirectToPage("/Index");

}

NOTENOTE

The basic flow of OnPostAsync :

Check for validation errors.

If there are no errors, save the data and redirect.

If there are errors, show the page again with validation messages. Client-side validation is identical to traditional

ASP.NET Core MVC applications. In many cases, validation errors would be detected on the client, and never

submitted to the server.

When the data is entered successfully, the OnPostAsync handler method calls the RedirectToPage helper method to

return an instance of RedirectToPageResult . RedirectToPage is a new action result, similar to RedirectToAction or

RedirectToRoute , but customized for pages. In the preceding sample, it redirects to the root Index page ( /Index ).

RedirectToPage is detailed in the URL generation for Pages section.

When the submitted form has validation errors (that are passed to the server), the OnPostAsync handler method

calls the Page helper method. Page returns an instance of PageResult . Returning Page is similar to how actions

in controllers return View . PageResult is the default return type for a handler method. A handler method that

returns void renders the page.

The Customer property uses [BindProperty] attribute to opt in to model binding.

Razor Pages, by default, bind properties only with non-GET verbs. Binding to properties can reduce the amount of

code you have to write. Binding reduces code by using the same property to render form fields (

<input asp-for="Customer.Name" /> ) and accept the input.

For security reasons, you must opt in to binding GET request data to page model properties. Verify user input before

mapping it to properties. Opting in to this behavior is useful when building features which rely on query string or route

values.

To bind a property on GET requests, set the [BindProperty] attribute's SupportsGet property to true :

[BindProperty(SupportsGet = true)]

剩余2015页未读，继续阅读

即将拥有人鱼线的Iverson

粉丝: 28
资源: 2

ASP.NET学习资源：从入门到进阶的PDF教程

从零学习ASP.NET

业界最强大的asp.net自学资料

ASPNET学习资料

ASP.Net.rar_.net网站_ASP·NET_asp. net pdf_asp.net_pdf asp.net

asp.net的pdf

asp.net 转换pdf

asp.net浏览pdf

asp.net导出pdf

asp.net中pdf拆分

asp.net 导出 pdf 文件

最新资源