Net tools

Done! These improvements are from the changes that we were able to get into the 1.0 product..NET developers know that the platform is a great choice for productivity. We want them to know that it’s also a great choice for performance..NET Core 1.0We’ve been talking about .NET Core for about two years now, although it has changed significantly over that time. It’s good to recap in this post what defines and is included in .NET Core 1.0..NET Core is a new cross-platform .NET product. The primary selling points of .NET Core are:Cross-platform: Runs on Windows, macOS and Linux.Flexible deployment: Can be included in your app or installed side-by-side user- or machine-wide.Command-line tools: All product scenarios can be exercised at the command-line.Compatible: .NET Core is compatible with .NET Framework, Xamarin and Mono, via the .NET Standard Library.Open source: The .NET Core platform is open source, using MIT and Apache 2 licenses. Documentation is licensed under CC-BY. .NET Core is a .NET Foundation project.Supported by Microsoft: .NET Core is supported by Microsoft, per .NET Core SupportComposition.NET Core is composed of the following parts:A .NET runtime, which provides a type system, assembly loading, a garbage collector, native interop and other basic services.A set of framework libraries, which provide primitive data types, app composition types and fundamental utilities.A set of SDK tools and language compilers that enable the base developer experience, available in the .NET Core SDK.The ‘dotnet’ app host, which is used to launch .NET Core apps. It selects and hosts the runtime, provides an assembly loading policy and launches the app. The same host is also used to launch SDK tools in the same way.DistributionsThere are two main distributions for .NET Core:.NET Core – Includes the .NET Core runtime and framework. The current version is “.NET Core 1.0”.NET Core SDK – Includes .NET Core and the .NET Core Tools. The current version is “.NET Core SDK 1.0 Preview 2”.The .NET Core Tools are considered “Preview” currently. We chose “Preview” because we are not yet done shaping the tools. We know that there are still some changes coming. It’s not a quality statement. We’re quite happy with the quality and use the .NET Core tools ever day as part of our engineering system.Most people will want to get the .NET Core SDK from dot.net/core. You can, however, check out our latest builds, where it’s easy to see the two different distributions.WorkloadsBy itself, .NET

Core includes a single application model — console apps — which is useful for tools, local services and text-based games. Additional application models have been built on top of .NET Core to extend its functionality, such as:ASP.NET CoreWindows 10 Universal Windows Platform (UWP)Xamarin.Forms.NET Core ToolsYou typically start .NET Core development by installing the .NET Core SDK. The SDK includes enough software to build an app. The SDK gives you both the .NET Core Tools and a copy of .NET Core. As new versions of .NET Core are made available, you can download and install them without needing to get a new version of the tools.Apps specify their dependence on a particular .NET Core version via the project.json project file. The tools help you acquire and use that .NET Core version. You can switch between multiple apps on your machine in Visual Studio, Visual Studio Code or at a command prompt and the .NET Core tools will always pick the right version of .NET Core to use within the context of each app.You can also have multiple versions of the .NET Core tools on your machine, too, which can be important for continuous integration and other scenarios. Most of the time, you will just have one copy of the tools, since doing so provides a simpler experience.The dotnet ToolYour .NET Core experience will start with the dotnet tool. It exposes a set of commands for common operations, including restoring packages, building your project and unit testing. It also includes a command to create an empty new project to make it easy to get started.The following is a partial list of the commands.dotnet new – Initializes a sample console C# project.dotnet restore – Restores the dependencies for a given application.dotnet build – Builds a .NET Core application.dotnet publish – Publishes a .NET portable or self-contained application.dotnet run – Runs the application from source.dotnet test – Runs tests using a test runner specified in the project.json.dotnet pack – Creates a NuGet package of your code.dotnet works great with C# projects. F# and VB support is coming..NET Standard LibraryThe .NET Standard Library is a formal specification of .NET APIs that are intended to be available on all .NET runtimes. The motivation behind the Standard Library is establishing greater uniformity in the .NET ecosystem. ECMA 335 continues to establish uniformity for .NET runtime behavior, but there is no similar spec for the .NET Base Class

42.3+Alpine: 3.7+Note: The runtime ID for Alpine was previously alpine-3.6. There is now a more generic runtime ID for Alpine and similar distros, called linux-musl, to support any Linux distro that uses musl libc. All of the other runtime IDs assume glibc.Chip support follows:x64 on Windows, macOS, and Linuxx86 on WindowsARM32 on Linux (Ubuntu 18.04+, Debian 9+)Note: .NET Core 2.1 is supported on Raspberry Pi 2+. It isn’t supported on the Pi Zero or other devices that use an ARMv6 chip. .NET Core requires ARMv7 or ARMv8 chips, like the ARM Cortex-A53.If you are new to Raspberry Pi, I suggest the awesome Pi resources at AdaFruit. You can buy a Pi there, too.Major thanks to Samsung and Qualcomm for investing heavily on .NET Core ARM32 and ARM64 implementations. Please thank them, too! These contributions speak to the value of open-source..NET Core Tools.NET Core now has a new deployment and extensibility mechanism for tools. This new experience is very similar to and was inspired by NPM global tools. You can create your own global tools by looking at the dotnetsay tools sample.You can try the new tools experience with the dotnetsay tool with the following commands:dotnet tool install -g dotnetsaydotnetsay.NET Core tools are .NET Core console apps that are packaged and acquired as NuGet packages. By default, these tools are framework-dependent applications and include all of their NuGet dependencies. This means that .NET Core tools run on all .NET Core supported operating system and chip architecture by default, with one set of binaries. By default, the dotnet tool install command looks for tools on NuGet.org. You can use your own NuGet feeds instead.At present, .NET Core Tools support two installation models:Global install, which requires the -g or –global parameter to install. Globally installed tools are copied to a specific location in your user profile that has been added to the path. They can be invoked directly, enabling the experience you see above, with direct use of “dotnetsay”.Ad-hoc install, which requires the –tool-path parameter to install. Ad-hoc installed tools are copied to a location of your choosing, wherever –tool-path points to. They can be invoked via full path or you can add add the –tool-path location to your path, enabling a similar but custom configuration of global install.Installation of tools without the -g or –tool-path parameters isn’t yet supported. We’re working on various forms of local tools installation, at which point you’ll be able to install tools without those parameters.We expect a whole new ecosystem of tools to establish itself for .NET. @natemcmaster maintains a list of dotnet tools. You might also check out his dotnet-serve tool.The following existing DotNetCliReferenceTool tools have been converted to in-box tools.dotnet watchdotnet dev-certsdotnet user-secretsdotnet sql-cachedotnet efRemove project references to these tools when you upgrade to .NET Core 2.1.Build Performance ImprovementsImproving the performance of the .NET Core build was perhaps the biggest focus of the release. It is greatly improved in .NET Core 2.1, particularly for incremental builds. These improvements apply to both dotnet build on the

