Terminaux 8.2 is coming soon!
Stay tuned for the release on GitHub and on NuGet!
#Terminaux #Colorimetry #GitHub #NuGet #TechNews #TechUpdates #csharp #programming #dotnet
https://officialaptivi.wordpress.com/2026/03/13/terminaux-8-2-is-coming-soon/
Terminaux 8.2 is coming soon!
Stay tuned for the release on GitHub and on NuGet!
#Terminaux #Colorimetry #GitHub #NuGet #TechNews #TechUpdates #csharp #programming #dotnet
https://officialaptivi.wordpress.com/2026/03/13/terminaux-8-2-is-coming-soon/
chicken nuget
"Absolutely no one should use nuget."
Three years ago I blogged about #nuget serving outdated #curl packages.
They then removed the packages I found.
I checked nuget again *today* and immediately found a nine year old curl package that is downloaded at the rate of 1,000 times/week from there... with **64** known vulnerabilities.
The blog post from back then: https://daniel.haxx.se/blog/2023/03/02/the-curl-nuget-story/
Again, something strange learned today: The #dotnet #nuget package `Microsoft.CodeAnalysis.Testing` is still not updated for .Net10 🤯
Issue tracking this: https://github.com/dotnet/roslyn-sdk/issues/1233
Just had to resort to:
```csharp
private static readonly ReferenceAssemblies Net100 = new(
targetFramework: "net10.0",
referenceAssemblyPackage: new PackageIdentity("Microsoft.NETCore.App.Ref", "10.0.1"),
referenceAssemblyPath: Path.Combine("ref", "net10.0"));
```
I recently released v2.0.0 of SignalRGen - a NuGet package that reduces SignalR boilerplate.
Type-safe hubs, cleaner client/server code, faster dev of realtime communication.
So while I'm working on my #dotnet SignalR boilerplate free Source Gen #nuget package a colleague brought up a different way of defining the interface for generation.
I've tried my best to describe that in this issue: https://github.com/MichaelHochriegl/SignalRGen/issues/74
Would be great to get some feedback on what you all prefer.
I'm fairly new to open source #dotnet #nuget package coding and I've just released v1.0.0 of my package, however I've just discovered a good way to move the package forward, that will lead to a breaking change. Do you find it problematic to release a v2.0.0 aprox. two months after v1.0.0 with no version inbetween? (If anyone wants to take a look at the project: https://signalrgen.net - still WIP)
#FluentAssertions has been taken over by a hostile company. They have changed the license from Apache 2.0 to some bs commercial license, probably without consent from the contributors. I've created a fork, feel free to depend on it if you need a drop-in replacement that won't just change the license.
I have just released the first version of my #csharp client library for the #Streamlabs socket API. It allows you to receive events from Streamlabs in real-time and is available via the #nuget package registry.