火焰紋章16進制是怎么算

Back in September, Microsoft released .NET Core 3 to much (deserved) fanfare. Included in it was a new web UI framework called Blazor. Then in May, Microsoft released Blazor 3.2, and with that released Blazor WebAssembly as a production-ready version of Blazor.

早在9月，微軟就發(fā)布了.NET Core 3 ，這是當之無愧的。 其中包括一個名為Blazor的新Web UI框架。 然后在5月，Microsoft發(fā)布了Blazor 3.2，并隨同發(fā)布了Blazor WebAssembly，將其作為Blazor的生產(chǎn)就緒版本。

Blazor is a weird thing. First, because it’s two things. Second, because of what one of those things promises: a JavaScript-less future for the web.

開拓者是一件奇怪的事。 首先，因為這是兩件事。 其次，由于其中之一的承諾：Web的無JavaScript未來。

Let’s step back and parse this out.

讓我們退后一步，解析一下。

.NET Core和.NET的未來 (.NET Core and the Future of .NET)

.NET Core 3.0 was a pretty major release. .NET has been undergoing many changes over the last 5 years or so, and .NET Core feels like the culmination of a lot of effort to streamline the entire ecosystem. .NET Core is the future of .NET, as evidenced by its name change to .NET 5 later this year.

.NET Core 3.0是一個非常重要的版本。 .NET在過去五年左右的時間里經(jīng)歷了許多變化，而.NET Core感覺就像是精簡整個生態(tài)系統(tǒng)的大量努力的最終結果。 .NET Core是.NET的未來，今年晚些時候更名為.NET 5便證明了這一點。

The main advantage that .NET Core has over the older .NET Framework is platform support. .NET Core is cross platform, and can run just about everywhere, whereas .NET Framework is tied to Windows. It’s also very stable, very fast, and comes with first-class tooling for developers.

.NET Core與舊版.NET Framework相比的主要優(yōu)點是平臺支持。 .NET Core是跨平臺的，幾乎可以在任何地方運行，而.NET Framework與Windows綁定。 它也非常穩(wěn)定，非常快，并為開發(fā)人員提供了一流的工具。

Web組裝 (WebAssembly)

Unrelated to .NET, WebAssembly has slowly become a thing. In short, WebAssembly is a new, assembly-like language for the web. It runs in the browser but at near-native speeds. It’s also highly optimized so it can run fast and is supported in all modern browsers.

與.NET無關， WebAssembly逐漸成為一件事。 簡而言之，WebAssembly是一種新的類似于Web的程序集語言。 它在瀏覽器中運行，但速度接近自然。 它還經(jīng)過高度優(yōu)化，因此可以快速運行，并且在所有現(xiàn)代瀏覽器中都受支持。

Importantly, WebAssembly is not a language that the vast majority of developers will ever write. Instead, WebAssembly is meant to be used as a compilation target. Instead of compiling code for a specific processor or operating system, you can compile code to WebAssembly and have your program run in a browser.

重要的是，WebAssembly不是絕大多數(shù)開發(fā)人員都會編寫的語言。 而是將WebAssembly用作編譯目標。 您可以將代碼編譯為WebAssembly，并使程序在瀏覽器中運行，而不必為特定處理器或操作系統(tǒng)編譯代碼。

開拓者 (Blazor)

Blazor is a new UI framework that was included in .NET Core 3. Conceptually, Blazor is more like Angular or React rather than ASP.NET MVC. It’s a component-based framework for building rich and interactive web applications. The main difference between Blazor and traditional JavaScript frameworks is that Blazor components are written entirely in C# and Razor. No JavaScript required!

Blazor是.NET Core 3中包含的新UI框架。從概念上講，Blazor更像是Angular或React，而不是ASP.NET MVC。 這是一個基于組件的框架，用于構建豐富的交互式Web應用程序。 Blazor與傳統(tǒng)JavaScript框架之間的主要區(qū)別是Blazor組件完全用C＃和Razor編寫。 無需JavaScript！

開拓者的兩面 (The Two Sides of Blazor)

Blazor has two models: Server and WebAssembly. The server model was shipped with .NET Core 3. At that time, WebAssembly was still in preview, but has now been fully released with Blazor 3.2. Both are now production ready.