As I explained in the post Migrating the build of a VSIX project to a build server if you are a solo developer, I am taking the steps to build my MZ-Tools extension on a build/release server. As part of that process, I realized than rather than installing Visual Studio 2017 Community edition on the server, I could use the Visual Studio 2017 Build Tools that were thought, well, for build servers that don’t need the overhead of a Visual Studio 2017 installation. They are a lightweight version of Visual Studio 2017 without the IDE (devenv.exe executable). They can be used to build either managed (C#, VB.NET, etc.) projects or native (C++) projects. Incidentally my MZ-Tools solution has both type of projects.The Visual 2017 Build Tools can be downloaded from here. Once you install them on a clean machine, you will notice that they provide only the following:A built-in (non-optional) set of components to build MSBuild-based projects (for example managed projects).An optional workload “Visual C++ build tools”.An optional workload “Web development build tools”.There are also optional individual components to install .NET Framework 4.6.1 support Windows SDKs, ATL support, etc.:In my case my extension needs to use .NET Framework 2.0 for some projects (I still support Visual Studio 2005). Since that version is not installed by default on modern versions of the Windows OS, I need to install it going to “Control Panel”, “Programs and Features” item, “Turn Windows Features on or off” link:My obfuscator tool needs the .NET Framework 3.5 SDK (or the .NET Framework 2.0 SDK). While the Visual Studio 2017 Community installer provides the optional individual component “.NET Framework 3.5 developments tools”, the installer of Build Tools 2017 doesn’t. That is not only a pity but also causes a bug if you install yourself the Windows 7.0 SDK that contains the .NET Framework 3.5 SDK that I reported here: the resource .resx files of a .NET project targeting .NET Framework 2.0 are compiled using the Assembly Linker (al.exe tool) of the .NET Framework 4.0, which will cause them to fail silently at run-time. Microsoft fixed the bug just in time for RTM in Visual Studio 2017, but the Build Tools 2017 still has the bug due to the lack of the “.NET Framework 3.5 developments tools”. There is a fix that I explained in the bug report if you find this problem. I have also requested to Microsoft to include the “.NET Framework 3.5 developments tools” in the installer of Build Tools 2017.My extension for Visual Studio targets version 2012, so I need to stick to .NET Framework 4.5, not some higher version. Since that version is not provided by the Build Tools 2017, I need to install the Windows 8.0 SDK, that contains the .NET Framework 4.5 assemblies and SDK.For the C++ projects, I needed to install:“Visual C++ ATL Support”: required to get files such as atlbase.h, etc.“Windows 8.1 SDK”: I could upgrade to some Windows 10 SDK version but they occupy much more space on disk.“UCRT

Libraries (BCL) for .NET library implementations.The .NET Standard Library enables the following key scenarios:Defines uniform set of BCL APIs for all .NET platforms to implement, independent of workload.Enables developers to produce portable libraries that are usable across .NET runtimes, using this same set of APIs.Reduces and hopefully eliminates conditional compilation of shared source due to .NET APIs, only for OS APIs..NET Core 1.0 implements the standard library, as does the .NET Framework and Xamarin. We see the standard library as a major focus of innovation and that benefits multiple .NET products.Support.NET Core is supported by Microsoft. You can use .NET Core in a development and deploy it in production and request support from Microsoft, as needed. Each release also has a defined lifecycle, where Microsoft will provides fixes, updates, or online technical assistance.The team adopted a new servicing model for .NET Core, with two different release types:Long Term Support (LTS) releasesTypically a major release, such as “1.0” or “2.0”Supported for three years after the general availability date of a LTS releaseAnd one year after the general availability of a subsequent LTS releaseFast Track Support (FTS) releasesTypically a minor release, such as “1.1” or “1.2”Supported within the same three-year window as the parent LTS releaseAnd three months after the general availability of a subsequent FTS releaseAnd one year after the general availability of a subsequent LTS releaseSome customers want to deploy apps on very stable releases and do not want new features until the app is developed again. Those customers should consider LTS releases.Other customers want to take advantage of new features as soon as possible, particularly for apps that are almost always in development. Those customers should consider FTS releases.Note: We haven’t released an FTS verion yet. .NET Core 1.0 is an LTS version..NET Core Tools TelemetryThe .NET Core tools include a telemetry feature so that we can collect usage information about the .NET Core Tools. It’s important that we understand how the tools are being used so that we can improve them. Part of the reason the tools are in Preview is that we don’t have enough information on the way that they will be used. The telemetry is only in the tools and does not affect your app.BehaviorThe telemetry feature is on by default. The data collected is anonymous in nature and will be published in an aggregated form for use by both Microsoft and community engineers under