Mastodawn

SSLInsights Feb 19

🐍💻 Fix Npgsql “Bad Protocol Version” on macOS & .NET 6

If you’re building .NET 6 apps on macOS and connecting to PostgreSQL using Npgsql, you might encounter:

🚫 Bad Protocol Version errors

This usually means a mismatch between client and server expectations, but it can be resolved.

Perfect for developers wrestling with cross-platform database connections.

👉 Resolve the error here:
https://sslinsights.com/fix-npgsql-bad-protocol-version-macos-net6/

#dotnet6 #Npgsql #macOSDev #PostgreSQL #DevOps #Programming #ErrorFix #SSLInsights

.NET Bot

Nov 17, 2023

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

Ichinin

✅🎯🙄Jul 14, 2023

So, porting a project from .NET 6 to .NET 8 should be as easy as changing the framework from one to the other, but this has to be done in BOTH the Project properties and the Publish settings or you get a rather peculiar error message about mismatching version numbers.

Found this out recently. The test project i used seems to run just fine, with a few warnings related to changes from .NET 6 to .NET 8, but compiles and gets published.

I ran Strings on the compiled binary and found that there are still some text references to .NET 6 in the binary like:

"System.Security.Permissions.SecurityPermissionAttribute, System.Runtime, Version=6.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"

I assume that this is some sort of left over reference created when the project was created, as the underlying runtime files now point to .NET 8 instead... i'm gonna try porting a larger project with many more dependencies and see if anything breaks.

#dotnet #porting #migration #dotnet6 #dotnet8

K.Riebbels Jun 25, 2023

Dive into consuming #DotNet6 configuration in your services effectively. 🤓 Master IOptions, IOptionsMonitor, IOptionsSnapshot, and learn how to validate settings in Azure. Give it a read! 📚 https://dotnet.kriebbels.me/how-to-consume-dot-net-6-configuration-in-your-services-effectively

How to Consume Dot Net 6 Configuration in Your Services Effectively

Previously on... In my previous blog posts, I wrote about the modularity of the configuration that Dotnet 6 offers. About sources and sections and how to register them. I mentioned how to manually build the configuration object and how to use the def...

A blog to (be) inspire(d) (by) others

Kunal Chowdhury

Jun 23, 2023

Visual Studio 2022 v17.6 now includes an updated Text Template Transformation Toolkit (T4) command-line tool built with .NET 6. Read more 👇🏼
https://devblogs.microsoft.com/dotnet/t4-command-line-tool-for-dotnet/

#VisualStudio #dotnet #dotnet6

Introducing the New T4 Command-Line Tool for .NET - .NET Blog

Learn about the new T4 text template utility built with .NET 6

.NET Blog

K.Riebbels Jun 17, 2023

New article alert! 📢 Diving into DotNet 6 Configuration Management - layered configs, sections, and more. I'd love to hear your thoughts on it! #DotNet6 #coding 🔗https://dotnet.kriebbels.me/dive-into-code-unleashing-the-dotnet-6-configuration-management

Dive into Code: Unleashing the DotNet 6 Configuration Management

Previously on... Previously, in my blog post, I discussed that Dotnet 6 Configuration allowes dynamic reloading of configuration data without application restarts and supported multiple sources such as environment variables, appsettings.json, user se...

A blog to (be) inspire(d) (by) others

InfoQ May 8, 2023

In this article, Tamás-Márk Furó describes the SPA (Single Page Applications) templates, and the proxy changes introduced for the development environment from .NET 5 to .NET 6, .NET 7, and on to the next versions.

ASP.NET SPA Templates Proxy Changes from .NET 5 to .NET 6, .NET 7, and on

From .NET 6 the communication between front-end Single Page Applications (SPA) in ASP.NET and back-end .NET API was changed, with the SPA templates using the front end’s proxy solutions.

InfoQ