Oni
信頼に値する人いない
- Dec 1, 2021
- 11
- 8
Why Autofac instead of Microsoft.Extensions.DependencyInjection?
First of all, let's be clear, both are good at what they do and neither does it better. However, Autofac has functions that can be more than useful to us in such a project. Like auto-generated factories, named and keyed services, ability to add metadata / attribute metadata to a component registration, etc.
Otherwise: If you're not missing any features that Autofac offers over the built-in DI, there's really no reason to switch.
Why Serilog instead of NLog?
More modern API and structured logging by default.
Add enrichers give us also the ability to intercept and modify the messages as we wish.
NLog is a bit faster, but not a relevant difference for us, I noticed that a lot of people here think convulsively about the performance of their application and try to improve it before something solid has even been built. Why make a problem if there isn't one?
Why EntityFrameworkCore instead of Dapper?
Dapper and EF Core are two of the primary ORMs in use in the .NET world, despite the fact that Dapper isn't really an ORM at all; it's more of a mapper library designed to map data results to C# objects. Thus, it's really a very thin layer between your application and the database you are using. EF Core, on the other hand, is a full-fledged ORM with lots of cool features, including change tracking. These features make this library a bit more cumbersome, and possibly a lot less performant than Dapper. But, as I have said before, performance doesn't matter unless you can prove that it matters, and for most apps the difference in speed between EF Core and Dapper will probably not be noticeable to the average user.
(Written by my man Matthew Jones 2 years ago - perfectly described)
I'll update the repository when I'm back home
Edit:
Patched the latest Habbo Flash Client for your project. (WIN63-2021-11-17-1657-345502145)
First of all, let's be clear, both are good at what they do and neither does it better. However, Autofac has functions that can be more than useful to us in such a project. Like auto-generated factories, named and keyed services, ability to add metadata / attribute metadata to a component registration, etc.
Otherwise: If you're not missing any features that Autofac offers over the built-in DI, there's really no reason to switch.
Why Serilog instead of NLog?
More modern API and structured logging by default.
Add enrichers give us also the ability to intercept and modify the messages as we wish.
NLog is a bit faster, but not a relevant difference for us, I noticed that a lot of people here think convulsively about the performance of their application and try to improve it before something solid has even been built. Why make a problem if there isn't one?
Why EntityFrameworkCore instead of Dapper?
Dapper and EF Core are two of the primary ORMs in use in the .NET world, despite the fact that Dapper isn't really an ORM at all; it's more of a mapper library designed to map data results to C# objects. Thus, it's really a very thin layer between your application and the database you are using. EF Core, on the other hand, is a full-fledged ORM with lots of cool features, including change tracking. These features make this library a bit more cumbersome, and possibly a lot less performant than Dapper. But, as I have said before, performance doesn't matter unless you can prove that it matters, and for most apps the difference in speed between EF Core and Dapper will probably not be noticeable to the average user.
(Written by my man Matthew Jones 2 years ago - perfectly described)
I'll update the repository when I'm back home
Edit:
Patched the latest Habbo Flash Client for your project. (WIN63-2021-11-17-1657-345502145)
Last edited:
