C# Naming Conventions allows you to change naming conventions for entire C# projects in one click, saving you hours of painstaking work and valuable time. Your original code style and formatting is preserved - only the naming changes! C# Naming Conventions does only one thing and it does it well.
Runs on Windows with version 4.6.1 or higher of the .NET Framework.
The Free Edition limits output to 100 lines per file (no limit on the number of files).
Results after Changing Options:
Q: Are the original C# files altered in any way?
Your existing code is left completely intact. The new C# files are output to the new location that you specify.
Q: What is the renaming accuracy?
Our accuracy is very high, but there will be a few minor adjustments required for most projects.
Q: What naming convention options are offered?
Naming conventions can be set for the main categories of: locals & parameters,
namespaces, types, methods, fields, properties, and constants. Methods and fields are further divided
into private vs non-private. Types are further divided into classes, structs, interfaces, enums, and delegates.
Constants are further divided into local constants, class constants, and enum members.
There are currently no options for renaming of events and there are no options for differential naming based on whether a member is static or not. Also, there are no current options for differential naming on more refined access categories (e.g., you can specify different naming for private vs non-private methods, but you cannot currently specify a different convention for internal methods vs public methods).
There are also options to remove existing Hungarian notation for locals & parameters, methods, properties, fields, class constants, and local constants. As an example, if you enter the prefix "str" for locals & parameters, then a local variable named "strMyString" will be first changed to "MyString" before further adjustments are made. You also have the option of adding a prefix for fields, class constants, and local constants.
There will usually be a few cases where you will need to adjust the utility's output by renaming an object manually. In general, this is more likely if you rely heavily on implicit typing (e.g., untyped lambda parameters). Also, certain C# constructs such as local functions, tuples, and unsafe code are not processed for renaming.
Q: What type of C# code is not included?
ASP.NET and razor pages are not included. Only actual C# code files are included in the renaming. Also, some constructs such as local functions, tuples, and unsafe code are not included. Due to the accelerating rate of changes in the C# language, please try newer features using the Free Edition before purchasing.
Copyright © 2004 – 2021 Tangible Software Solutions, Inc.