Blazor有兩種模型：Server和WebAssembly。 服務器模型隨.NET Core 3一起提供。當時，WebAssembly仍處于預覽狀態(tài)，但現(xiàn)在已隨Blazor 3.2一起完全發(fā)布。 兩者都已經(jīng)準備好生產(chǎn)。

Both models use the same component-oriented architecture, but are vastly different in how they run those components. The Server model runs, well, on a server. The code sent to the browser isn’t your code, but rather a small part of the framework which uses SignalR (a .NET library for managing real-time connections between a client and server) to send events from the browser to the server and DOM diffs back to the browser. The server renders your components and manages the interactions through SignalR.

兩種模型都使用相同的面向組件的體系結構，但是在運行這些組件的方式上卻有很大的不同。 服務器模型可以很好地在服務器上運行。 發(fā)送到瀏覽器的代碼不是您的代碼，而是框架的一小部分，該框架使用SignalR(用于管理客戶端和服務器之間的實時連接的.NET庫)將事件從瀏覽器發(fā)送到服務器，并DOM擴散回瀏覽器。 服務器呈現(xiàn)您的組件并通過SignalR管理交互。

The WebAssembly model is actually a bit easier to understand. All of the code, the framework and your components, run in the browser. Your C# code is compiled into DLLs like any other .NET application, but is then sent to the browser. Mono (a .NET runtime originally for Linux and the runtime behind Xamarin apps) is what is actually compiled to WebAssembly and it what runs your code in the browser. It’s very strange to open the browser dev tools and watch it downloading a bunch of DLLs.

實際上，WebAssembly模型更容易理解。 所有代碼，框架和組件都在瀏覽器中運行。 您的C＃代碼像其他任何.NET應用程序一樣被編譯為DLL，但隨后被發(fā)送到瀏覽器。 Mono(最初用于Linux的.NET運行時，以及Xamarin應用程序背后的運行時)實際上是編譯為WebAssembly的內(nèi)容，它是在瀏覽器中運行代碼的內(nèi)容。 打開瀏覽器開發(fā)工具并觀看它下載大量DLL是很奇怪的。

Both models have their advantages. Server requires less work in the browser, but there is some latency in the UI since the network is involved. WebAssembly runs quicker, but requires a hefty initial download (about 2MB from the starter project).

兩種模式都有其優(yōu)勢。 服務器在瀏覽器中的工作量較少，但由于涉及網(wǎng)絡，因此UI中存在一些延遲。 WebAssembly的運行速度更快，但需要大量的初始下載(從入門項目中下載大約2MB)。

Blazor —快速樣本 (Blazor — A Quick Sample)

Creating a new Blazor project is easy. There are project templates available in the latest versions of Visual Studio (Windows and Mac), or you can create one using the .NET CLI: `dotnet new blazorwasm -o ProjectName`. Once the CLI finishes creating the project, navigate into the new folder and use `dotnet run` to launch it.

創(chuàng)建一個新的Blazor項目很容易。 在最新版本的Visual Studio(Windows和Mac)中，有可用的項目模板，或者您可以使用.NET CLI創(chuàng)建一個模板：“ dotnet new blazorwasm -o ProjectName”。 CLI完成創(chuàng)建項目后，導航到新文件夾并使用`dotnet run`啟動它。

The sample components and layouts are a great way to get familiar with how you can build apps with Blazor.

示例組件和布局是熟悉如何使用Blazor構建應用程序的好方法。

> Side note: I don’t actually like the “standard” way of mixing C# and Razor together using the `@code` block. Instead, I prefer to make a separate C# file for the logic and leave the view code in the Razor file. This can be done easily as the generated classes from the components are partial classes and can be extended. More info here.

>注意：我實際上并不喜歡使用“ @code”塊將C＃和Razor混合在一起的“標準”方式。 相反，我更愿意為邏輯創(chuàng)建一個單獨的C＃文件，并將視圖代碼保留在Razor文件中。 這很容易完成，因為從組件生成的類是局部類并且可以擴展。 更多信息在這里。

Blazor includes all you need to create full-featured, interactive web apps. Routing, form validation, and HTTP access are all available and are shown in the basic project template. And since it’s all in C#, .NET developers can get up and running quickly and can even reuse code from other parts of their systems. Blazor supports data annotation validation on forms, so business logic around model validation can be reused.

