stream:// .net
casbin/Casbin.NET
An authorization library that supports access control models like ACL, RBAC, ABAC in .NET (C#) - casbin/Casbin.NET
Build your own .NET CPU profiler in C#
After describing memory allocation profiling it is now time to dig into the CPU sample profiling in C#!
Next Up for WinForms in .NET 6 Is High DPI Support -- Visual Studio Magazine
While Microsoft and community developers have improved desktop dev tooling in .NET 5 and new open source implementations, the tech hasn't translated easily from the Windows-only .NET Framework, and catch-up efforts planned for next year's .NET 6 include high DPI support for one troublesome project, Windows Forms.
C# vs. F# – planetgeek.ch
C# vs. F# – planetgeek.ch planetgeek.ch Home Books Presentations Legal Notice C# vs. F# By Urs EnzlerIn .NET, C#, F#December
Modern Entity Framework: A Tour of EF Core 5.0 pt 1
#dotnet #EntityFramework #DataEF Core 5.0 includes support for many-to-many relationships and TPT mapping, two sorely missed features from EF6. Join us for a...
Visual Basic in .NET 5: Ready for WinForms Apps -- Visual Studio Magazine
With the milestone .NET 5 and Visual Studio 2019 v16.8 releases now out, Microsoft is reminding Visual Basic coders that their favorite programming language enjoys full support and the troublesome Windows Forms Designer is even complete -- almost.
What's next for System.Text.Json? | .NET Blog
Learn about the new performance, reliaility and easy adoption that has been made with System.Text.Json, and what’s going to come next.
What does the [Intrinsic] attribute in C# do?
A quick Google search for "instrinsic attribute c#" only returns articles about other attributes, such as [Serializable]. Apparently these are called "intrinsic attributes". However, there is als...
F# Ukraine Interview Session #1 with Vagif Abilov
Vagif is a Russian/Norwegian developer working for a Norwegian company Miles. He has about three decades of programming experience, currently focusing on bui...
.NET Core 2.1, 3.1, and .NET 5.0 updates are coming to Microsoft Update
Delivering .NET Core 2.1, 3.1, and .NET 5.0 updates on Windows via Microsoft Update.
The updated GetGCMemoryInfo API in .NET 5.0 and how it can help you | .NET Blog
A bit of history In .NET 3.0 we introduced a GC.GetGCMemoryInfo API for library code to get memory load related things (this was used in ArrayPool for example) so it exposed things library folks wanted at the time. In 5.0 I got requests from folks to monitor more things about the GC.
Understanding Disposables In .NET Dependency Injection - Part 1 - Steve Talks Code
In this post I will be discussing the traps that can catch you out by potentially creating memory leaks when registering types that implement the IDisposable interface as services with the out-of-the-box .NET Dependency Injection container.
KorzhCom/EasyData
EasyData open source framework for easy CRUD operations UI (and more) - KorzhCom/EasyData
Enabling and using C# 9 features on older and “unsupported” runtimes
A guide on how to enable support for many new C# 9 features on older runtimes and frameworks that do not offer them out of the box
Generating Code in C#
How Source Generators, a New Feature Coming In C# 9.0, Will Help You Automate Code Creation
Announcing ODP.NET 19.10 Release: New .NET 5 and Bulk Copy Support
Today, Oracle released ODP.NET 19.10 for .NET 5 (ODP.NET Core) and .NET Framework (managed ODP.NET) on NuGet Gallery. These releases…
Astonishing Performance of .NET 5
I migrated Fusion to .NET 5 today — and honestly, I was absolutely shocked by the performance boost it brings:
Introducing F# 5
For the past five years, we've been working to make F# as good as it can on .NET Core. With the release of .NET 5, we're also introducing F# 5 - the culminat...
Exploring .NET 5 with the AWS Toolkit for Visual Studio | Amazon Web Services
This week, .NET 5.0 was officially released. Read about how you can get more out of your .NET investments on AWS and some of the services and tools that we have worked on to support .NET 5 on AWS. In this post we show how you can use the AWS Toolkit for Visual Studio to […]
Announcing ASP.NET Core in .NET 5 | ASP.NET Blog
.NET 5 is now released! .NET 5 is the next version of .NET Core and the future of the .NET platform. With .NET 5 you have everything you need to build rich, interactive front end web UI and powerful backend services.
Reactive Programming: Hot Vs. Cold Observables
The Observer Pattern is at the core of reactive programming, and observables come in two flavors: hot and cold. This is not explicit when you are coding, so this article explains how to tell the difference and switch to a hot observable. The focus is on hot observables. The concepts here are relevant to all languages that support reactive programming, but the examples are in C#. It's critical to understand the distinction before you start doing reactive programming because it will bring you unstuck if you don't. Please support this blog by signing up for my course Introduction to Uno Platform. Reactive Programming It's hard to clearly define what Reactive Programming is because it spans so many languages and platforms, and it has overlap with programming constructs like events in C#. I recommend reading through the Wikipedia article because it attempts to give a history of reactive programming and provide objective information. In a nutshell, reactive programming is about responding to events in the form of sequences (also known as streams) of data. Technically, any programming pattern that deals with this is a form of reactive programming. However, a pattern called the Observer pattern has emerged as the de facto standard for reactive programming. Most programming languages have frameworks for implementing the observer pattern, and the observer pattern has become almost synonymous with reactive programming. Here are some popular frameworks: RxJS (JavaScript) System.Reactive(.Net) ReactiveX (Java oriented - with implementations for many platforms) RxDart (Dart) The concept is simple. Observables hold information about observers who subscribe to sequences of notifications. The observable is responsible for sending notifications to all of the subscribed observers. Note: The publish-subscribe (pub/sub pattern) is a closely related pattern, and although technically different, is sometimes used interchangeably with the observer pattern. Hot Observables Hot observables start producing notifications independently of subscriptions. Cold observables only produce notifications when there are one or more subscriptions. Take some time to read up about the observer pattern if you are not familiar. If you start Googling, be prepared for many different interpretations of the meaning. This article explains it well and gives examples in C#. This article is another good article on the topic of hot and cold observables. A hot observable is simpler because only one process runs to generate the notifications, and this process notifies all the observers. A hot observable can start without any subscribed observers and can continue after the last observer unsubscribes. On the other hand, a cold observable process generally only starts when a subscription occurs and shuts down when the subscription ends. It can run a process for each subscribed observer. This is for more complex use cases. Hot Observable Use Case Let's imagine the simplest use case. The notification publisher is a singleton. It gets instantiated when the app starts and will continue to poll for information throughout the app's lifespan. It will never shut down, and it will send notifications to all instances of the subscriber that subscribe to it. In C#, observers implement the IObserver<> interface, and observables implement the IObservable<> interface. This is an implementation of the use case in C#. We create the publisher with CreateObservable(), and then two subscribers subscribe. They both receive the notification Hi repeatedly until they unsubscribe, or we can cancel the task. This is a hot observable because the long-running task runs independently of the subscribers. Note: this is not the recommended approach. This is just an example for clarity. View this gist on GitHub Reactive Extensions The reactive extensions are a set of C# helpers for building observables and observers. They exist in the namespace System.Reactive. Their home is in this is repo. You can use it by installing the System.Reactive NuGet package. It would help if you used these extensions instead of directly implementing IObservable<> or IObserver<>. Reactive frameworks for other platforms have similar libraries. Cold Observables Observable.Create from the reactive extensions creates observables. What the documentation doesn't tell you is that the observable is cold by default. The code that you supply doesn't run unti...
Developing a Lightweight TUI Music Player in C# using Terminal.Gui (Part One)
Note: Part two of this guide is now available here! Recently, I’ve been listening to a lot of SomaFM internet radio streams while I work as they have a lot of terrific commercial-free programming. One day while being creatively inspired by the Sonic Universe station’s offerings, I had the idea...
Use ASP.NET With Turbolinks 5
The web development community has come a long way since the early days of the web. Building interactive web experiences can leave many developers in a state of paralysis. What web framework should we use? What transpiler should create my assets? Do I go with React or VueJS? So many questions that we need to answer. For folks who work on the back end of the technological stack, or for people who only focus on HTML and CSS, rejoice!
gRPC performance improvements in .NET 5 | ASP.NET Blog
gRPC and .NET are fast. Explore the many performance improvements in gRPC and .NET 5.
C#9 records: immutable classes - NDepend
C#9 introduces record to define immutable data classes with a consice syntax. Learn to use records and avoid common mistakes.
Hot Vacancies
.NET Developer
A developer is needed for an American startup that manages the operation and maintenance of residential complexes. This is a new project from scratch with a temporary integration of the old system (Web Forms, no code access).
.NET Backend Developer
Field Complete is a team of passionate, young & fun-loving professionals looking to change the uneffective way that Servicing Industry works on US markets. Field Complete is growing really fast. We are looking for a Back End Developer to build a top-level modern API, ready for high load. Strong expertise with:
Senior Xamarin Developer
You will join a mobile team which is working on two very exciting projects, Sportsbook and Casino. The apps are used by users in the US, where we are working on the regulated markets. We are releasing apps every two weeks. Our apps are generating almost 75% of the company revenue and the user base is growing daily. Technical stack on the project: Xamarin.Forms, MVVM with DI, NewRelic, Azure + App Center etc. Switching to .Net MAUI in the nearest 2-3 months.
Senior .NET Engineer
You will be working in a large US-oriented company that puts as a priority: security, performance, and stability. The candidate will work on pushing a huge number of changes (several thousand per sec) to several thousand clients in a near real-time manner.
Middle strong .NET developer
Our customer is an American company that develops software for businesses to help manage their networks, systems, and information technology infrastructure. The company provides purpose-built products for IT professionals, MSPs, and DevOps pros.