dotnet项目_dotnet已过时可帮助您使项目保持最新状态

dotnet项目

I've moved my podcast site over to ASP.NET Core 2.1 over the last few months. You might want to follow the saga by checking out some of the recent blog posts.

在过去的几个月中，我已将播客站点移至ASP.NET Core 2.1。 您可能想通过阅读一些最近的博客文章来关注这个传奇。

• Upgrading my podcast site to ASP.NET Core 2.1 in Azure plus some Best Practices

  在Azure中将我的播客站点升级到ASP.NET Core 2.1以及一些最佳实践

• Major build speed improvements - Try .NET Core 2.1 today

  重大的构建速度改进-立即尝试.NET Core 2.1

• Using ASP.NET Core 2.1's HttpClientFactory with Refit's REST library

  将ASP.NET Core 2.1的HttpClientFactory与Refit的REST库一起使用

• Penny Pinching in the Cloud: Deploying Containers cheaply to Azure

  竹Pin捏在云中：便宜地将容器部署到Azure

• Detecting that a .NET Core app is running in a Docker Container and SkippableFacts in XUnit

  检测.NET Core应用程序是否正在Docker容器中运行以及XUnit中的SkippableFacts

• Adding Cross-Cutting Memory Caching to an HttpClientFactory in ASP.NET Core with Polly

  使用Polly向ASP.NET Core中的HttpClientFactory添加交叉剪切内存缓存

• The Programmer's Hindsight - Caching with HttpClientFactory and Polly Part 2

  程序员的后见之明-使用HttpClientFactory和Polly缓存第2部分

• Setting up Application Insights took 10 minutes. It created two days of work for me.

  设置Application Insights花费了10分钟。 它为我创造了两天的工作。

That's just a few of the posts. Be sure to check out the last several months' posts in the calendar view. Anyway, I've been trying lots of new open source tools and libraries like coverlet for .NET Core Code Coverage, and frankly, keeping my project files and dependencies up to date has sucked.

那只是几篇文章。 请务必在日历视图中查看最近几个月的帖子。 无论如何，我一直在尝试许多新的开放源代码工具和库，例如.NET Core Code Coverage的Coverlet ，坦率地说，保持项目文件和依赖项的最新状态很烂。

Npm has "npm outdated" and paket has "paket outdated," why doesn't dotnet Core have this also? Certainly at a macro level there's more things to consider as NuGet would need to find the outdated packages for UWP, C++, and a lot of other project types as well. However if we just focus on .NET Core as an initial/primary use case, Jerrie Pelser has "dotnet outdated" for us and it's fantastic!

Npm有“ npm过时”而paket有“ paket过时”，为什么dotnet Core也没有呢？ 当然，在宏级别上，还有更多需要考虑的事情，因为NuGet需要找到UWP，C ++和许多其他项目类型的过时软件包。 但是，如果我们仅将.NET Core用作初始/主要用例，那么Jerrie Pelser对我们来说“ dotnet过期”是非常棒的！

Once you've got the .NET Core 2.1 SDK or newer, just install the tool globally with one line:

获得.NET Core 2.1 SDK或更高版本后，只需一行就可以在全球范围内安装该工具：

dotnet tool install --global dotnet-outdated

At this point I'll run "dotnet outdated" on my podcast website. While that's running, let me just point you to https://github.com/jerriep/dotnet-outdated as a lovely example of how to release a tool (no matter how big or small) on GitHub.

此时，我将在播客网站上运行“ dotnet过期”。 在运行的同时，让我指向https://github.com/jerriep/dotnet-outdated，作为如何在GitHub上发布工具(无论大小)的一个可爱示例。

• It has an AppVeyor CI link along with a badge showing you that it's passing its build and test suite. Nice.

  它具有一个AppVeyor CI链接以及一个徽章，向您显示它正在通过其构建和测试套件。 真好

• It includes both a NuGet link to the released package AND a myGet link and badge to the dailies.

  它既包含指向已发布程序包的NuGet链接，又包含指向每日包的myGet链接和徽章。

• It's got clear installation and clear usage details.
  它具有清晰的安装和清晰的用法详细信息。
• Bonus points of screenshots. While not accessible to all, I admit personally that I'm more likely to feel that a project is well-maintained if there are clear screenshots that tell me "what am I gonna get with this tool?"
  屏幕截图的奖励点。 虽然不是所有人都能使用，但我个人承认，如果有清晰的屏幕截图告诉我“我将使用该工具获得什么？”，则我更有可能觉得项目得到了很好的维护。

Here's the initial output on my Site and Tests.

这是我的网站和测试的初始输出。

After updating the patch versions, here's the output, this time as text. For some reason it's not seeing Coverlet's NuGet so I'm getting a "Cannot resolve latest version" error but I haven't debugged that yet.

更新补丁程序版本后，这是输出，这次是文本。 出于某种原因，它没有看到Coverlet的NuGet，所以我遇到了“无法解析最新版本”错误，但我尚未对其进行调试。

» hanselminutes.core.tests
  [.NETCoreApp,Version=v2.1]
  Microsoft.AspNetCore.Mvc.Testing 2.1.1
  Microsoft.NET.Test.Sdk 15.7.2
  Selenium.Support 3.13.1
  Selenium.WebDriver 3.13.1
  Xunit.SkippableFact 1.3.6
  coverlet.msbuild 2.0.1 Cannot resolve latest version
  xunit 2.3.1
  xunit.runner.visualstudio 2.3.1

» hanselminutes.core
  [.NETCoreApp,Version=v2.1]
  BuildBundlerMinifier 2.8.391
  LazyCache 2.0.0-beta03
  LazyCache.AspNetCore 2.0.0-beta03
  Markdig 0.15.0
  Microsoft.ApplicationInsights.AspNetCore 2.4.0-beta2
  Microsoft.AspNetCore.App 2.1.1
  Microsoft.Extensions.Http.Polly 2.1.1
  Microsoft.NET.Test.Sdk 15.7.2

As with all projects and references, while things aren't *supposed* to break when you update a Major.Minor.Patch/Revision.build...things sometimes do. You should check your references and their associated websites and release notes to confirm that you know what's changed and you know what changes you're bringing in.

与所有项目和参考一样，当您更新Major.Minor时，事情并不会*被打破。 补丁/修订.build ...有时会发生。 您应该检查您的参考文献及其关联的网站和发行说明，以确认您知道更改了哪些内容以及要带来的更改。

Shayne blogged about dotnet out-dated and points out the -vl (version lock) options that allows you to locking on Major or Minor versions. No need to take things you aren't ready to take.

Shayne在博客中介绍了过时的dotnet，并指出了-vl(版本锁定)选项，该选项使您可以锁定主要或次要版本。 无需拿走您还没有准备好拿的东西。

All in all, a super useful tool that you should install TODAY.

总之，您今天应该安装一个超级有用的工具。

dotnet tool install --global dotnet-outdated

The source is up at https://github.com/jerriep/dotnet-outdated if you want to leave issues or get involved.

如果您想留下问题或参与进来，请访问https://github.com/jerriep/dotnet-outdated 。

Sponsor: Check out dotMemory Unit, a free unit testing framework for fighting all kinds of memory issues in your code. Extend your unit testing with the functionality of a memory profiler!

赞助商：查看dotMemory Unit ，这是一个免费的单元测试框架，用于解决代码中的各种内存问题。 使用内存分析器的功能扩展您的单元测试！

翻译自: https://www.hanselman.com/blog/dotnet-outdated-helps-you-keep-your-projects-up-to-date

dotnet项目