Skip to main content

Search

Items tagged with: dotnet


If there is some #dotnet developer interested in #GTK4 bindings, dislikes warnings like me and has some spare time to support a small size #OSS project feel free to stop by at https://github.com/gircore/gir.core

There are literally thousands of warnings to fix. The good news is that almost all of them are due to generated code. So a single fix could get rid of hundreds of them.

Come by to scratch that itch.


I'm going to make a prediction. In less than five years, Microsoft is going to give up on C# even on the backend, in favor of multiple languages such as Typescript/Javascript, Rust, Go and even Java. You're going to see them writing their newer backends primarily in Typescript and Rust. #dotnet #programming


Folks will have to update their “find the syntax issues in this C# code” interview questions thanks to #csharp 12. 😅

#dotnet


If someone is curious about #AvaloniaUI and wants to try my Game of Life implementation, I have it up here.

The largest dimensions I could get were 250^2 before it started to feel sluggish. If you have better hardware, try it and see how high you can get.

#dotnet

https://github.com/khalidabuhakmeh/GameOfLifeMvvm


Any #dotnet MAUI folks know what this error means?


The release of #NUNIT v2.0 was on October 3, 2002.

Allowing developers to unit test their #dotnet applications.

Do you even unit test? What unit testing framework are you using?


Content warning: Programming


#dotnet #history #2

The first version of the .NET framework was released on January 15, 2002, for Windows 98, ME, NT 4.0, 2000, and XP.

#development


#dotnet 8 has a real opportunity to make some affiliate money. They just need to partner with Manscape on this ticket.


The trend in #csharp seems to isolate as much inside a function (thanks #fsharp).

I think it would make sense for #csharp to adopt global functions as a first-class citizen.

It definitely would reduce ceremony for folks using something like the Mediator pattern.

#dotnet


The new "required" keyword in #csharp 11 and #dotnet 7 are pretty cool.

Force consumers of your object to define values for properties. This helps reduce the need for constructor overloads.


Content warning: Programming, Dev Recommendations