Scrutor
sdk
Our great sponsors
Scrutor | sdk | |
---|---|---|
16 | 113 | |
3,417 | 2,532 | |
- | 1.8% | |
0.0 | 10.0 | |
about 1 month ago | 2 days ago | |
C# | C# | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Scrutor
- Reflection -> Source Generated
-
Why asp.net core is not popular like Spring boot or nodejs, although it's better than both in all aspects?
You can with MS's default DI as well via scrutor.
- C# Design Patterns: Implementing the decorator pattern
-
Migrating to .Net Core MVC from .Net framework 4.8
if you are heavily invested in autofac you can replace the build in DI with another container. at this point i don't think it is that necessary. especially if you use scrutor. it gives your some nice assembly scanning registration that autofac/simple injector give https://github.com/khellang/Scrutor
-
ModuleLoader vs Reference
If you wouldn't mind, I have one additional question. If I wouldn't bother to remove this loading, how could one add that as service when using DI? I have found tool called Scrutor (https://github.com/khellang/Scrutor), is it something commonly used in situation like this?
-
Would you use an attribute that registers your interface/classes with .nets IoC container?
I much prefer using Scrutor and asbly scanning myself. https://github.com/khellang/Scrutor
-
Dependency Injection
you can also use Scrutor to get closer to Autofac functionality https://github.com/khellang/Scrutor
-
You Probably Don't Need to Worry About MediatR
That can't be the only justification, because you can easily register services using reflection without using MediatR.
-
A new small opensource library - Autojector.
I might suggest additional registration time extensions to modify the behavior as needed on classes. Take a look at Scrutor for some inspiration on API specifically.
-
6 .NET Myths Dispelled — Celebrating (Almost) 21 Years of .NET
There is a package that simplifies it for you if you want. But not everybody agrees that automatic registration is good pattern, so you have a choice.
sdk
-
Programmatically elevate a .NET application on any platform
[DllImport("libc")] private static extern uint geteuid(); public bool IsCurrentProcessElevated() { if (RuntimeInformation.IsOSPlatform(OSPlatform.Windows)) { // https://github.com/dotnet/sdk/blob/v6.0.100/src/Cli/dotnet/Installer/Windows/WindowsUtils.cs#L38 using var identity = WindowsIdentity.GetCurrent(); var principal = new WindowsPrincipal(identity); return principal.IsInRole(WindowsBuiltInRole.Administrator); } // https://github.com/dotnet/maintenance-packages/blob/62823150914410d43a3fd9de246d882f2a21d5ef/src/Common/tests/TestUtilities/System/PlatformDetection.Unix.cs#L58 // 0 is the ID of the root user return geteuid() == 0; }
-
Swift was always going to be part of the OS
> There's definitely things they tried to improve on that... weren't really improvements. The way "assemblies" are matched in .NET is much more sophisticated- the goal there was to try to kill DLL hell. It evolved into the Global Assembly Cache, which is sort of the Windows Registry of DLLs. Not a huge fan of those bits.
The Global Assembly Cache did not make the jump to the modern .NET (Core). There was the thing called `dotnet store`, but it’s broken since .NET 6: https://github.com/dotnet/sdk/issues/24752
The assembly redirection hell has also been greatly reduced there.
-
.NET Blazor
I do the same.
I have a small write-up here: https://chrlschn.dev/blog/2023/10/end-to-end-type-safety-wit...
You get end-to-end type safety (even better once you connect it to EF Core since you get it all ways to your DB).
With this setup with hot-reload (currently broken in .NET 8 [0]), productivity is really, really good. Like tRPC but with one of the most powerful ORMs out there right now.
[0] https://github.com/dotnet/sdk/issues/36918
-
Why does dotnet cli not support updating sdk's?
Noticed an open issue just now.
-
.NET 8 – .NET Blog
You're thinking of https://github.com/dotnet/sdk/issues/22247
-
LÖVE: a framework to make 2D games in Lua
That's a twisted and wrong narrative
Unity like refers to a Editor driven approach
Unity became popular with its moonscript language (javascript like), they then ditched it to focus on C#, but what propelled unity to what it is today is the Editor driven approach, not c#, not DOTS
They are forced to transpile C# to C++ via IL2CPP as a result to target consoles/mobiles
C# is a disease when it comes to console/mobile support
It's a substantial dependency, quite heavy
And you are not free of unity like fuck ups, it's a microsoft language after all:
https://github.com/dotnet/sdk/issues/22247
And let's not forget when they changed the license of their debugger overnight to prevent people from using it in their products (jetbrains for example)
And them deprecating open source tooling to a proprietary/closed one for vscode (c# devkit)
Let's be careful when we recommend evil as an alternative to evil ;)
-
How to run multiple programs like python3 filename.py???
The script can be found at the end of the thread here https://github.com/dotnet/sdk/issues/8742
-
Writing Python like it's Rust
Another difference you might be surprised by is that the .NET tooling by default collects various data from your system and sends it to Microsoft [1]. If you want to avoid this (and still want to use .NET) you'll have to make sure that the environment variable DOTNET_CLI_TELEMETRY_OPTOUT is set in all contexts before touching anything.
[1] https://github.com/dotnet/sdk/issues/6145
-
.NET 8 is on the way! +10 Features that will blow your mind 🤯
SDK Pull Request
-
Disadvantages of using F# with Mono?
Pretty sure the final file referenced here https://github.com/dotnet/sdk/issues/8742 is the one I am thinking of.
What are some alternatives?
Autofac - An addictive .NET IoC container
kdmapper - KDMapper is a simple tool that exploits iqvw64e.sys Intel driver to manually map non-signed drivers in memory
Lamar - Fast Inversion of Control Tool and Successor to StructureMap
MQTTnet - MQTTnet is a high performance .NET library for MQTT based communication. It provides a MQTT client and a MQTT server (broker). The implementation is based on the documentation from http://mqtt.org/.
Microsoft.Extensions.DependencyInjection
ASP.NET Core - ASP.NET Core is a cross-platform .NET framework for building modern cloud-based web applications on Windows, Mac, or Linux.
Simple Injector - An easy, flexible, and fast Dependency Injection library that promotes best practice to steer developers towards the pit of success.
.NET Runtime - .NET is a cross-platform runtime for cloud, mobile, desktop, and IoT apps.
Unity - This repository contains all relevant information about Unity Container suit
vscodium - binary releases of VS Code without MS branding/telemetry/licensing
DryIoc - DryIoc is fast, small, full-featured IoC Container for .NET
CoreCLR - CoreCLR is the runtime for .NET Core. It includes the garbage collector, JIT compiler, primitive data types and low-level classes.