C# Strings — Turkish 'i' Bug Breaks Logins
In Turkish culture, 'I' and 'i' are separate letters — default comparison fails logins.
20+ years shipping production .NET services in enterprise systems. Drawn from code that ran under real load.
- ✓Basic programming fundamentals
- ✓A computer with internet access
- ✓Willingness to follow along with examples
- A string is an immutable sequence of characters, implemented as System.String
- Immutability means every operation that looks like a change creates a new string
- Use string interpolation ($"") for readability — avoid raw concatenation
- StringBuilder is the performance tool for building strings in loops
- String comparison must use StringComparison enum to avoid culture-sensitive bugs
- Biggest mistake: using + inside loops creates O(n²) allocations
A C# string is a reference type that represents an immutable sequence of UTF-16 code units. Immutability means every operation that appears to modify a string — like concatenation, replacement, or trimming — actually allocates a new string object on the heap, leaving the original untouched.
This design exists primarily for thread safety and hash table performance: strings can be shared across threads without synchronization, and their hash codes are computed once and cached. The trade-off is that naive string manipulation in loops creates O(n²) allocations, which is why StringBuilder exists for high-frequency text construction.
In the .NET ecosystem, string is a language alias for System.String, and the two are identical at compile time — but the aliasing trap burns beginners who expect string to behave like a value type because of its lowercase syntax. Unlike Java or Python strings, C# strings are not null-terminated and can contain embedded null characters (\0).
They also support verbatim literals (@"...") for escaping-free paths and raw string literals (C# 11+) for multi-line text without escape sequences.
String comparison is where most production bugs live, including the infamous Turkish 'i' bug. The default == operator and string. use ordinal (culture-insensitive) comparison by default in modern .NET, but older code or explicit Equals()StringComparison.CurrentCulture can produce different results depending on the system locale.
The Turkish locale treats 'I' and 'i' differently from English — 'I' lowercases to 'ı' (dotless i) and 'i' uppercases to 'İ' (dotted I) — so a login system that normalizes usernames with ToLower() under the Turkish locale will silently corrupt credentials. The fix is always to use ordinal or invariant culture comparisons for programmatic identifiers like usernames, emails, or file paths.
Performance-wise, the runtime interns string literals automatically — identical literals in your source code share the same object reference. But strings created at runtime (e.g., from Console. or ReadLine()StringBuilder.) are not interned unless you explicitly call ToString()string., which can be a memory leak if overused.Intern()
For most applications, the default behavior is fine; the real performance wins come from avoiding + in loops, preferring StringBuilder for more than ~3-5 concatenations, and using string. or Create()string. with Concat()Span<T> for zero-allocation formatting in hot paths.
Imagine a string of beads on a necklace — each bead is a single letter or character, and the whole necklace is your string. In C#, a string is exactly that: a sequence of characters (letters, numbers, symbols, spaces) treated as one single unit. When your app shows the message 'Welcome, Sarah!' on screen, that entire sentence is a string. Strings are literally everywhere — usernames, error messages, URLs, file paths — if it's text, it's a string.
Every application that has ever existed talks to humans using text. Your banking app says 'Transfer successful.' Your favourite game says 'Player 1 wins.' Your email client says 'No messages found.' All of that is text, and text in C# lives inside strings. Before you can build anything meaningful, you need to understand how C# handles text — and it turns out C# has some very specific and powerful opinions about it.
The problem strings solve is simple: computers only understand numbers. Underneath the hood, the letter 'A' is just the number 65, and 'B' is 66. Strings give you a friendly, human-readable wrapper around all those numbers so you can write code that works with words and sentences naturally, without worrying about the raw numeric values underneath.
By the end of this article you'll know how to create strings, combine them, search inside them, change their content, compare them correctly, and avoid the classic traps that trip up beginners and even some experienced developers. You'll also walk away with a solid mental model of why strings in C# behave the way they do — and that 'why' is what separates developers who just copy code from developers who actually understand it.
What a String Actually Is in C# — and Why It's Immutable
In C#, a string is an object of the built-in System.String class. When you write string with a lowercase 's', it's just a convenient alias — C# quietly replaces it with System.String behind the scenes. Either spelling works; most C# developers use the lowercase version by convention.
Here's the most important thing to understand about strings right away: they are immutable. Immutable means once a string is created, it cannot be changed. Ever. If you think you're changing a string, you're actually creating a brand new string and throwing away the old one.
Think of it like a sticky note. Once you write on it, you can't erase and rewrite it — you have to throw it away and grab a fresh sticky note. This design choice makes strings safe to share across your program without worrying that one piece of code secretly modifies text that another piece depends on.
This immutability has a very real performance consequence we'll revisit in the gotchas section — it's one of the most common C# interview topics.
using System; class StringBasics { static void Main() { // Declaring a string with a literal value string greeting = "Hello, World!"; // string (lowercase) is just an alias for System.String // Both of these lines are identical in behaviour string firstName = "Alice"; System.String lastName = "Johnson"; // same type, different spelling // Strings can contain letters, numbers, symbols, even spaces string emailAddress = "alice.johnson@example.com"; string productCode = "ITEM-2024-XL"; // An empty string — valid and very common string emptyText = ""; // string.Empty is the recommended way to represent an empty string // It's more expressive and avoids any confusion with null string alsoEmpty = string.Empty; // Proving immutability — 'greeting' is not modified. // ToUpper() creates and returns a BRAND NEW string. // The original 'greeting' still holds "Hello, World!" string shoutedGreeting = greeting.ToUpper(); Console.WriteLine(greeting); // original — unchanged Console.WriteLine(shoutedGreeting); // new string Console.WriteLine(firstName + " " + lastName); Console.WriteLine(emailAddress); Console.WriteLine("Is emptyText empty? " + string.IsNullOrEmpty(emptyText)); } }
ToUpper(), Replace(), Trim() — actually returns a NEW string. Your original string is untouched. If you don't capture the return value, the change is lost forever. Always do: string result = original.ToUpper(); not just original.ToUpper();Trim().ToLower() creates two new strings but no garbage if the original is large.Creating and Combining Strings — Concatenation, Interpolation and Verbatim Strings
Once you have strings, you immediately need to combine them. Imagine building a personalised message like 'Good morning, Alice! You have 3 new notifications.' — that sentence is assembled from separate pieces of data. C# gives you several ways to do this, and each has its place.
The oldest way is concatenation using the + operator. It works, but it gets messy fast when you have more than two or three pieces.
String interpolation (using the $ prefix) is the modern, readable approach. You embed expressions directly inside curly braces {} inside the string. It reads almost like plain English and is the recommended approach in modern C# code.
Format strings using string. are older but still appear heavily in legacy codebases, so you need to recognise them.Format()
Verbatim strings (using the @ prefix) let you write strings exactly as they appear — including backslashes and multiple lines — without needing escape characters. They're invaluable for file paths and multi-line text.
Understanding which tool to reach for keeps your code readable and your colleagues happy.
using System; class StringCombining { static void Main() { string userName = "Alice"; int notificationCount = 3; double accountBalance = 1025.50; // --- METHOD 1: Concatenation with + --- // Works fine for simple cases, gets messy with many variables string welcomeMessage = "Good morning, " + userName + "! You have " + notificationCount + " new notifications."; Console.WriteLine(welcomeMessage); // --- METHOD 2: String Interpolation (RECOMMENDED for modern C#) --- // The $ prefix enables interpolation. Expressions go inside { } // You can put ANY valid C# expression inside the braces string interpolatedMessage = $"Good morning, {userName}! You have {notificationCount} new notifications."; Console.WriteLine(interpolatedMessage); // Interpolation also supports formatting specifiers after a colon // :C formats as currency, :F2 forces 2 decimal places string balanceMessage = $"Your balance is {accountBalance:C} as of today."; Console.WriteLine(balanceMessage); // You can even call methods inside the braces string upperCaseName = $"Username in capitals: {userName.ToUpper()}"; Console.WriteLine(upperCaseName); // --- METHOD 3: string.Format() — older style, still common in legacy code --- // {0}, {1} etc. are placeholders replaced by the arguments that follow string formattedMessage = string.Format("Hello, {0}. Your balance is {1:C}.", userName, accountBalance); Console.WriteLine(formattedMessage); // --- METHOD 4: Verbatim strings with @ --- // Without @, backslashes need escaping: "C:\\Users\\Alice\\Documents" // With @, you write it exactly as it looks — no escaping needed string filePath = @"C:\Users\Alice\Documents\report.pdf"; Console.WriteLine(filePath); // Verbatim strings also support multiple lines — the line breaks are included string multiLineAddress = @"123 Maple Street Springfield IL 62701"; Console.WriteLine(multiLineAddress); } }
Essential String Methods — Searching, Slicing and Transforming Text
A string sitting still isn't very useful. Real applications constantly need to inspect and reshape text: check if an email address contains '@', extract a username from a full name, remove accidental spaces from user input, replace offensive words, or check if a password meets minimum length requirements.
C# strings come loaded with built-in methods that handle all of these scenarios. You don't need to write complex loops — the heavy lifting is already done for you.
The most important methods to master are: Length (how many characters?), ToUpper() / ToLower() (change case), Trim() (remove whitespace from edges), Contains() (does this text exist inside?), StartsWith() / EndsWith() (checks at boundaries), IndexOf() (where does this text start?), Substring() (cut out a piece), Replace() (swap text for other text), and Split() (break a string into an array of pieces).
These ten methods will handle about 90% of the string manipulation you'll ever need in day-to-day development.
using System; class StringMethods { static void Main() { string userInput = " alice.johnson@example.com "; string productDescription = "The Red Bicycle is fast, reliable, and red."; string fullName = "Alice Johnson"; string csvLine = "London,Paris,Tokyo,Sydney"; // --- Length --- // Returns the number of characters (spaces count!) Console.WriteLine($"Raw input length: {userInput.Length}"); // includes the spaces // --- Trim --- // Removes leading and trailing whitespace — essential for cleaning user input string cleanEmail = userInput.Trim(); Console.WriteLine($"Cleaned email: '{cleanEmail}'"); Console.WriteLine($"Clean length: {cleanEmail.Length}"); // --- ToLower / ToUpper --- // Useful for case-insensitive comparisons or display formatting string normalizedEmail = cleanEmail.ToLower(); Console.WriteLine($"Normalised: {normalizedEmail}"); // --- Contains --- // Returns true or false — checks if a substring exists anywhere inside bool hasAtSymbol = cleanEmail.Contains("@"); Console.WriteLine($"Is it an email? {hasAtSymbol}"); // --- StartsWith / EndsWith --- bool isHttps = "https://thecodeforge.io".StartsWith("https"); bool isPdf = "report.pdf".EndsWith(".pdf"); Console.WriteLine($"Secure URL: {isHttps}, Is PDF: {isPdf}"); // --- IndexOf --- // Returns the ZERO-BASED position of the first match, or -1 if not found int atPosition = cleanEmail.IndexOf("@"); Console.WriteLine($"'@' is at index: {atPosition}"); // --- Substring --- // Substring(startIndex) extracts from startIndex to the end // Substring(startIndex, length) extracts exactly 'length' characters string domainPart = cleanEmail.Substring(atPosition + 1); // everything after @ Console.WriteLine($"Domain: {domainPart}"); string extractedFirstName = fullName.Substring(0, 5); // first 5 chars Console.WriteLine($"First name extracted: {extractedFirstName}"); // --- Replace --- // Replaces ALL occurrences, not just the first one string correctedDescription = productDescription.Replace("red", "blue"); Console.WriteLine(correctedDescription); // --- Split --- // Breaks a string into an array at every occurrence of the separator string[] cities = csvLine.Split(','); Console.WriteLine($"Number of cities: {cities.Length}"); foreach (string city in cities) { Console.WriteLine($" City: {city}"); } } }
IndexOf() returns -1 when the text isn't found — not zero. Zero means it was found at the very beginning of the string. Always check for -1 before using the result in a Substring() call, or you'll get an ArgumentOutOfRangeException at runtime. Pattern: int pos = text.IndexOf("@"); if (pos >= 0) { / safe to use pos / }Contains(), StartsWith(), EndsWith() use Ordinal comparison by default in .NET 5+ — but in older frameworks they used CurrentCulture. This caused behavior changes on upgrade.Split() with ',' does not trim each element — leading/trailing spaces remain. Use StringSplitOptions.TrimEntries in .NET 5+.Comparing Strings Correctly and Building Strings Efficiently with StringBuilder
String comparison sounds trivial — just use ==, right? In C# it's mostly safe for simple cases, but the moment you deal with user input, data from APIs, or mixed-case text, naive comparison breaks down. 'Alice' and 'alice' are the same username but == says they're different.
The correct tool is string. with a Equals()StringComparison option, or string.. These let you explicitly say whether case matters and whether to use the current culture's rules or a stable, predictable ordinal comparison.Compare()
Now for performance: remember how strings are immutable? Every time you use + to build a string inside a loop, you're creating and discarding a new string object on every single iteration. If you're building a 10,000-row report by appending line by line, that's 10,000 string objects created and thrown away. That's a serious memory and speed problem.
StringBuilder from System.Text solves this exactly. It's like a mutable notepad — you keep writing on the same object, and only convert it to a final string at the very end. For any string built in a loop, always use StringBuilder.
using System; using System.Text; // Required for StringBuilder class StringComparisonAndBuilder { static void Main() { // ===================================================== // PART 1: String Comparison Done Right // ===================================================== string storedUsername = "Alice"; string inputFromUser = "alice"; // user typed lowercase // Naive comparison — WRONG for usernames (case-sensitive) bool naiveMatch = (storedUsername == inputFromUser); Console.WriteLine($"Naive == comparison: {naiveMatch}"); // False — incorrect! // Correct comparison — OrdinalIgnoreCase ignores casing // Use this for usernames, file names, command inputs bool correctMatch = string.Equals(storedUsername, inputFromUser, StringComparison.OrdinalIgnoreCase); Console.WriteLine($"OrdinalIgnoreCase comparison: {correctMatch}"); // True — correct! // For text displayed to users (like sorting a list of names) // use CurrentCultureIgnoreCase — it respects locale rules bool cultureMatch = string.Equals(storedUsername, inputFromUser, StringComparison.CurrentCultureIgnoreCase); Console.WriteLine($"CurrentCultureIgnoreCase comparison: {cultureMatch}"); // Null-safe check: always handle null before comparing string possiblyNullInput = null; bool isSafe = string.Equals(storedUsername, possiblyNullInput, StringComparison.OrdinalIgnoreCase); Console.WriteLine($"Null-safe comparison result: {isSafe}"); // False, no crash Console.WriteLine(); // ===================================================== // PART 2: Building Strings Efficiently with StringBuilder // ===================================================== int reportRowCount = 5; // imagine this is 10,000 in production // BAD approach — creates a new string on every + in the loop // Do NOT do this in loops with many iterations string badReport = "Sales Report\n"; for (int rowNumber = 1; rowNumber <= reportRowCount; rowNumber++) { badReport += $"Row {rowNumber}: ${ rowNumber * 100}.00\n"; // new string each time! } Console.WriteLine("--- Bad Report (illustrative only) ---"); Console.Write(badReport); Console.WriteLine(); // GOOD approach — StringBuilder mutates ONE internal buffer // Only call .ToString() once at the very end StringBuilder reportBuilder = new StringBuilder(); reportBuilder.AppendLine("Sales Report"); // AppendLine adds text + newline for (int rowNumber = 1; rowNumber <= reportRowCount; rowNumber++) { // Append builds up the content without creating intermediate strings reportBuilder.AppendLine($"Row {rowNumber}: ${rowNumber * 100}.00"); } // Convert to a real string exactly once string efficientReport = reportBuilder.ToString(); Console.WriteLine("--- Efficient Report ---"); Console.Write(efficientReport); // StringBuilder also supports Insert, Remove and Replace reportBuilder.Insert(0, "=== CONFIDENTIAL ===\n"); Console.WriteLine("First 30 chars after Insert: " + reportBuilder.ToString().Substring(0, 20) + "..."); } }
ToString(). Use string for simple, fixed text. Use StringBuilder when building text across multiple operations, especially inside loops.String Pooling, Interning, and Performance Trade-offs
C# has an internal string pool — a hash table of unique string literals. When you write string hello = "Hello"; and later string greet = "Hello";, both variables point to the same object in memory. The runtime interning reduces memory for duplicate literals.
But there's a gotcha: strings created at runtime (e.g., from JSON, user input, or concatenation) are NOT automatically interned. They live on the heap as separate objects, even if the content is identical. You can explicitly intern them with string., but that's rarely worth it — interning adds lifetime to the pool and can increase memory if you intern many unique strings.Intern()
Another key performance detail: string.Empty vs "". They are equivalent at runtime (both point to the same interned empty string), but using string.Empty is more readable and signals intent. However, in hot loops, string.Empty is a static field access, while "" is a literal — the difference is negligible, but the compiler optimizes both.
Finally, consider StringComparer for dictionary keys: if you have a Dictionary<string, int> and need case-insensitive keys, pass StringComparer.OrdinalIgnoreCase to the constructor. This avoids calls to ToLower on every lookup.
using System; using System.Collections.Generic; class StringPoolAndPerformance { static void Main() { // === String interning demo === string literal1 = "thecodeforge"; string literal2 = "thecodeforge"; Console.WriteLine(Object.ReferenceEquals(literal1, literal2)); // True — same interned object // Runtime strings are NOT interned automatically string runtime1 = new string(new char[] { 't', 'h', 'e', 'c', 'o', 'd', 'e', 'f', 'o', 'r', 'g', 'e' }); string runtime2 = new string(new char[] { 't', 'h', 'e', 'c', 'o', 'd', 'e', 'f', 'o', 'r', 'g', 'e' }); Console.WriteLine(Object.ReferenceEquals(runtime1, runtime2)); // False — different objects Console.WriteLine(runtime1 == runtime2); // True — content equality // Explicit interning string interned = string.Intern(runtime1); Console.WriteLine(Object.ReferenceEquals(interned, literal1)); // True — now in pool // === Case-insensitive dictionary with StringComparer === var dict = new Dictionary<string, int>(StringComparer.OrdinalIgnoreCase); dict.Add("USA", 1); Console.WriteLine(dict.ContainsKey("usa")); // True without conversion } }
Intern(). For most apps, it's not worth it — rely on the built-in literal pooling.Intern() each one as you read.ToLower().string vs. System.String — The Aliasing Trap That Burns Beginners
Every C# dev knows string is an alias for System.String. Few understand why that distinction matters at 3 AM when a legacy codebase throws a NullReferenceException. Here's the deal: string works without using System;. String doesn't. That alone makes string the production-safe choice.
But the real gotcha? string? declares a nullable reference type. String? does the same, but only if you've enabled nullable reference types. Mixed codebases? You'll see String pop up in auto-generated files or old-school BCL examples. Treat them as identical in runtime behavior—they compile to the same IL. The difference is purely syntactic sugar.
When you see System.String.Copy() or System.String.Intern() in a code review, that's fine. But write string in your own code. It's idiomatic, consistent, and signals you understand the type system. One less argument at code review.
// io.thecodeforge — csharp tutorial using System; class StringDemo { static void Main() { // Both compile to identical IL string orderId = "ORD-2024-01"; System.String customerName = "Acme Corp"; // Nullable reference type (requires #nullable enable) string? discountCode = null; Console.WriteLine($"Order: {orderId}, Customer: {customerName}"); Console.WriteLine($"Discount: {discountCode ?? "none"}"); } }
string over String in method signatures and local variables. Only use System.String when you need to avoid ambiguity in reflection or fully qualified names in generated code.string for everyday code; never assume String works without using System;. They're the same IL, but string is the idiomatic alias.Quoted, Verbatim, and Raw String Literals — Stop Escaping Like It's 2005
String literals in C# come in three flavors, and picking the wrong one is how you end up with a regex that looks like a cat walked across your keyboard. Quoted literals use backslash escapes: "c:\\Program Files\\App". Verbatim literals (@"...") ignore escapes except for double quotes (""), so paths become readable: @"c:\Program Files\App".
Raw string literals (C# 11+) are the real game changer. They handle multi-line text, embedded quotes, and JSON without screaming. Use three or more double quotes """. The compiler aligns indentation based on the closing delimiter. Perfect for SQL queries, JSON payloads, or any string where backslashes would make you cry.
Never use quoted literals for file paths or Windows directory strings. That's amateur hour. Verbatim strings handle paths cleanly. Raw strings handle everything else. Pick the tool that minimizes character count and maximizes readability.
// io.thecodeforge — csharp tutorial using System; class LiteralDemo { static void Main() { // Quoted: backslash escapes required string quotedPath = "c:\\Users\\Admin\\Documents\\report.pdf"; // Verbatim: no backslash escaping, just double quotes for quotes string verbatimPath = @"c: Users\Admin\Documents\report.pdf"; // Raw (C# 11+): handles JSON, SQL, multi-line string rawJson = """ { "userId": 1001, "role": "admin" } """; Console.WriteLine(quotedPath); Console.WriteLine(verbatimPath); Console.WriteLine(rawJson); } }
String Interpolation and Composite Formatting — The Performance Killer Nobody Talks About
Everyone loves string interpolation: $"Hello, {name}!". It's clean, concise, and readable. But every interpolated string compiles to a string. call under the hood—unless you're using C# 10+ with Format()String.Concat optimizations for simple cases. That means boxing, culture-dependent formatting, and allocation overhead.
Composite formatting (string.Format("Hello, {0}!", name)) predates interpolation. It's more verbose, but gives you explicit control over culture and formatting specifiers. When you're logging millions of rows or building report lines in a tight loop, the difference matters.
Here's the rule: use interpolation for UI strings and developer-facing output. Use composite formatting with CultureInfo.InvariantCulture for log messages, data serialization, and any string that crosses machine boundaries. And never, ever use $ in a loop where performance counts—pre-allocate the format template and call string.Format once.
// io.thecodeforge — csharp tutorial using System; using System.Globalization; class FormatDemo { static void Main() { double revenue = 1234567.89; string region = "DE"; // Interpolation: clean, but cultures depend on current thread string userFriendly = $"Revenue for {region}: {revenue:C}"; // Composite formatting with invariant culture string machineReadable = string.Format( CultureInfo.InvariantCulture, "Revenue for {0}: {1:F2}", region, revenue); Console.WriteLine(userFriendly); // Depends on thread culture Console.WriteLine(machineReadable); // Always invariant } }
InvariantCulture for logs, serialization, and any cross-boundary output.Substrings in C# — Substring(), AsSpan(), and When the Difference Is 10x Performance
Substrings are everywhere—parsing logs, extracting tokens, slicing user input. The default reflex is Substring(), and it works fine for small tasks. But here's the dirty secret: every call to Substring() allocates a brand new string on the heap. For hot paths—think JSON parsers, CSV processors, or tight loops processing thousands of entries—that allocation tax adds up fast. Enter AsSpan(). It returns a ReadOnlySpan<char> that points into the original string's memory, zero allocation. The performance difference? An order of magnitude faster in benchmarks. No copy, no GC pressure, just a lightweight view. Use Substring() when you actually need a new string (e.g., to pass to legacy APIs), and AsSpan() when you're reading or iterating. The Slice() method on spans replaces index-based manual math with clear, efficient slicing. Stop allocating memory just to read a few characters.
// io.thecodeforge — csharp tutorial string data = "2025-04-10;ERROR;DB timeout"; // Allocating — creates new string string date = data.Substring(0, 10); // Allocation-free — zero heap pressure ReadOnlySpan<char> span = data.AsSpan(); ReadOnlySpan<char> dateSpan = span.Slice(0, 10); // For iteration or comparison, use span directly if (dateSpan.SequenceEqual("2025-04-10")) Console.WriteLine("Date match, zero allocation");
ReadOnlySpan<char> back to string via new string(span) re-allocates. Only do this when you truly need a string object (e.g., dictionary keys).AsSpan() + Slice() over Substring() in hot paths—zero allocations, 10x faster.Accessing Individual Characters — Indexer, Span, and the Allocation Trap
Need a single character from a string? The indexer s[5] returns a char in O(1) time—no allocation, no fuss. So why does this topic deserve a warning? Because the moment you do anything with that character—convert it, pass it to a method expecting string, or concatenate it—you silently trigger allocations. The trap: s[5]. allocates a new string. Building a new string by iterating characters with ToString()+=? That's O(n²) allocations. Use StringBuilder or, better yet, a char[] buffer. For zero-allocation character access, AsSpan() gives you the same indexer but on a ReadOnlySpan<char>, which works with stackalloc buffers and avoids heap allocations entirely. When you need to transform characters (uppercase, filter, replace), operate on spans rather than creating new string intermediate versions. The golden rule: read with the indexer, process with spans, and allocate only when you must persist the result.
// io.thecodeforge — csharp tutorial string s = "hello"; // Fast — no allocation char ch = s[1]; // Hidden allocation — ToString() creates a new string string trap = s[1].ToString(); // Zero-allocation: use span ReadOnlySpan<char> span = s.AsSpan(); char ch2 = span[1]; // Transform without allocation Span<char> buffer = stackalloc char[s.Length]; s.AsSpan().CopyTo(buffer); for (int i = 0; i < buffer.Length; i++) if (buffer[i] == 'l') buffer[i] = 'L';
s[i].ToString() or char.ToUpper(s[i]) in a loop allocates per iteration. Collecting them into a string via += is quadratic. Use StringBuilder or span-based mutation.ToString() on a single char is not. Read with indexer, process with spans, allocate only when storing.String Interpolation Advancements in C# 12/13
C# 12 introduced a major enhancement to string interpolation with the $ and $$ syntax, allowing you to control the number of braces used for interpolation. This is particularly useful when embedding JSON or other brace-heavy content. In traditional $ interpolation, a single {expression} is used. With $$, you use double braces {{expression}} to avoid escaping issues. For example:
```csharp string name = "Alice"; int age = 30;
// Standard $ interpolation string json = $"{{\"name\": \"{name}\", \"age\": {age}}}"; Console.WriteLine(json); // {"name": "Alice", "age": 30}
// $$ interpolation (C# 12+) string json2 = $$"""{"name": "{{name}}", "age": {{age}}}"""; Console.WriteLine(json2); // {"name": "Alice", "age": 30} ```
In C# 13, further refinements allow for more complex expressions and better performance. The $$ syntax is especially beneficial when combined with raw string literals ("""), as shown above, eliminating the need for escape sequences entirely. This advancement reduces errors and improves readability in code that generates structured text like JSON, XML, or configuration files.
string name = "Alice"; int age = 30; // Standard $ interpolation string json = $"{{\"name\": \"{name}\", \"age\": {age}}}"; Console.WriteLine(json); // {"name": "Alice", "age": 30} // $$ interpolation (C# 12+) string json2 = $$"""{"name": "{{name}}", "age": {{age}}}"""; Console.WriteLine(json2); // {"name": "Alice", "age": 30}
$$ interpolation with raw strings for generating structured data like JSON to minimize escaping bugs and improve code maintainability.$$ interpolation syntax reduces escaping when embedding expressions in brace-heavy content, especially when paired with raw string literals.StringBuilder vs String.Create vs String.Concat Performance Comparison
When building strings dynamically, performance varies significantly between StringBuilder, String.Create, and String.Concat. String.Concat is optimized for a small number of concatenations (up to ~10) and internally uses String.AllocateFast for zero-allocation in some cases. StringBuilder is ideal for many concatenations (e.g., loops) as it uses a mutable buffer, reducing allocations. String.Create (introduced in .NET Core 2.1) allows you to fill a pre-allocated string buffer directly, offering the best performance when you know the final length and can write characters sequentially.
Example benchmark (simplified):
```csharp using System.Diagnostics;
string[] parts = Enumerable.Range(0, 1000).Select(i => i.ToString()).ToArray();
// String.Concat var sw = Stopwatch.StartNew(); string result1 = string.Concat(parts); sw.Stop(); Console.WriteLine($"Concat: {sw.ElapsedTicks} ticks");
// StringBuilder sw.Restart(); var sb = new StringBuilder(); foreach (var part in parts) sb.Append(part); string result2 = sb.ToString(); sw.Stop(); Console.WriteLine($"StringBuilder: {sw.ElapsedTicks} ticks");
// String.Create sw.Restart(); int totalLength = parts.Sum(p => p.Length); string result3 = string.Create(totalLength, parts, (span, state) => { int pos = 0; foreach (var part in state) { part.AsSpan().CopyTo(span.Slice(pos)); pos += part.Length; } }); sw.Stop(); Console.WriteLine($"String.Create: {sw.ElapsedTicks} ticks"); ```
Typical results: String.Create is fastest, followed by StringBuilder for many parts, and String.Concat for few parts. Choose based on your scenario: use String.Concat for a handful of strings, StringBuilder for loops, and String.Create for maximum performance when you know the exact length.
using System.Diagnostics; string[] parts = Enumerable.Range(0, 1000).Select(i => i.ToString()).ToArray(); // String.Concat var sw = Stopwatch.StartNew(); string result1 = string.Concat(parts); sw.Stop(); Console.WriteLine($"Concat: {sw.ElapsedTicks} ticks"); // StringBuilder sw.Restart(); var sb = new StringBuilder(); foreach (var part in parts) sb.Append(part); string result2 = sb.ToString(); sw.Stop(); Console.WriteLine($"StringBuilder: {sw.ElapsedTicks} ticks"); // String.Create sw.Restart(); int totalLength = parts.Sum(p => p.Length); string result3 = string.Create(totalLength, parts, (span, state) => { int pos = 0; foreach (var part in state) { part.AsSpan().CopyTo(span.Slice(pos)); pos += part.Length; } }); sw.Stop(); Console.WriteLine($"String.Create: {sw.ElapsedTicks} ticks");
Raw String Literals in C# 11+
C# 11 introduced raw string literals using triple quotes ("""), allowing you to embed multi-line strings, JSON, XML, or any text without escaping. The syntax """...""" preserves whitespace and line breaks exactly as written. You can also combine raw strings with interpolation using $ or $$.
Example for JSON:
``csharp string json = """ { "name": "Alice", "age": 30, "city": "New York" } """; Console.WriteLine(json); ``
For XML:
``csharp string xml = """ <person> <name>Alice</name> <age>30</age> </person> """; Console.WriteLine(xml); ``
Raw string literals eliminate the need for escape sequences like \" or , making code more readable and less error-prone. They are especially useful for configuration files, SQL queries, and any embedded text. Note that the opening """ must be followed by a newline, and the closing """ must be on its own line (or at the end of the content). Indentation is determined by the closing """ position.
// JSON with raw string literal string json = """ { "name": "Alice", "age": 30, "city": "New York" } """; Console.WriteLine(json); // XML with raw string literal string xml = """ <person> <name>Alice</name> <age>30</age> </person> """; Console.WriteLine(xml);
""") in C# 11+ allow embedding multi-line text like JSON and XML without escaping, improving readability.Login Failure Due to Turkish 'i' — Culture-Sensitive Comparison
- Always specify StringComparison explicitly for any comparison involving user input or identifiers.
- Default culture-sensitive comparison is for user-facing text sorting, not for programmatic identifiers.
- Use OrdinalIgnoreCase for usernames, file paths, and any internal tokens.
(int)userInput[0] to see raw char codestring.Equals(a, b, StringComparison.Ordinal)int idx = data.IndexOf("pattern"); if (idx <= -1) throw;string? safe = data?.Substring(0, Math.Min(5, data.Length));new StringBuilder(capacity)dotnet-counters monitor --counters System.Runtimetext.Normalize(NormalizationForm.FormC)Regex.Replace(text, @"\p{C}", "") strips control chars| Feature / Aspect | string | StringBuilder |
|---|---|---|
| Mutability | Immutable — every change creates a new object | Mutable — modifies the same internal buffer |
| Memory usage in loops | High — discards and recreates on every operation | Low — reuses a single buffer throughout |
| Performance for many appends | Slow — O(n²) for n concatenations in a loop | Fast — amortised O(n) for n appends |
| Syntax convenience | High — clean literals, interpolation, all methods | Medium — uses Append/AppendLine/Insert/Remove |
| Thread safety | Safe to share — immutability prevents race conditions | Not thread-safe by default |
| Best use case | Fixed text, single expressions, method returns | Building reports, generating HTML, CSV, SQL |
| File | Command / Code | Purpose |
|---|---|---|
| StringBasics.cs | using System; | What a String Actually Is in C# |
| StringCombining.cs | using System; | Creating and Combining Strings |
| StringMethods.cs | using System; | Essential String Methods |
| StringComparisonAndBuilder.cs | using System; | Comparing Strings Correctly and Building Strings Efficiently |
| StringPoolAndPerformance.cs | using System; | String Pooling, Interning, and Performance Trade-offs |
| StringVsSystemString.cs | using System; | string vs. System.String |
| StringLiteralComparison.cs | using System; | Quoted, Verbatim, and Raw String Literals |
| FormatPerformanceDemo.cs | using System; | String Interpolation and Composite Formatting |
| Example.cs | string data = "2025-04-10;ERROR;DB timeout"; | Substrings in C# |
| Example.cs | string s = "hello"; | Accessing Individual Characters |
| interpolation-advancements.cs | string name = "Alice"; | String Interpolation Advancements in C# 12/13 |
| stringbuilder-vs-create-vs-concat.cs | using System.Diagnostics; | StringBuilder vs String.Create vs String.Concat Performance |
| raw-string-literals.cs | string json = """ | Raw String Literals in C# 11+ |
Key takeaways
ToLower()Interview Questions on This Topic
Why are strings in C# immutable, and what are the practical implications?
What is the difference between String.Empty and ""? Are they interchangeable?
Explain the different StringComparison values and when to use each.
How does StringBuilder avoid the performance problem of string concatenation?
ToString(). In contrast, string concatenation creates a new string object for every + operation, leading to O(n²) allocations for n concatenations. StringBuilder gives amortized O(n) time and uses less memory.What is string interning, and when should you use string.Intern()?
Intern() places them in the pool, reducing memory if many identical strings exist. However, interned strings are never garbage collected, so interning many unique strings can increase memory. Use only when you have a limited set of frequently repeated runtime strings.Frequently Asked Questions
Despite behaving like a value type in some ways (equality by content), string is a reference type. It inherits from object. The CLR treats it specially: it's immutable and has value-like equality semantics. But its memory is on the heap, and assignments copy references.
The == operator for strings calls string.Equals internally with Ordinal comparison. So there is no difference in behavior for most cases. However, for other reference types, == checks reference equality. For strings it's safe to use ==, but Equals is more explicit and allows passing StringComparison.
Use string.IsNullOrEmpty(str) or string.IsNullOrWhiteSpace(str) if you also want to treat whitespace as empty. They return a bool and are null-safe.
string.Format uses a StringBuilder internally, so it's efficient for moderate formatting. However, the parsing of the format string itself has overhead. For simple concatenation, interpolation is clearer and equally efficient.
The theoretical maximum is 2^31 - 1 characters (about 2.1 billion), because the Length property is an int. However, in practice, memory limits and performance degrade well before that. You'll likely hit an OutOfMemoryException before reaching the limit.
20+ years shipping production .NET services in enterprise systems. Drawn from code that ran under real load.
That's C# Basics. Mark it forged?
9 min read · try the examples if you haven't