What problem does it solve? Writing correct Neo4j client code in .NET involves many subtle traps: disposing drivers synchronously, misusing DI lifetimes, returning cursors from managed transactions, or mishandling null graph values. This Skill provides authoritative patterns and a mistake/fix reference for the official Neo4j .NET Driver v6 so C# code connects, queries, and handles errors correctly the first time. ## Core Features & Use Cases - Driver lifecycle and DI setup: Register IDriver as a singleton in ASP.NET Core, use await using, verify connectivity at startup, and load credentials from configuration. - API selection guidance: Decision table for ExecutableQuery vs managed transactions (ExecuteReadAsync/ExecuteWriteAsync) vs explicit transactions, with cursor consumption rules. - Type mapping and batching: Cypher-to-.NET type tables, null-safe record access, UNWIND batching with anonymous types, and Preview object mapping to C# records. - Use Case: You are building an ASP.NET Core service backed by Neo4j Aura. Use this Skill to wire up the driver in Program.cs, run parameterized queries with ExecutableQuery, stream large results via ExecuteReadAsync, and avoid the 20+ documented common mistakes. ## Quick Start Ask the assistant to show how to register the Neo4j driver as a singleton in ASP.NET Core and run a parameterized query with ExecutableQuery.
