Practical coding tips, real solutions and career insights for software developers — straight to your inbox. No fluff.
No spam. Unsubscribe anytime. Privacy policy
Thanks for subscribing. First issue lands soon.
When it comes to iterating over collections in C#, the performance difference between foreach and for loops primarily depends on the collection type being traversed.
For arrays and Lists, a traditional for loop with indexing can be marginally faster because it avoids the overhead of creating an enumerator object, especially in performance-critical scenarios.
The foreach loop internally creates an IEnumerator, which adds a small memory allocation and method call overhead.
However, for most modern applications, this performance difference is negligible and often optimized away by the JIT compiler.
The readability benefits of foreach typically outweigh the minor performance gains of for loops in non-critical code paths.
Collections like LinkedList or those implementing only IEnumerable actually perform better with foreach since they don't support efficient random access.
The rule of thumb: use foreach for readability in most cases, and only switch to for loops when benchmarking shows a meaningful performance improvement in your specific high-performance scenarios.
Example
// Collection to iterate List<int> numbers = Enumerable.Range(1, 10000).ToList(); // Using for loop public void ForLoopExample(List<int> items) { int sum = 0; for (int i = 0; i < items.Count; i++) { sum += items[i]; } // For loop can be slightly faster for List<T> and arrays // because it avoids creating an enumerator } // Using foreach loop public void ForEachLoopExample(List<int> items) { int sum = 0; foreach (int item in items) { sum += item; } // More readable and works well for any collection type // Preferred for most scenarios where performance isn't critical } // For a LinkedList, foreach is typically faster public void LinkedListExample(LinkedList<int> linkedItems) { int sum = 0; // This would be inefficient with a for loop since LinkedList // doesn't support efficient indexing foreach (int item in linkedItems) { sum += item; } }
In C#, you can format an integer with commas (thousands separator) using ToString with a format specifier.
int number = 1234567; string formattedNumber = number.ToString("N0"); // "1,234,567" Console.WriteLine(formattedNumber);
Explanation:
"N0": The "N" format specifier stands for Number, and "0" means no decimal places. The output depends on the culture settings, so in regions where , is the decimal separator, you might get 1.234.567.
Alternative:
You can also specify culture explicitly if you need a specific format:
using System.Globalization; int number = 1234567; string formattedNumber = number.ToString("N0", CultureInfo.InvariantCulture); Console.WriteLine(formattedNumber); // "1,234,567"
When working with financial data in C#, proper currency formatting is essential for clear and professional presentation. The .NET framework provides several convenient methods to format numeric values as currency, with the most common being the ToString() method with the "C" format specifier.
For example, decimal amount = 1234.56m; string formatted = amount.ToString("C"); will display "$1,234.56" in US culture.
decimal amount = 1234.56m; string formatted = amount.ToString("C");
For more control over the formatting, you can specify a culture explicitly using CultureInfo - amount.ToString("C", new CultureInfo("fr-FR")) would display "1 234,56 €".
amount.ToString("C", new CultureInfo("fr-FR"))
This allows your application to handle different currency symbols, decimal separators, and grouping conventions appropriately.
If you need to handle multiple currencies or require more specialized formatting, you can also use the String.Format() method or string interpolation with custom format strings.
For instance, String.Format("{0:C}", amount) or $"{amount:C}" achieves the same result as ToString("C"). Additionally, you can control the number of decimal places using format strings like "C2" for two decimal places.
String.Format("{0:C}", amount)
$"{amount:C}"
Remember that when dealing with financial calculations, it's best practice to use the decimal type rather than float or double to avoid rounding errors that could impact currency calculations.
decimal price = 1234.56m; // Basic currency formatting Console.WriteLine(price.ToString("C")); // Output: $1,234.56 // Currency formatting with specific culture Console.WriteLine(price.ToString("C", new CultureInfo("de-DE"))); // Output: 1.234,56 € // Currency formatting with string interpolation Console.WriteLine($"{price:C}"); // Output: $1,234.56 // Controlling decimal places Console.WriteLine(price.ToString("C3")); // Output: $1,234.560
In C#, readonly, const, and static are keywords used to define variables with different behaviors in terms of mutability, memory allocation, and scope.
readonly
const
static
Understanding their differences is crucial for writing efficient and maintainable code. In this article we'll take a look at each and see how they are used.
A const variable is a compile-time constant, meaning its value must be assigned at declaration and cannot be changed later.
string
enum
public class MathConstants { public const double Pi = 3.14159; } // Usage: Console.WriteLine(MathConstants.Pi); // Output: 3.14159
⚠ Limitations:
A readonly field allows initialization either at declaration or in the constructor but cannot be modified afterward.
public class Circle { public readonly double Radius; public readonly double Pi = 3.14159; public Circle(double radius) { Radius = radius; // Allowed because it's inside the constructor. } } // Usage: Circle c = new Circle(5); Console.WriteLine(c.Radius); // Output: 5
✔ Best for: Values that should remain constant per instance but need to be assigned dynamically at runtime.
A static variable belongs to the type itself rather than to any instance of the class.
public class GlobalConfig { public static string ApplicationName = "MyApp"; public static readonly DateTime StartTime = DateTime.Now; } // Usage: Console.WriteLine(GlobalConfig.ApplicationName); // Output: MyApp
✔ Best for: Global state, caching, configuration values, and utility methods.
Choosing the Right One:
Understanding these differences helps you write cleaner, more efficient C# code. Happy coding! 🚀
Register for my free weekly newsletter.