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.
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.
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.
I'm familiar with his blog and that picture, but this is my first time finding his TH-cam channel and seeing what he looks like now, so it was a surprise 😂
I am amazed by these tools, but once you use them, although they streamline and simplify the work, they also let you know how outdated your projects, which comprise the solution, are. The path that Scott shows is only a quarter of everything you have to do to transition your .NET 6.0 project to .NET 8.0. If your complete path spans from development to production. It took him 10 minutes with three projects, whereas I spent over 2 hours on the same tasks (addressing issues when changing versions, methods that no longer exist and need to be replaced). Then, to complete the path to production, for the CI/CD to deploy it to Azure, it took another five hours, for me. The YAML changes, they're small changes but they matter, and then when he does the Release on the app service, there are also other adjustments to make in a YAML. In short, it takes almost a full workday to get everything updated (Completed the entire path) and have a correct baseline for the .NET 10 version, which is what I hope to use for the next update. I hope to comment on this again in the next 2 years. :)
Seems good if your solution is made up of multiple projects, since the package manager only shows what you're using in that one selected project, where as I can see in the video it's showing updates across all projects
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.)
This is a nice tool. But I wonder why this was not done directly in dotnet command or dotnet nuget command itself. I also see that GUI extension of VS have update all button. So, needed code seems to be already exists somewhere. If best practices are followed it would probably be quite easy to add it to dotnet command line too.
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.
I've written my own bash one-liner that interactively updates packages. super simple, just wraps dotnet list package --outdated with fzf and pipes it into dotnet add package
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?
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.
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.
I'm the other way around. I never do anything command line unless the GUI version doesn't exist. And I'm a long-time, high level programmer. I know it's an uncommon response for people at my level, but it's more efficient and I have no issues with it, otherwise I'd command line more.
@@BrianHunsakerMusic bummer! You can’t repeat GUI operations easily and you may miss all the core nuggets of wisdom of how the systems work. Are you working on Rust or C or C++?
@@mattcargileC# actually. Some people use the excuse that "the GUI doesn't have all the options", but I say they've never used a product like Tortoise SVN / Git. It can be done well and correct and have all the options I normally need. And I don't have to remember cryptic commands or consult my cheat sheet for things I forgot by avoiding the command line. I don't lose anything, I save time trying to memorize or look up cheat sheets. I understand that people who are always in Unix and other types of folks will prefer command line, that makes sense. For programmers in my area, it just doesn't. But I've always been beating my own drum so it's not surprising.
@@mattcargileNot sure what you mean. I hit F5 in Visual Studio. When I build Docker containers locally and push to the cloud, yes I use a few commands since it's much faster than a pipeline. That's about it.
![[#2024MAMA] G-DRAGON - 무제(Untitled, 2014)+POWER+HOME SWEET HOME+뱅뱅뱅+FANTASTIC BABY | Mnet 241123 방송](http://i.ytimg.com/vi/Ox29z5Nf1Uk/mqdefault.jpg)
"You can't just blindly update stuff."
YOU UNDERESTIMATE MY POWER.
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.
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! 😊
Embarrassed that I'd never heard of dotnet-outdated
Not you only
Totally the same
Now I know what I’ve been missing.
Had no idea such a marvel existed! Feels i was livin' under a rock all this while! Thanks for sharing!
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.
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.
.NET SDK already has a command to list outdated/deprecated/vulnerable packages, but it does not upgrade them.
I yoloed .net 6 to .net 8 and everything worked out of the box.
Isn't that profile pic @2:38 from like 2003? Might be time to run profilepic-outdated. 😆
sometimes i still keep the profile picture of me being 6, it has it's charm :D
That's his "codefishing" image to get all the single lines of code.
I'm familiar with his blog and that picture, but this is my first time finding his TH-cam channel and seeing what he looks like now, so it was a surprise 😂
I am amazed by these tools, but once you use them, although they streamline and simplify the work, they also let you know how outdated your projects, which comprise the solution, are.
The path that Scott shows is only a quarter of everything you have to do to transition your .NET 6.0 project to .NET 8.0. If your complete path spans from development to production.
It took him 10 minutes with three projects, whereas I spent over 2 hours on the same tasks (addressing issues when changing versions, methods that no longer exist and need to be replaced).
Then, to complete the path to production, for the CI/CD to deploy it to Azure, it took another five hours, for me. The YAML changes, they're small changes but they matter, and then when he does the Release on the app service, there are also other adjustments to make in a YAML.
In short, it takes almost a full workday to get everything updated (Completed the entire path) and have a correct baseline for the .NET 10 version, which is what I hope to use for the next update.
I hope to comment on this again in the next 2 years. :)
What’s wrong with NuGet Package Manager?
Seems good if your solution is made up of multiple projects, since the package manager only shows what you're using in that one selected project, where as I can see in the video it's showing updates across all projects
@@reikooters you can also see for multiple projects by right clicking the solution and picking nuget manager
@@mustafasabur Thanks for that! Somehow I never noticed it
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.)
This is a nice tool. But I wonder why this was not done directly in dotnet command or dotnet nuget command itself. I also see that GUI extension of VS have update all button. So, needed code seems to be already exists somewhere. If best practices are followed it would probably be quite easy to add it to dotnet command line too.
I just learn about upgrade-assistant, now I can try to upgrade my +12 years old side projects.
thanks hanselman
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.
I've written my own bash one-liner that interactively updates packages. super simple, just wraps dotnet list package --outdated with fzf and pipes it into dotnet add package
Awesome! Together with upgrade-assistant dotnet cli is on fire! Never knew these tools existed, is there a list compiled somewhere with these tools?
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?
9:34 this comnent must be engrave in stone for centuries.
My first and last job was in .NET MVC for Government of India
What is that tool you are using to make arrows/boxes on the screen and zoom in?
ZoomIt
You can’t run .net outdated YOLO 😂 Great video!
I wish i saw this a couple weeks ago when i updated our app. The nuget packages were my biggest issue.
I love the terminal color scheme and theme can we get a link or a copy of the settings for that?
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.
All very cool info... but what is that line completion history browser thing?? That's awesome!
www.hanselman.com/blog/adding-predictive-intellisense-to-my-windows-terminal-powershell-prompt-with-psreadline
If I write unit tests using xUnit, is Playwright not an optionn since it specifically mentions testing frameworks: MSTEST and NUnit?
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.
I use this tool a lot. It’s great
Good video, thanks.😀
How did you know I am buried in .net 6 projects and the need to unbury myself is... palpable!
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
Thanks this is great!
Love seeing you drive stick shift! 😊
I'm the other way around. I never do anything command line unless the GUI version doesn't exist. And I'm a long-time, high level programmer. I know it's an uncommon response for people at my level, but it's more efficient and I have no issues with it, otherwise I'd command line more.
@@BrianHunsakerMusic bummer! You can’t repeat GUI operations easily and you may miss all the core nuggets of wisdom of how the systems work. Are you working on Rust or C or C++?
@@mattcargileC# actually. Some people use the excuse that "the GUI doesn't have all the options", but I say they've never used a product like Tortoise SVN / Git. It can be done well and correct and have all the options I normally need. And I don't have to remember cryptic commands or consult my cheat sheet for things I forgot by avoiding the command line. I don't lose anything, I save time trying to memorize or look up cheat sheets. I understand that people who are always in Unix and other types of folks will prefer command line, that makes sense. For programmers in my area, it just doesn't. But I've always been beating my own drum so it's not surprising.
@@BrianHunsakerMusic what about reproducing builds across dev local env? You need to use the CLI for that.
@@mattcargileNot sure what you mean. I hit F5 in Visual Studio. When I build Docker containers locally and push to the cloud, yes I use a few commands since it's much faster than a pipeline. That's about it.
Is it safe to assume that this tool will search all package reference sources?
Why use this instead of just keeping using nuget package manager?
Scott... can you do a video about Playwright?
"You guys have tests?!" :D
How to get that colorful CLI in Terminal?
I have a video on it
@@shanselman would you share the link plz
@@furqan-safdarohmyposh
--yolo needs to be a flag on every dotnet command! 😂
hi, can you share your gist please :)
Does that also work with Central Package Management (Directory.Packages.props)?