How to set primary constructor naming convention to CamelCase

Question

When I refactor a class with a regular constructor to a primary constructor I'd like Visual Studio to capitalize the name of the parameters.

For example:

public class Desk
{
    private Guid Material;
  
    public Desk(Guid material)
    {
        Material = material;
    }
}

would become

public class Desk(Guid Material)
{
    // ....  
}

The reason being PascalCase variables are outside the scope of any method. It doesn't matter to the method if the class chooses to make that public or not.

How can I get VS to suggest this sort of refactor when it suggests a primary constructor.

They're still private to the class, captured as fields, so they should not be PascalCase, they should still be camelCase. — madreflection
– madreflection, Commented May 29 at 16:07
I think you want public class Desk(Guid material) { private Guid Material { get; } = material; } — Charlieface
– Charlieface, Commented May 29 at 16:09
Do you name all your private fields in PascalCase, too? There's nothing saying you can't do that, and it's perfectly fine if you're the only one maintaining that code, but that's not in line with .NET naming conventions and others would be confused by it. The refactoring doesn't offer to do that because it' sticks with .NET naming conventions. — madreflection
– madreflection, Commented May 29 at 16:16
Well, that's not "normal" for .NET. Parameters, local variables, and private fields are usually in camelCase. As a team, you're going to be fighting the norm, and new additions to your team are going to say "What the---?!" Why? — madreflection
– madreflection, Commented May 29 at 16:22
At a high level, you create an analyzer project, implement an analyzer to generate a warning, and implement a code fix that changes the syntax tree. You'll need to search for an example or tutorial on Roslyn analyzers and code fixes for details on how to do that. You can use it either as a Visual Studio extension (applies to all projects) or as a NuGet package (can be added per project using PackageReference,, ideally using an internal NuGet source) — madreflection
– madreflection, Commented May 29 at 16:36

null · Accepted Answer · 2025-05-29 21:28:29Z

1

You can apply rules specifically to primary constructor parameters in ReSharper. As per the comment from Egor Fedorenko:

Edit the default "Parameters" rules to NOT to apply on primary constructor parameters:

Create a new rule "Primary constructor parameters" with _lowerCaseNaming with underscore, and apply it for primary constructor parameters only:

answered May 29 at 21:28

null

5,7421 gold badge23 silver badges39 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

How to set primary constructor naming convention to CamelCase

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related