DOTNET WEEKLY EPS23: .NET 9.0's Breaking changes and fixing last week Aspire problem

Hi friends! This is a weekly video of .NET related stories and code discussions/presentations/demos, with a balanced dose of desktop, web, and mobile development targets. Also contains some optimization techniques, best practices, and about 10% subjective opinions on how .NET should be :)
** Starting from episode 19, we discuss .NET 9.0!
**** Starting from this video EP 21, we are now going to have full HD of 1920x1080 video!
In this episode, we are discussing Breaking changes in .NET 9.0 and also discuss the previous video's problem in using Aspire SqlServer component/support in .NET Aspire in .NET 9.0.
The problem of having Aspire SqlServer support was how to successfully connect to Sql Server in the container from Sql Server Management Studio v20. Now I could do this nicely by using different port beside 1433 configured in the Aspire's AppHost project. But other problems arise as well as gotcha when the container is persistent but the Aspire app is closed!
The main topic of breaking changes is also interesting: we now have to get used to have categorized breaking changes defined in MS .NET doc pages: behavioral changes, source incompatible, and binary incompatible. These categorization is actually available since .NET 8.0, therefore we have to get used to this. Hear my own explanation to these categories in detail!
PS: Starting from this week's video, I suggest you should use .NET SDK 9.0.101 and VS 2022 17.12.3 due to this happening on my previous video:
"Unfortunately, during the preparation of this video, I have to update my VS 2022 again as I found a nasty breaking changes that prevent some of my internal projects to fail when compile, when I was migrating some projects that use older version of nuget packages that in October has new security vulnerabilities findings. "
"This happened due to breaking changes in .NET 9.0 SDK when restoring and auditing nuget packages, and yes, it have been fixed on Tuesday, link below. Therefore I have had to update my VS 2022 to 17.12.3 to ensure that my compilation runs ok and now latest VS 2022 17.12.3 has also updated .NET SDK 9.0.101 fixed this problem, by reverting back to use default behavior."
NOTE: to run the content in this video it is recommended to have 16GB of RAM, as you need Docker to run containers.
Additional links:
What's new in .NET 9.0: learn.microsof...
Breaking changes in .NET 9.0: learn.microsof...
.NET Aspire in .NET 9.0 official docs: learn.microsof...