.NET Developers should be using dotnet-outdated to update their project's references

preview_player
Показать описание
Рекомендации по теме
Комментарии
Автор

"You can't just blindly update stuff."

YOU UNDERESTIMATE MY POWER.

TheBuzzSaw
Автор

Thank you for your comment on the previous video regarding my comment on technology debt. This is a great corrective to that. Anyway, after 18 years of programming in C#, I have come to the conclusion to be like a cowboy and update even blindly and wait for what tests and staging will reveal as I collect technology debt. I have seen many destroyed projects and companies because they did not care about updating anything and then the cost of the project increased to such an extent that it could not be saved.

msdevel
Автор

Thanks, we are in the process of updating our .net6 projects, the timing couldn't have been better. Never knew about these tools much appreciated! 😊

vackoo
Автор

Embarrassed that I'd never heard of dotnet-outdated

takistewart
Автор

Had no idea such a marvel existed! Feels i was livin' under a rock all this while! Thanks for sharing!

PranayDora
Автор

I just started upgrading projects this week and have been running into some problems using Microsoft's .Net upgrade assistant. This is something I will definitely check out! Thanks!

phantompooper
Автор

I am absolutely awed. Didn’t know about this and it’s so helpful. My current project team is struggling with the automated scan tools implemented across organisation which reports every vulnerability scan. This is like God send. We host our azure functions in aks. The base images we get have vulnerabilities in the extension bundles. These eventually are updated by Microsoft but I need to check if I can scan the whole docker image and upgrade those packages safely.

hemant-sathe
Автор

Awesome! Together with upgrade-assistant dotnet cli is on fire! Never knew these tools existed, is there a list compiled somewhere with these tools?

bdcp
Автор

Thanks this can be really useful. Although currently it completely aborts at the first project it does not understand, even if I pass it the ifs option (which rather for failed package sources, not for failing projects), so running it for a full directory of projects is still waiting to become easier I guess.

jongeduard
Автор

Another question... Is this something you would use along side the dotnet upgrade tool. And rhe followup is does it replace the nuget package manager altogether? There seems to be complimentary overlap. Or is your typical use case to not use those tools and rely on outdated solely or mostly.

What are the case you would use those tools instead of this one?

(These are all questions i will have to supply the deciders id we adopt this alproach.)

HunterMayer
Автор

I wrote a tool for this at my work for every repo without having a local copy, so that we can just update all packages in all repos nightly. It just uses azure devops rest api to fetch only csproj files into memory, load them with msbuild locator, update them with nuget protocol, push back and open a pr.

Most off the shelf tools including those shown here don't work with projects that contain multiple target frameworks or old style projects like pre core asp, and they tend to be quite slow.

georgehelyar
Автор

Anny good guide on moving from vcxproj to csproj guide? Woud love a tool like the one you mensioned to update like the dotnet upgrade assistant

kouroshb
Автор

If I write unit tests using xUnit, is Playwright not an optionn since it specifically mentions testing frameworks: MSTEST and NUnit?

kjw
Автор

I love the terminal color scheme and theme can we get a link or a copy of the settings for that?

mk.gurenzero
Автор

thanks hanselman <3 but how can you draw those slick arrows?

mhDuke
Автор

Isn't that profile pic @2:38 from like 2003? Might be time to run profilepic-outdated. 😆

Joooooooooooosh
Автор

Maybe this is off topic... Nuget package manager is flagging libraries/packages that have known vulnerabilities/issues. Is that within the scope of this tool?

HunterMayer
Автор

Is it safe to assume that this tool will search all package reference sources?

IssaFram
Автор

What is that colorful tool telling your basic git info all the time?
What is the tool you use to search interactively in the git history? It isn't fzf, I guess.

gff
Автор

Is there an alternative solution to dotnet-outdated that works with .NET framework (classic)? I have projects built with 4.7.2 and 4.8 that I need to run dotnet-outdated against.

jadali