Blazor包括創(chuàng)建功能齊全的交互式Web應用程序所需的全部。 路由，表單驗證和HTTP訪問均可用，并顯示在基本項目模板中。 而且，由于.NET開發(fā)人員全部使用C＃，因此它們可以快速啟動并運行，甚至可以重用系統(tǒng)其他部分的代碼。 Blazor支持在表單上進行數(shù)據(jù)注釋驗證，因此可以重用圍繞模型驗證的業(yè)務邏輯。

>Be aware that WebAssembly is still subject to the same browser sandbox that normal JavaScript-based web apps are forced to use.

>請注意，WebAssembly仍受制于通常使用基于JavaScript的Web應用程序所在的瀏覽器沙箱。

Blazor WebAssembly —我想要的未來 (Blazor WebAssembly — The Future I Want)

My controversial opinion about Blazor is that the Server model should not exist. I think the WebAssembly model is superior and is the future I want to see on the web. I get why Microsoft created the Server model: it could be ready faster, and they want to show that the components you create are relatively independent of how they are being run. But it muddies the waters around Blazor when the WebAssembly model is more forward-facing and just as capable.

我對Blazor有爭議的觀點是服務器模型不應該存在。 我認為WebAssembly模型是優(yōu)越的，并且是我希望在網(wǎng)絡上看到的未來。 我明白了Microsoft創(chuàng)建服務器模型的原因：它可以更快地準備就緒，他們想證明您創(chuàng)建的組件相對獨立于其運行方式。 但是，當WebAssembly模型更具前向性且功能強大時，它會使Blazor周圍的水變得更加混亂。

One advantage of the WebAssembly model is that it’s independent of where or how it is hosted. When you publish a WebAssembly project, you get a folder full of files. A Blazor WebAssembly project is a static site and can be hosted anywhere. You don’t need to host it in Azure, or even run ASP.NET Core. And Blazor WebAssembly apps can be created as Progressive Web Apps to enable offline support since they don’t require a persistent network connection.

WebAssembly模型的優(yōu)點之一是，它獨立于托管位置或托管方式。 發(fā)布WebAssembly項目時，將獲得一個充滿文件的文件夾。 Blazor WebAssembly項目是一個靜態(tài)站點，可以在任何地方托管。 您無需將其托管在Azure中，甚至無需運行ASP.NET Core。 并且Blazor WebAssembly應用程序可以創(chuàng)建為Progressive Web Apps，以啟用脫機支持，因為它們不需要持久的網(wǎng)絡連接。

WebAssembly opens the door to a future where interaction on the web doesn’t rely exclusively on JavaScript, and Blazor proves that a framework can be created that takes full advantage of that. I’m excited to use Blazor for more projects, and I think it’s worth your time to check it out.

WebAssembly開啟了未來之門，網(wǎng)絡上的交互不僅僅依賴JavaScript，Blazor證明可以創(chuàng)建一個充分利用JavaScript的框架。 我很高興能將Blazor用于更多項目，并且我認為值得您抽出寶貴時間來進行檢查。

• Andrew Moscardino, Software Developer at AWH
  AWH的軟件開發(fā)人員Andrew Moscardino

Citations

引文

Manager, Daniel RothPrincipal Program, et al. “ASP.NET Core Updates in .NET Core 3.0 Preview 2.” ASP.NET Blog, 18 Nov. 2019, devblogs.microsoft.com/aspnet/aspnet-core-3-preview-2/.

Daniel Roth首席項目經(jīng)理等。 “ .NET Core 3.0預覽版2中的ASP.NET Core更新。” ASP.NET博客，2019年11月18日，devblogs.microsoft.com / aspnet / aspnet-core-3-preview-2 /。

翻譯自: https://medium.com/swlh/blazor-is-worth-your-time-8cd77bbb95cd

火焰紋章16進制是怎么算

總結

以上是生活随笔為你收集整理的火焰纹章16进制是怎么算_火焰是值得你的时间的全部內(nèi)容，希望文章能夠幫你解決所遇到的問題。

如果覺得生活随笔網(wǎng)站內(nèi)容還不錯，歡迎將生活随笔推薦給好友。