"that’s scumbag behavior"
Imagine saying something like this in regards to someone like @jbogard who has made so many huge contributions to the #dotnet community over the years.
I'm sorry for the way you're being spoken to in that thread.
Maintainers have every right to introduce changes to licensing without being bullied. Companies are also free to simply not use the tool(s) in question.
"that’s scumbag behavior"
Imagine saying something like this in regards to someone like @jbogard who has made so many huge contributions to the #dotnet community over the years.
I'm sorry for the way you're being spoken to in that thread.
Maintainers have every right to introduce changes to licensing without being bullied. Companies are also free to simply not use the tool(s) in question.
"that’s scumbag behavior"
Imagine saying something like this in regards to someone like @jbogard who has made so many huge contributions to the #dotnet community over the years.
I'm sorry for the way you're being spoken to in that thread.
Maintainers have every right to introduce changes to licensing without being bullied. Companies are also free to simply not use the tool(s) in question.
Entity Framework Query Plans in VS Code
This EFCore visualizer extension has been available for Visual Studio for a while, now it's also available as a VS Code extension.
https://t.co/EHj4KDXGwv
@RaidTeyar Against the business requirements, surely? Strongly typed IDs have their benefits, but I don't think every use of int or Guid amounts to primitive obsession.
@mehdidotnet@jerrynixon True, but that assumes EF Core is generating the GUID. Disconnected clients may need to generate IDs independently, potentially without EF Core at all. That's where a SQL Server-friendly sequential GUID generator on the client-side is useful.