string.format

I need to print a string in a message box in specific format for which i am using code similar to as shown below: string text=""; for (int i=0; i<n; i++) { a=.. b=.. c=.. text += String.Format("{0, -8} {1,-4} {2,8}", a, b, c); } MessageBox.Show(text); So for following set of values: XYZ,ABC,100 X,ABC,100 I get following output: XYZ ABC 100 X ABC 100 So you can see the second line is not well formatted. Probably this is happening because i am printing this in MessageBox. The space a character and a 'space' takes is different. Any solution for this? Bob Black Try using a \t to insert tabs

This question already has answers here : Closed 10 years ago . Duplicate from : String output: format or concat in C#? Especially in C# world using String.Format for everything is really common, normally as VB.NET developer unless I have to* I don't String.Format, I prefer normal string concatenation, such as: V1 = V2 & "test-x" & V3 & "-;" to me it's better than this: V1 = String.Format("{0} test-x {1} -;", V2, V3) Am I missing something? Or is this just a personal preference? Reasons to Use String.Format (From The Answers) ( I'll try to keep this up to date ) Localization is so much easier

Given the following C# code: var dt = DateTime.Now; Console.WriteLine("{0:MM/dd/yy} ... {1}", dt, string.Format("{0:MM/dd/yy}", dt)); ... when the short date (under Windows 7, Control Panel -> Region and Language -> Additonal Settings -> Date ) is set to the USA standard of " M/d/yyyy ," I get this: 06/17/14 ... 06/17/14 However, when I change the short date to " ddd dd MMM yyyy ," I get this: 06/17/14 ... 06 17 14 I was under the impression that Console.WriteLine and string.Format always string formatted DateTime values identically. What is the explanation for this discrepancy? EDIT: Looks

I am using a DataBinder.Eval expression in an ASP.NET Datagrid, but I think this question applies to String formatting in .NET in general. The customer has requested that if the value of a string is 0, it should not be displayed. I have the following hack to accomplish this: <%# IIf(DataBinder.Eval(Container.DataItem, "MSDWhole").Trim = "0", "", DataBinder.Eval(Container.DataItem, "MSDWhole", "{0:N0}")) %> I would like to change the {0:N0} formatting expression so that I can eliminate the IIf statement, but can't find anything that works. You need to use the section separator , like this: <%#

How do I string.format() or sprintf() in coffeescript? Peter Lyons So there's 2 things going on here. First is interpolation, which coffeescript directly supports using double-quoted string literals and ruby style syntax like this: "The #{speed} #{color} #{animal} jumped over the lazy dog" That will replace the placeholders with the corresponding variables from the local scope. That's the idiomatic way to handle string interpolation in coffeescript (and ruby). Second is the formatting, which you should probably handle separately if you want to get numbers with specific decimal places,

Can anyone explain if there is any benefit in either one of the following methods: decimal d = 12.0m; // 1. how I'd have done it myLabel.Text = d.ToString(); // 2. how I saw someone do it today myLabel.Text = String.Format("{0}", d); Just to clarify, I'm not querying what the methods do, I'm obviously happy with that, just if there is perhaps a performance benefit in one over the other in this specific example. I'm aware of the added flexibility of cultures and formatting offered by string.format(), but I'd always just 'tostring()' numerics to attach their value to a label, or text based

This question is unlikely to help any future visitors; it is only relevant to a small geographic area, a specific moment in time, or an extraordinarily narrow situation that is not generally applicable to the worldwide audience of the internet. For help making this question more broadly applicable, visit the help center . The following code keep giving me error saying Input string was not in a correct format, but I am pretty sure it is right, isn't it? int id = 112; String[] newData = { "1", "2", "21", "reidb", "reidb", "reidb", "reidb", "aa", "Some description", "11", "2012-02-28", "2012-01