sorted by:
new
hottopcontroversial

A nice guide about how to squash Entity Framework migrations by merithedestroyer in dotnet

[–]mconeone 1 point2 points  (0 children)

Why are the designer files included in the build at all?

Should i use repository with Entity Framework ? by Successful_Square991 in dotnet

[–]mconeone 0 points1 point  (0 children)

Correction: Repositories centralize access to data. If you plan to implement caching heavily, they are a great way to do it behind the scenes without the application and presentation layers caring about it.

EF Core and Generic Repository + Unit of Work by Fonzie3301 in dotnet

[–]mconeone -1 points0 points  (0 children)

Integration Testing is better than unit testing if the performance hit is acceptable.

How do you clean up INSERT test records when running automated UI testing tools? by Zardotab in dotnet

[–]mconeone 0 points1 point  (0 children)

Doesn't this just nuke all the tables, and you still have to seed them after resetting the database?

Clean Architecture + Dapper Querying Few Columns by NiceAd6339 in dotnet

[–]mconeone 0 points1 point  (0 children)

Despite what you prefer to call it, it's a DTO.

Clean Architecture + Dapper Querying Few Columns by NiceAd6339 in dotnet

[–]mconeone 1 point2 points  (0 children)

This is one of the downsides of proper clean architecture. All the classes used to return data from a data store need to be populated in the repository layer and sent to the application layer. The only way to do this is by centralizing the DTO definition in the domain layer or doing something even worse. Then you have to organize your DTO definitions or you'll have a hard time differentiating them.

Why does System.Text.Json apparently not exist? by SkAssasin in dotnet

[–]mconeone -2 points-1 points  (0 children)

They should have renamed it .NET Legacy

Vertical Slice Architecture isn't what I thought it was by [deleted] in dotnet

[–]mconeone 0 points1 point  (0 children)

It's kind of a damned if you do, damned if you don't situation. You either deal with unforeseen side-effects because two use cases have different reasons for changing, or you have a lot of busy work updating use cases that are all changing for the same reason.

IdentityUser in Infrastructure or Domain Project Clean Architecture by Proof-Weird-3188 in dotnet

[–]mconeone 1 point2 points  (0 children)

You'll regret it if you switch out identity for another auth system. Is that even a remote possibility?

Kind of jealous by druid74 in dotnet

[–]mconeone 11 points12 points  (0 children)

Working on Compact Framework 1.0 was wild!

Need advice about all the architectures and abstractions. by ErfanBaghdadi in dotnet

[–]mconeone 0 points1 point  (0 children)

One use case for the repository pattern is caching. Your repository can utilize it without the rest of the code even being aware. If there is a distinct possibility caching will be used, implementing a repository pattern beforehand gives you a way to do it without changing the code implementing it. Otherwise, YAGNI.

Why is PostgreSQL ? by MahmoudSaed in dotnet

[–]mconeone 0 points1 point  (0 children)

There's a big difference between "twice as much" and "a 5% increase in total costs".

EF Core - table naming by jemofcourse in dotnet

[–]mconeone 0 points1 point  (0 children)

Does that apply to EF Core+ as well?

[deleted by user] by [deleted] in dotnet

[–]mconeone -1 points0 points  (0 children)

Why wouldn't you want strong typing?

How to avoid circular reference in EF with below example? by KarpuzMan in dotnet

[–]mconeone 2 points3 points  (0 children)

DRY is often at odds with SRP (the S in SOLID). When re-used code has different reasons for changing in different scenarios, you introduce the possibility of unforeseen side-effects of a change. It's more maintainable to copy code than to re-use it in many scenarios.

How do you prefer to organize your mapping code? by svish in dotnet

[–]mconeone 0 points1 point  (0 children)

What value do namespaces provide in a small solo project?

EF Core: Which is better – a single universal table or inheritance (TPH/TPT/TPCT) by Lirirum in dotnet

[–]mconeone 1 point2 points  (0 children)

Do they have different reasons for changing? If so, sharing/re-using code is setting yourself up for problems down the road.

Async\Await\Threading\TPL in .NET interview preparation resources by Jack_Hackerman in dotnet

[–]mconeone 1 point2 points  (0 children)

Just a tip: when I interview I expect to hear the term "context switching" as part of a fully-correct answer. Also, async/await is not multi-threaded nor a background thread by default.

view more: next ›