WE ARE DOING IT LIVE!!!!

Spring Meetup @Digicomp Zürich, Wed, Apr 2, 2025, 6:00 PM | Meetup **SPRING .NET Zurich Meetup @ Digicomp Zurich** Join us in person or online at [https://www.youtube.com/c/dotNETZurich](https://www.youtube.com/c/dotNETZurich). Start the

Today @DigiComp-Academy: The .NET User Group Zürich Meetup with Timon Jucker and myself: www.meetup.com/dotnet-zuric...

We are talking about #async and #await in #csharp / #dotnet and some performance stuff with Single Instruction Multiple Data.

Nice mindmap with all the C# language features by @steven-giesel.com 👇
linkdotnetblog.azureedge.net/blog/2025033...

This is a very good step-by-step guide for reproducing in an issue ;)

Darn!

.NET Collections and Data Structures Learn how to apply the right collection for the task at hand.

Read about Collections and data structures in .NET at the JetBrains guide.

www.jetbrains.com/guide/dotnet...

Spring Meetup @Digicomp Zürich, Wed, Apr 2, 2025, 6:00 PM | Meetup **SPRING .NET Zurich Meetup @ Digicomp Zurich** Join us in person or online at [https://www.youtube.com/c/dotNETZurich](https://www.youtube.com/c/dotNETZurich). Start the

The .NET User Group Zurich is back (well, we never went away): 2nd of April at Digicomp Zurich:

1. Demystify Concurrency
2.Using SIMD in C#

Sounds interesting? Join us in-person or remotely: www.meetup.com/dotnet-zuric...

Interested in potential #csharp 14 language features?

Checkout my latest blog post

steven-giesel.com/blogPost/b6d...

IEnumerable vs IEnumerator in C#: One is 2x Faster - LinkedIn Edition During my recent browsing on LinkedIn I saw that question: IEnumerable vs IEnumerator in C#: One is 2x Faster – Which One? Naturally, I was very suspicious. So let's find out what is going on here.

While browsing through LinkedIn, I encountered a benchmark that was unfortunately full of errors. In my upcoming blog post, I will go through the issues and how to design it in a better way

steven-giesel.com/blogPost/b70...

#csharp #dotnet

Really nice work

I am also not sure what the support policy of non-current versions of packages are (from Microsoft).

Just because there is STJ 9.0.1 doesn’t necessarily mean STJ 8.0.4 is outdated.

And yes, direct deps override transitive ones - but that shouldn’t be used to workaround a CVE

That is the funny part - People (including Microsoft) did push out new version still having outdated dependencies.

So even if you as a responsible dev, did you job and keep everything up to date, you would not have been done.

Hmm that might be - never thought of that.

Maybe it is laziness. Every ide makes it somewhat easy to upgrade all your packages in one go.

Central Package Management makes this even more trivial

When you say it - I can remember some discussion going on, on the GitHub repo. And basically, as you can always override such issue with a direct dependency it wasn’t crtitical.

Personally - I don’t like that because it doesn’t lead developers to a „pit of success“

Understandable - but you will face the issue probably in November this year again :)

And I am still not sure why the issue comes in the first place. It might be worth reporting this over at the nuget repo.

I mean, given that even netstandrd2.0 would support the v9 version of the dependency

Well - that is a good question.

We faced similar issues with the System.Text.JSON - where even many MS packages didn’t update STJ to fix the CVE (even though the package itself got updated).

Interesting - for sure there are man corner cases where this might not work.

Thanks for the update

"Drop-Shipping"?

Interesting - that would also move the validation whether or not services can be created to compile-time (not in all cases, but in many) !?

As direct deps are always overruling transient deps, users can override the package. But the other way around doesn't work.

Yes, there is a risk that it breaks your library code, though.

We in bUnit took your last approach.
We aligned TFM with the package version, see: github.com/bUnit-dev/bU...

I also did this in some of my other smaller libraries.
For netstandard2.0, I would roll with the lowest required version - so 8.0.1 for your dep.

LINQ MindMap: .NET 10 Edition Very small update - as the work on .NET 10 starts - or better - continues with full force, I did update the LINQ MindMap.

Highres version: steven-giesel.com/blogPost/004...

.NET 10's first preview will arrive soon. And yes, there are new LINQ operators coming! Therefore I updated my LINQ mindmap to the current #dotnet 10 state.

The link for the High-Res version (free of charge, of course) is in the comments.

#csharp #linq

That is advanced mode :)

When you upgrade packages, do you read the release notes?

We maintainers, normally, invest a bit of time to write them ;)

Nice! Have to check it out!

If that would work in rider or as a standalone tool - that would be something

LOL :) that is a good take!