public class Customer
{
//…properties
public string FullName{ get{ return String.Format(”{0} {1}”, FirstName, LastName; } }
}

string result = string.Join(”,”, customers.Select(c=>c.FullName).ToArray() );

Something like that, anyway. Or if you don’t like FulllName, would this work?

string result = string.Join(”,”, customers.Select(c=>String.Format(”{0} {1}”, c.FirstName, c.LastName ).ToArray() );

I also write an extension method for string to make String.Format more fluent. You can then do this:

string fullName = “{0} {1}”.QuickFormat(c.Forename, c.Surname);

@Steve: Missed the delimiter.Length, thank you.

I looked at string.Join, and the reason I shyed away from it was because of the ToArray. The ToArray is unlikely to cause problems, but it is slightly more direct in that a separate array does not have to be created.

Which, for the size of the data that I’m parsing, is probably being offset by the use of the StringBuilder.

This is what I get for posting something so quickly…but then again, it is a great way to learn/remember what is possible.

And I always use the string.Join method, first argument is your delimiter, second argument is a string array.
return string.Join(delimiter, list.Select(action).ToArray());

Func should really be Func<T, string>
And in case that didn’t work a Func that takes a T and returns a string.

I’m curious as to why do you use a custom delegate when you can use a Func? Also, is there a reason for action.Invoke(t) rather than action(t)?

Terry