Start Debugging

Tag: comparison

88 posts · Page 2 of 9

2026-09-17 comparison dotnet dotnet-11

Microsoft.Data.SqlClient vs System.Data.SqlClient in .NET 11

Use Microsoft.Data.SqlClient. System.Data.SqlClient is deprecated, already emits CS0618 on every type you touch, and loses its .NET assets when .NET 8 goes end of support on November 10, 2026, the same day .NET 11 ships. The measured feature gap, the Encrypt default that breaks the migration, and the 7.0 package split.

2026-09-17 comparison dotnet dotnet-11

Process.Run vs Process.Start in .NET 11: which should you use?

Use Process.Run when you start a tool and only care how it exited: one call, a timeout that kills the child, and a ProcessExitStatus with the signal. Keep Process.Start when you need the Process object: writing to stdin, reading output as it arrives, UseShellExecute, or killing a whole process tree.

2026-09-16 comparison ef-core ef-core-11

SQL Server compatibility level 150 vs 160: what changes for EF Core 11 queries

EF Core 11 now defaults UseSqlServer to compatibility level 160, which puts LEAST, GREATEST and two-argument LTRIM/RTRIM into your SQL, including every Take(n).FirstOrDefault(). Keep 160 on SQL Server 2022 and later; pin UseCompatibilityLevel(150) if any environment still runs SQL Server 2019.

2026-09-12 comparison ef-core ef-core-11

Native json column vs nvarchar(max) for storing JSON in SQL Server with EF Core 11

Use the native json type on SQL Server 2025 and Azure SQL: EF Core 11 gets JSON_CONTAINS, typed JSON_VALUE, in-place modify() and JSON indexes out of it. Stay on nvarchar(max) for SQL Server 2019/2022, legacy tooling, or a schema you must be able to roll back.

2026-09-12 comparison csharp dotnet

Lookup<TKey, TElement> vs Dictionary<TKey, List<TValue>> for duplicate keys in C#

Use ToLookup when you group once and only read: it is immutable, returns an empty sequence for missing keys, accepts null keys and keeps first-seen order. Use Dictionary<TKey, List<TValue>> when the groups change after construction or cross a JSON boundary.

2026-09-05 comparison flutter dart

ref.watch vs ref.read in Riverpod: what is the difference and when do I use each?

ref.watch subscribes and rebuilds, ref.read reads once and never rebuilds. Use watch in every build method and read only inside event callbacks. Here is the decision matrix, the source of both methods in flutter_riverpod 3.4.3, and the four silent failure modes: watch in a callback, read in a provider body, read on an autoDispose provider, and read used as an optimization.

2026-09-01 comparison github-copilot ai-agents

Copilot Memory vs Repository Custom Instructions vs AGENTS.md: Which One the Model Actually Reads

Instructions files are deterministic and always sent. AGENTS.md sits at the bottom of the documented repository precedence list. Copilot Memory is a separate store Copilot writes for itself, read by only three surfaces, and it is not in the precedence list at all. Here is the support matrix and the rule for deciding where each convention belongs.

2026-09-01 comparison dotnet dotnet-11

Framework-dependent vs self-contained vs Native AOT for a .NET 11 container image

Framework-dependent on a chiseled aspnet image is the right default for an ASP.NET Core service on .NET 11, because the runtime layer is shared across services and a runtime CVE is fixed by a base image bump. Self-contained trimmed and Native AOT buy a 2x to 5x smaller image and a much faster cold start, and cost you that. Real published sizes, the layer-sharing math, and the .NET 11 base image inference bug that breaks the AOT path.

2026-09-01 comparison csharp csharp-14

Returning a Task directly vs async/await passthrough in a C# repository method: which should you use?

Eliding async/await in a repository passthrough saves about 6 ns and 72 bytes, and costs you a stack frame, try/catch semantics, and safe disposal. Keep return await unless the method is a pure passthrough on a measured hot path.

2026-08-31 comparison agent-skills mcp

Agent Plugins 1.0 vs Vendor-Specific Plugin Formats: What the Shared Standard Actually Covers

Agent Plugins 1.0.0 standardizes exactly two component types: skills and MCP servers. Slash commands, hooks, subagents, rules, LSP servers, permission config and secrets all stay vendor-specific. Here is the field-by-field matrix across Claude Code, Cursor, Copilot and Codex, and which layout to author in.