![]() On phones, in addition to Xamarin, there was the Windows Phone 8.1 and Silverlight Phone platforms. Windows also had the Windows 8/8.1 platform and the Universal Windows Platform (UWP). I’ve only discussed two platforms so far, the. NET platforms have many similar types, they’re fundamentally different, so you can’t guarantee a type will exist on both platforms, or that it will expose the same methods and properties. NET types you use in your apps on a daily basis: the int and string types, the file-reading APIs, the Task APIs, and so on. In the middle of each stack you have the Base Class Libraries (BCLs). NET Framework, but not using the Xamarin platform, and vice versa for an iOS app. For example, you could build a Windows Forms app on the. At the top of each stack, you have the app-specific libraries that you use to build applications for your platform. NET applications, such as the compiler and the common language runtime (CLR). Each layer builds on the capabilities of the layer below, with the highest layer providing the app models that you’ll use to build your applications.Īt the bottom of each stack is the tooling that allows you to compile and run. Each platform contained libraries and app models specific to their platform, but they used similar fundamental libraries and types, as shown in figure 1. Historically, these two platforms were completely separate, but they consisted of many similar components and implemented similar APIs. NET Framework that you can use to build mobile applications on Windows, Android, and iOS. If you’re a mobile developer, you might also be familiar with the Xamarin framework, which uses the cross-platform Mono implementation of the. It’s installed by default on Windows and was historically used for most desktop and server. NET Framework, version 4.8.1 at the time of writing, is a Windows-only development platform that you can use for both desktop and web development. NET developer, chances are you’re already familiar with the. Finally, in the next post, I’ll discuss what. In the next post I’ll describe how this was achieved in pre-.NET Core days, using Portable Class Libraries (PCLs) and the successor approach using. NET Core wasn’t developed in isolation, and one of its primary design goals was to improve the ability to share code between multiple frameworks. As part of this, I’ll discuss the similarities and differences between. ![]() ![]() NET ecosystem, how it has evolved, and the issues Microsoft were attempting to solve. In this post I’ll discuss the history of the. NET often find confusing, as well as provide some context for the changes. NET, and even to seasoned veterans! In this post, I’ll try to straighten out some of the terms that developers new to. Unfortunately, it can be confusing for developers new to. This churn isn’t surprising given Microsoft’s newfound transparency regarding the development process and building in the open on GitHub. NET 5+ has resulted in a particularly large degree of churn and the introduction of many new concepts. NET was first introduced, but the development of. On top of that, you'll also get ebook copies of the first and second editions, free! Rather than throw it away, I've turned it into a couple of posts here!Īlthough this post didn't make it into the book, if you like what you see, take a look at ASP.NET Core in Action-for now you can even get a 35% discount by entering the code au35loc into the discount code box at checkout at. There's a lot of new content in this edition, so we chose to remove one of the appendices from the book, trying to make sense of the. I've been working hard on the latest edition of my book, ASP.NET Core in Action, Third Edition, working through the final review process.
0 Comments
Leave a Reply. |