C#

Say you’re reviewing a pull request for a San Diego coffee roaster’s order system and you find clsOrder, order_helper, OrderBase and a class called Orders inside the Orders namespace. Quick answer: the C# class naming conventions are PascalCase nouns with no prefix, a suffix only when the base type asks for one, and I only … Read more >>

Interviewers love this one: turn “4815” into an int without calling int.Parse. To convert a string to int without Parse in C#, loop over the characters and build the number yourself: In this tutorial, I’ll write my own convert string to int without parse in C# routine, then add a sign, invalid-character checks and overflow … Read more >>

Picture a Portland outdoor store exporting 2,400 product titles for a new catalog. Every title ends with a color, like “Trail Runner Jacket Navy”, and the catalog wants only “Trail Runner Jacket”. That’s a textbook remove last word from string C# job, and the quickest answer is LastIndexOf(' ') plus a range slice up to … Read more >>

Most naming mistakes I fix in code reviews look like strCustName, n or tmp2. They compile, but they break the C# variable naming conventions, and the next reader has to guess what each one holds: Quick answer: name local variables and parameters in camelCase, spell words out, drop type prefixes, and save single letters for … Read more >>

Exported order data almost never comes out clean. To remove the last character from a string in C#, call s.Remove(s.Length – 1), or on C# 8 and later use the range operator s[..^1]. Both return a new string and leave the original alone. In this tutorial, I’ll answer the classic C# remove last character from … Read more >>

Our code reviews still catch MAX_CART_ITEMS in new C# code, usually from developers who came from Java, Python or C. Quick answer: the C# constant naming convention is PascalCase for every const, whether it’s public, private or local, with no underscore prefix: I tested this in a .NET 10 checkout for a Texas outdoor store, … Read more >>

The C# boolean naming convention is to name a bool like a yes/no question: start it with Is, Has, Can or Should, use camelCase for locals, PascalCase for properties and methods, and _camelCase for private fields: Every example below ran on .NET 10 in a checkout for Bayou Coffee Roasters, a made-up New Orleans coffee … Read more >>

A pull request for a Texas retailer’s order system hit my queue last week with custName, CUST_ID, and m_total in one class. That’s three naming conventions fighting inside 40 lines of C#. Here’s the quick answer. C# uses PascalCase for types, namespaces, methods, properties, events, and constants, camelCase for local variables and parameters, _camelCase for … Read more >>

This is the enum I flag most often in code reviews, and it breaks three C# enum naming conventions at once: an Enum suffix, ALL_CAPS members and the type name repeated inside every value. The fix is enum OrderStatus { Pending, Shipped, Delivered }: a singular PascalCase type with plain PascalCase members. Below are the … Read more >>

Most field bugs we catch in code review start with name = name; inside a constructor. It compiles with a warning, and the field stays empty, because the parameter hides the field. Quick answer: the C# field naming conventions are _camelCase for private and internal fields, s_ and t_ prefixes for static and thread-static fields, … Read more >>