I had some people DM me and tag me on this post to determine if it's malware or "slop". Using the software requires providing billing information prior to downloading the trial. I got mildly annoyed by this and contacted support. I requested access to the binary without needing to provide billing information. Their support team was ... actually very, very, very polite and nice. I was kind of taken back by how polite they were. They provided me the software with a 60 day trial. I can't tell if they know I do malware development and reverse engineering because (usually) places are hesitant to just give me the stuff like this on a platter. I would feel bad if I was hyper-critical of this product because of how polite the person running this profile is, they're just a chill dude. To be direct: - Is this malware? No. - Is this slop? Probably not, no. - Does this actually improve FPS? Yes, unironically. However, it is very important you realize this software is changing the voltage and clock speed on your machine (among other things). They're achieving this in a legitimate way by working with AMD and Intel with actual SDK (Software Development Kit) documentation. This product went to great lengths to secure its source code. It has junk code insertion, in-memory patching (stubs), junk variables, control flow obfuscation, and it also does device finger-printing to ensure you don't steal their product. All of this was performed using professional anti-reverse engineering products. It was a real pain in my balls to deal with. I got mildly irritated at several points. Some strings are AES256 encrypted and decrypted when needed (run-time lazy loading) making static-analysis even more difficult. Despite all of this, none of it is malicious. They just don't want nerds stealing their stuff. At first glance however it does use methods similar to malware to avoid reverse engineering. The application UI is also incredibly heavy. It is using the latest and great .NET UI stuff to make it look super cool and gamer-like. It launches from HyperTune.exe which then loads the actual (super obfuscated) HyperTune.dll using HOSTFXR (Google it). The obfuscation tools they used disassembled and fractionated the application entry point (and subsequent functionality) down into 1,618 other functions (see attached image) The only saving grace was the visibility into it's dependencies and other 3rd party libraries it uses (Realm for local settings savings, Sentry for logging errors, SimpleInjector for handling classes they use, etc). I won't go into full details on how their product actually works, I would feel bad because of support dude being a chill dude, but here is my main criticism: - Loading of kernel-mode drivers from vendors for overclocking. They load AMD and Intel drivers based on your hardware profile on your machine. However, the driver configuration settings are set to AUTOSTART. Hence, once you use this software these kernel-mode components will auto-start even if HyperTune is not running. Additionally, uninstalling HyperTune will not uninstall these kernel-mode components. These kernel-mode components come by default with the installer in a directory called /3p/ but move to SYSTEM32 after installation (as they should be). - For reasons I do not understand, HyperTune modifies HKLM\Software\Policies\Microsoft\Windows\WindowsUpdate\AU ... it disables automatic updates from Windows. I don't know why. My presumption is this could prevent potential driver conflicts, but if not managed correctly this exposes users to security vulnerabilities. Did they actually spend $1,000,000 developing this? With a full development team, infrastructure they're using (Sentry, VERCEL, enterprise and professional anti-reverse engineering tools, etc) ...maybe...?

Cada tanto me toca bailar con uno.... Que feo es querer meter alguna tecnología nueva a un WCF OWIN SimpleInjector

Catching up on comments in this one: github.com/dotnet/aspnetcore… Just coincidentally, I strongly recommended to a client this week to eliminate the usage of SimpleInjector because it didn't play well w/ the .NET DI abstractions in new-ish .NET as they upgrade

Are you interested to hear the names of nuget packages that serve different purpose and how to create your own nuget package? Following are the nuget packages under different purposes : Logging - Serilog - NLog Dependency Injection - Autofac - NInject - SimpleInjector - StructureMap - Unity - DryIoc - Castle Windsor - Scrutor - Lamar - Microsoft.Extensions.DependencyInjection Testing - xUnit - NUnit - MSTest - SpecFlow - Shouldly - FluentAssertions - AutoFixture - GenFu Encryption - BouncyCastle - DotNetCore.Encrypt - Effortless Mocking - Moq - FakeItEasy Background Jobs - Quartz - Hangfire Serialization - Newtonsoft.Json - System.Text.Json Date and Time - NodaTime - Humanizer Mapping - AutoMapper - Mapster - Mapperly - TinyMapper - ExpressMapper - AgileMapper Network - DotNetty - Network Fake Data - Bogus Authentication - JWT - IdentityServer4 Validation - FluentValidation Guard Clauses - Ardalis.GuardClauses Caching - Redis ORM - EntityFrameworkCore - Dapper - NHibernate - Simple.Data - LinqConnect - Massive API Gateway - Ocelot - Kong.Net API Calls - Refit - RestSharp - Flurl - RestEase - HttpClientFactory - Polly Feature Flags - FeatureToggle - NFeature - FeatureSwitcher - FeatureFlags Messaging - MassTransit - RabbitMQ.Client - Nats.Client - EasyNetQ Real-Time Communication - SignalR API Documentation - Swashbuckle.AspNetCore - NSwag.AspNetCore Fault Handling - Polly CQRS - MediatR 📌 In my tomorrow's newsletter I'll show how to create your own Nuget Package and publish it on Nuget Package Manager. If you are interested to learn about it make sure to subscribe my newsletter with 8200 software engineers 👉 lnkd.in/dNHxJGRG

What I find useful from SimpleInjector is the ability to resolve dependencies depending on the service type, implementation type and receiving type. That allows me to declare ILogger in C's constructor and have Logger<T> injected.

Simple Injector is my favorite.

That would literally kill support for non-conforming containers like @simpleinjector

Yeah! Public holiday learning with lots of tech stacks (GraphQL, MongoDb, Mediatr, SimpleInjector, HotChocolate, etc).

3/3 While a 'conforming container' isn't the worst mistake by a long shot, the end problem is the same; because MS provides a conforming container, new devs may not even know what Autofac or SimpleInjector -are-, because MS provides, and that's what MVPs and the like blog about.

Story of my life. 100÷ of #SimpleInjector 5.2 goes out to binding redirect issues.

I released an alpha of the ASP NET Core integration packages for #simpleinjector v5.2. These packages contain breaking changes and I need your help in making sure they work as intended in your applications. Please try them out and report any inconsistencies.

@simpleinjector does, but at runtime. Why would you want the source?

* Use SimpleInjector as a first-class DI container. * Ability to use something like reflection, but type-safe without the performance cost. * Ability to compile very simple console apps to Web Assembly (no Blazor, just runtime app code). * Extension Properties in C#.

@simpleinjector has a neat "Verify" method to check if composition is valid (if all dependencies are accounted for). Besides that, no automatic testing of container configuration. ... But I aim to keep it dead simple, using good old (unit-tested) factories for fancy stuff

SimpleInjectorで不要なインスタンス生成を抑止する qiita.com/Nuits/items/e858c7… #Qiita かいた。

yes but as a library developer i am tired of pointing people to some other thing

One of the reasons I don’t use MS DI for anything more complex than Hello World-level apps. @simpleinjector FTW 😍

We are using SimpleInjector in most of our projects. And Microsoft for smaller aspnet core projects

We use SimpleInjector and love it.

@simpleinjector has always had great perf, a good set of powerful APIs, and supports design patterns and features that lead developers into the 'pit of success'. I've used it on many projects and give it 👍👍