Mark your calendars: #dotnet7's end of support is approaching fast on May 14, 2024!
After this date, no more updates or security fixes will be issued.
Details on #InfoQ: https://bit.ly/3PPgsmw
Mark your calendars: #dotnet7's end of support is approaching fast on May 14, 2024!
After this date, no more updates or security fixes will be issued.
Details on #InfoQ: https://bit.ly/3PPgsmw
Here is the list of hashtags I currently follow. If I see a post with at least one of these hashtags, I will boost it.
Should I add more hashtags to this list? Or are these already too many?
#dotnetconf #dotnetconf2023 #dotnet6 #dotnet7 #dotnet8 #omnisharp #resharper #jetbrainsrider #nuget #csharp #dotnet
Can confirm on my M2 Pro MacBook that #dotnet8 give MBBSEmu's emulated x86 core a ~20% performance bump by just upgrading from #dotnet7 to #dotnet8! Can't be mad about that 🤓
Makes it *almost* as fast as a 486DX4 @ 100mhz 🤯
Hats off to the #dotnet team at #microsoft and around the world! Really outstanding release 🍾
> Build a basic #DotNet7 app
> Everything works fine
> File Publishes to .exe fine
> Set up for self contained single file for easy distribution
> Exe still needs .dll files
THIS ISN'T SINGLE FILE OR SELF CONTAINED
Also irritating, it seems like the work arounds found searching for a solution don't work anymore.
I am sure there is a way but its damn irritating. It doesn't help that I am basically a newbie at C# and Dotnet.
In distributed architectures, we’ll usually have a number of independent stateless services that serve a purpose (set around a domain, such as ordering items, storing items in a catalog, handling authentication etc.) While services should strive to be stateless, there will be some services that need to track state in order to fufil a business operation or function. Dapr has a state management build block that simplifies state tracking and enables you to store state across a variety of data stores.
Yes! Finally successful in getting my #dotnet7 #Blazor app to import #Mastodon Lists from a csv backup file.
It's nuts how there's actually NO W3C standard for passing array-parameters in a query: https://stackoverflow.com/a/67095427 . It's framework dependent, and is PHP dialect here.
https://docs.joinmastodon.org/methods/lists/#accounts-add wants an account_id array, but NOT in json which would be more concise.
Instead, it's fat pairs of literally { "account_ids[], "<account-id>" } for every account to add!
It's 2023, #dotnet7, and this is fubar is still happening in a #Blazor Hybrid #MAUI app:
"System.Net.Http.HttpRequestException: The SSL connection could not be established, see inner exception.
---> System.IO.IOException: Cannot determine the frame size or a corrupted frame was received."
Meanwhile, back to 2021 in .NET 5.0 -- same: https://stackoverflow.com/questions/64610237/net-5-0-cannot-determine-the-frame-size-or-a-corrupted-frame-was-received
Things I hate about new Microsoft APIs. Completely untested alpha quality, and tied to OS version. Need Win11 upgrade from Win10? wth.