http://blogs.msdn.com/b/brada/archive/2003/04/22/49997.aspx:

As David implies, there difference between String.Empty and "" are pretty small, but there is a difference. "" actually creates an object, it will likely be pulled out of the string intern pool, but still... while String.Empty creates no object... so if you are really looking for ultimately in memory efficiency, I suggest String.Empty. However, you should keep in mind the difference is so trival you will like never see it in your code... As for System.String.Empty or string.Empty or String.Empty... my care level is low ;-)

一个不同之处在于，如果使用切换大小写语法，就不能编写大小写字符串。空:因为它不是一个常数。您将得到一个编译错误:期望一个常量值

更多信息请看这个链接: string-empty-versus-empty-quotes

如果你想恶作剧某人，在他们的代码中加入“‍”。这不是空字符串，它是“\u200D”。你不能用string.Empty欺骗别人。

使用您和您的团队认为最易读的内容。

其他答案表明，每次使用""都会创建一个新的字符串。这是不正确的-由于字符串实习，它将在每个程序集或每个AppDomain创建一次(或可能在整个过程中创建一次-在这方面不确定)。这种差异可以忽略不计——非常非常微不足道。

然而，你觉得哪个更有可读性是另一回事。这是主观的，因人而异——所以我建议你找出你的团队中大多数人喜欢什么，然后保持一致。我个人觉得“”更容易读。

“”和“”很容易被误认为彼此的论点并不能真正让我接受。除非你使用的是比例字体(我从未与任何使用比例字体的开发人员合作过)，否则很容易看出区别。

I strongly prefer String.Empty, aside from the other reasons to ensure you know what it is and that you have not accidentally removed the contents, but primarily for internationalization. If I see a string in quotes then I always have to wonder whether that is new code and it should be put into a string table. So every time code gets changed/reviewed you need to look for "something in quotes" and yes you can filter out the empty strings but I tell people it is good practice to never put strings in quotes unless you know it won't get localized.

编译器应该让它们在长期运行时都是一样的。选择一个标准，这样你的代码就容易阅读，并坚持下去。