.NET Core基础教程：跨平台开发新篇章

需积分: 5 161 浏览量更新于2024-07-20 1 收藏 2.17MB PDF 举报

".NET Core Succinctly" 是一本由Giancarlo Lelli编写的书籍，主要关注.NET Core这一开源、跨平台的开发框架。这本书旨在引导读者理解.NET Core的基础知识，包括如何利用它进行跨平台开发，并在云环境中优化应用程序。书中的内容涵盖了以下关键知识点： 1. **开源策略与.NET Core**：解释了.NET Core作为开源项目的战略意义，以及它如何促进跨平台开发和向后兼容性。 2. **动手实践.NET Core**：这部分内容可能涉及通过实际操作介绍.NET Core的基本用法，帮助读者熟悉环境和工具。 3. **贡献.NET Core仓库**：讨论如何参与.NET Core的开发，对开源项目作出贡献，包括代码提交、问题跟踪和社区互动。 4. **使用Visual Studio构建.NET Core应用**：详细介绍了如何使用Visual Studio这一强大的开发工具来创建.NET Core应用程序，包括项目设置、调试和测试。 5. **.NET Core的主要工作负载**：讨论了.NET Core支持的不同类型的应用程序，如Web应用、API服务等，以及如何针对这些工作负载进行开发。 6. **在Linux上构建.NET Core应用**：展示了如何在非Windows操作系统上（如Linux）搭建和运行.NET Core应用，强调了其跨平台的特性。 7. **向.NET Core迁移**：提供了将现有应用程序迁移到.NET Core的指南，可能包括兼容性问题和迁移策略。 8. **.NET Core 1.0的更新**：这部分可能涵盖了自书籍出版以来.NET Core的重大更新，特别是1.0版本的发布及其新特性。 9. **参与.NET Core的开源项目**：鼓励读者如何参与到.NET Core的开源社区，分享知识，解决问题，以及如何通过GitHub等平台进行协作。这本书不仅提供了一个深入理解.NET Core的起点，还强调了其在现代应用程序开发中的作用，以及如何利用它来构建云优化的解决方案。对于想要学习或已经在使用.NET Core的开发者来说，是一份宝贵的资源。通过阅读本书，读者可以掌握如何有效地利用.NET Core进行跨平台开发，同时了解如何为.NET Core的持续发展做出贡献。

Preface

Before digging deeper into the contents of this e-book, I believe that we should first analyze why

a book like this was considered useful and needed at this point in time. At first, this might sound

like a pretentious goal, but during the course of this e-book, and for the most part in this

introductory chapter, we will understand that at the end of the day it was quite clear and

somehow obvious.

I believe that the purpose of technology is to help individuals achieve their goals, whether they

use it consciously or not. My job, and probably yours, since you’re reading this, is about

leveraging technology to build stuff that at the end of the day will empower someone. We are

witnesses of this momentum on a daily basis with the unstoppable growth of mobile

technologies, platforms, and devices. Devices are announced and their computational power

increases every year (if not every six months) and we, first as consumers and then as

developers, are faced with the never-ending challenge of choosing what to build, how to build it,

and for whom. I believe that the most sensitive aspect of this is that any of those three choices

inevitably comes with a price…and many times we pay with our most precious currency, time.

Since time is a finite resource and there’s no way to earn time, we must be sure not to waste it.

Rephrasing this is a more technological way, we must value our previous investments in the

best way we can.

However, until recent days, this hasn’t been an easy task. Let’s analyze what used to happen,

and what we as Microsoft developers were used to facing. Twelve years since the release of the

first .NET framework, we were used to having fragmented versions of .NET for different

platforms. From the .NET Compact Framework to Silverlight, Windows Phone, and Windows

Store applications, every time Microsoft has taken .NET to a new platform, the supposedly

“common” language runtime has ended up with a different subset. Each time, there’s a different

runtime, framework, and application model, with different development being done at each layer

and APIs that go back to a common code base but haven’t always stayed common. Back in

those days, Microsoft tried endlessly to reassure us, talking about common skill and reusing

what we already knew, but the reality was one: fragmentation (and many headaches).

Microsoft tried to tackle this problem by introducing Portable Class Libraries, Shared Projects,

and finally, Universal Apps. The core concept of the first two approaches was the idea of

contract, or in other words, a way of abstracting the APIs so you can use them as if they were

the same for each platform. These approaches ended up becoming standard de-facto in

modern application developments, and once Xamarin came up, it allowed us to take this even

further by letting us reuse our code on other platforms like iOS, Android, and Mac OS X. That

was a sort of glimpse into a cross-platform .NET. Unfortunately, in each case, the

implementation of those APIs was different. At this point you might think that the solution to our

dilemma was close, but unfortunately it was not…or at least not a complete one. Portable Class

Libraries managed to get platforms closer, but were just not capable of making the .NET

Framework more modular.

剩余51页未读，继续阅读

DWcsdnNET

粉丝: 415
资源: 651

.NET Core基础教程：跨平台开发新篇章

ASP.NET Core Succinctly

c# with open

python中paramiko插件

fastcache-1.1.0-cp38-cp38-win_amd64.whl

【图像检索】基于matlab颜色特征图像检索（含直方图距离）【含Matlab源码 4145期】.md

【图像加密】基于matlab混沌结合小波变换图像加密【含Matlab源码 3223期】.md

基于Java的学生管理系统的实现与代码解析

xxhash-1.4.4-cp36-cp36m-win_amd64.whl

crontablllllll

dubins-1.0.1-cp36-cp36m-win_amd64.whl

最新资源