When you work simultaneously with APIs, databases, and frontend applications, it’s almost inevitable to run into inconsistencies in naming conventions. In the modern .NET development ecosystem, where multiple layers and systems with different rules coexist, what may seem like a minor detail to the team often becomes a constant source of friction within the code.

That’s where packages like Nomus come into play.

In this article, I’ll show you how to install the Nomus package in .NET and how to implement it with a practical example — but before we begin, let’s define:

What is Nomus?

It’s a NuGet package designed for applications in .NET 8.0 and above , aimed at simplifying string normalization and conversion between different casing styles .

What problem does it solve?

When working with multiple systems, it’s common to encounter different naming formats:

APIs that use camelCase

Databases with snake_case

Classes in PascalCase

URLs in kebab-case

Without the right tool, you end up writing manual logic…