Images make up a huge proportion of the size of a website - a quick test on the Amazon home page shows that 94% of the page's size is due to images. In the next section I'll describe how I built my own global tool dotnet-tinify that uses the TinyPNG api to compress images in a folder. You can then run dotnet serve from any folder. For example, to install Nate's dotnet serve tool, you just need to run: dotnet install tool -global dotnet-serve Obviously this has the downside that all your team have to have the same tools (and potentially the same version of the tools) installed already. The intention is to expose all the first-party CLI tools (such as dotnet-user-secrets and dotnet-watch) as global tools, so you don't have to remember to explicitly install them into your projects. You can think of this as synonymous with npm -g global packages Rather than having to install the tool manually in every project, you install it once globally on your machine, and then you can run the tool from any project. NET Core 2.1, a feature was introduced that allows you to globally install a. Unfortunately, having to manually add this line to every project means that I rarely bother installing non-essential-but-useful tools like dotnet watch anymore.NET Core 2.1 global tools On the one hand, adding them to the project file means that everyone who clones your repository from source control will automatically have the correct tools installed. The tools themselves are distributed as NuGet packages, so when you run a dotnet restore on the project, it will restore the tool at the same time.Īdding tool references like this to every project has both upsides and downsides. csproj file and add a DotNetCliToolReference: Unfortunately, there's no tooling for doing this either in the CLI or in Visual Studio. NET Core 2.1, you need to specifically install these tools in every project where you want to use them. This includes things like the EF Core migration tool, the user-secrets tool, and the dotnet watch tool.
NET Core and ASP.NET Core development) includes the concept of "tools" that you can install into your project. He's also created a CLI template you can install to get started.NET CLI tools prior to. If you're interested in global tools, I strongly suggest reading his post on them, as it provides background, instructions, and an explanation of what's happening under the hood. The code for my global tool was heavily based on the dotnet-serve tool by Nate McMaster.
You can find the code for the tool in this post at. NET Core 2.1, and show some of the code required to build your own global tools.
NET Core CLI tools, describe the changes to tooling in. NET Core CLI global tool I created that can be used to compress images using the TinyPNG developer API.
0 kommentar(er)
