Menu
Forums
All threads
Latest threads
New posts
Trending threads
New posts
Search forums
Trending
What's new
New posts
New profile posts
Latest activity
Members
Current visitors
New profile posts
Search profile posts
Upgrades
Log in
Register
What's new
Search
Search
Search titles only
By:
All threads
Latest threads
New posts
Trending threads
New posts
Search forums
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
Server Development
Habbo Retros
Habbo Development
Starlight [C#/.NET Core/Dapper]
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="Oni" data-source="post: 471783" data-attributes="member: 104662"><p><strong>Why <em>Autofac</em> instead of <em>Microsoft.Extensions.DependencyInjection</em>?</strong></p><p>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.</p><p>Otherwise: If you're not missing any features that Autofac offers over the built-in DI, there's really no reason to switch.</p><p></p><p><strong>Why <em>Serilog </em>instead of <em>NLog</em>?</strong></p><p>More modern API and structured logging by default.</p><p>Add enrichers give us also the ability to intercept and modify the messages as we wish.</p><p>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?</p><p></p><p><strong>Why <em>EntityFrameworkCore </em>instead of <em>Dapper</em>?</strong></p><p>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.</p><p><em>(Written by my man Matthew Jones 2 years ago - perfectly described)</em></p><p></p><p>I'll update the repository when I'm back home <img src="/styles/default/xenforo/smilies/emojione/smile.png" class="smilie" loading="lazy" alt=":)" title="Smile :)" data-shortname=":)" /></p><p></p><p><strong>Edit:</strong></p><p>Patched the latest Habbo Flash Client for your project. (WIN63-2021-11-17-1657-345502145)</p><p><img src="https://i.imgur.com/byPAaBc.gif" alt="" class="fr-fic fr-dii fr-draggable " style="" /></p></blockquote><p></p>
[QUOTE="Oni, post: 471783, member: 104662"] [B]Why [I]Autofac[/I] instead of [I]Microsoft.Extensions.DependencyInjection[/I]?[/B] 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. [B]Why [I]Serilog [/I]instead of [I]NLog[/I]?[/B] 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? [B]Why [I]EntityFrameworkCore [/I]instead of [I]Dapper[/I]?[/B] 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. [I](Written by my man Matthew Jones 2 years ago - perfectly described)[/I] I'll update the repository when I'm back home :) [B]Edit:[/B] Patched the latest Habbo Flash Client for your project. (WIN63-2021-11-17-1657-345502145) [IMG]https://i.imgur.com/byPAaBc.gif[/IMG] [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
Server Development
Habbo Retros
Habbo Development
Starlight [C#/.NET Core/Dapper]
Top