Why I’m Building TigerWrap

I’ve worked with SQL Server for over 15 years. I love stored procedures. I love clean schemas. What I don’t love is the boilerplate — writing the same C# wrappers over and over, carefully mapping parameters, handling nulls, getting output parameters right, and repeating this across every project.

TigerWrap started because I got tired of wasting time on things that should be automated — but still wanted full control over my database.

I’m not interested in frameworks that try to take over the whole stack. I already have a schema, stored procedures, and error-handling patterns that work — including a shared response code system.

What I want is clean, focused C# code that wraps my stored procedures the way I wrote them — with proper support for:

  • Table-valued parameters
  • Output parameters
  • Nullability
  • Consistent response code handling

That’s it. No assumptions. No magic. Just a generator that respects my design and saves me time.

TigerWrap is a CLI tool that reads your database schema and gives you reliable, testable C# code to call your stored procedures — like a grown-up Dapper generator, but focused and respectful of your SQL-first design.

It already generates wrapper methods, maps result types, and supports output parameters, return values, TVPs, and enums — all with a focus on clarity, testability, and respecting your schema.

It’s not for everyone. But if you’ve ever written SqlCommand boilerplate or fought with DataTable to pass a TVP — it might be for you.

If that resonates, check it out or drop me a note. I’m building it in the open, and I’d love feedback.

💬 Want to get in touch?
You can find me on LinkedIn — I’d love to hear your thoughts.