blocks|key|1221484|text|没有区别，这些是.Net框架类型的C#中的类型别名，您在下面调用相同的方法。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1221485|例如：|1221486|1221487|int是System.Int32|unordered-list-item|offset|length|style|CODE|1221488|string的别名是System.String|1221489|的别名|1221490|You+can+find+a+complete+list+of+these+aliases+on+MSDN+here。|1221491|entityMap|0|LINK|mutability|MUTABLE|url|http://msdn.microsoft.com/en-us/library/ya5y69ds.aspx^0|0|0|0|0|3|4|C|0|0|6|A|D|0|0|0|1M|0|0^^$0|@$1|2|3|4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|10|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|11|8|@]|9|@]|A|$]]|$1|E|3|F|5|G|7|12|8|@$H|13|I|14|J|K]|$H|15|I|16|J|K]]|9|@]|A|$]]|$1|L|3|M|5|G|7|17|8|@$H|18|I|19|J|K]|$H|1A|I|1B|J|K]]|9|@]|A|$]]|$1|N|3|O|5|6|7|1C|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|1D|8|@]|9|@$H|1E|I|1F|1|1G]]|A|$]]|$1|R|3|-4|5|6|7|1H|8|@]|9|@]|A|$]]]|S|$T|$5|U|V|W|A|$X|Y]]]]

There's no difference, these are type aliases in C# for .Net framework types, you're calling the same method underneath.

For example:

<ul>
<li><code>int</code> is an alias for <code>System.Int32</code></li>
<li><code>string</code> is an alias for <code>System.String</code></li>
</ul>

<a href="http://msdn.microsoft.com/en-us/library/ya5y69ds.aspx" rel="noreferrer">You can find a complete list of these aliases on MSDN here</a>.

blocks|key|3404731|text|这些都不是相关的原始数据类型。它们只是C#中提供的速记。string别名System.String和int别名System.Int32。对int.MaxValue的调用就是对Int32.MaxValue的调用。C#只允许您以速记方式键入它，类似于您在另一种类似C的语言中键入的内容。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3404732|entityMap^0|S|6|10|D|1E|3|1J|C|1X|C|2F|E|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]|$9|M|A|N|B|C]|$9|O|A|P|B|C]|$9|Q|A|R|B|C]|$9|S|A|T|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|U|8|@]|D|@]|E|$]]]|G|$]]

Those are not related primitive data types. They are simply shorthands available in C#. <code>string</code> aliases <code>System.String</code> and <code>int</code> aliases <code>System.Int32</code>. Calls to <code>int.MaxValue</code> are calls to <code>Int32.MaxValue</code>. C# just allows you to type it in shorthand similar to what you would type if you were in another C-like language.

blocks|key|1968707|text|大多数答案大体都是这样的。但是，在某些情况下需要别名。在我的脑海中：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1968708|public+enum+MyEnum:Byte+{...}+//will+not+compile

public+enum+MyEnum:byte+{...}+//correct|code-block|syntax|javascript|1968709|还有其他几个地方你必须使用别名；除此之外，它主要是风格。以下两条规则被普遍接受，第一条规则可能比第二条规则更多：|1968710|1968711|对定义变量或成员类型(声明、参数、类型转换、泛型类型闭包)的所有用法使用别名(小写关键字)|unordered-list-item|1968712|对静态上下文中类型的所有用法(调用静态方法，如解析器或字符串操作方法，或调用静态属性，如MinValue/MaxValue).|1968713|+)使用类型名称(PascalCased类标识符|1968714|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|U|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|V|8|@]|9|@]|A|$]]|$1|J|3|K|5|L|7|W|8|@]|9|@]|A|$]]|$1|M|3|N|5|L|7|X|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|Y|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|R|$]]

Most of the answers have it in general. HOWEVER, there are some cases in which the alias is required. Off the top of my head:

<pre><code>public enum MyEnum:Byte {...} //will not compile

public enum MyEnum:byte {...} //correct
</code></pre>

There are a couple other places where you must use the alias; besides that, it's mostly style. The following two rules are generally accepted, perhaps the first more than the second:

<ul>
<li>Use the alias (lowercase keyword) for all usages of that define a variable or member type (declaration, parameters, casting, generic type closure)</li>
<li>Use the type name (PascalCased class identifier) for all usages of the type in static context (Calling static methods such as parsers or string manipulation methods, or static properties like MinValue/MaxValue).</li>
</ul>

blocks|key|1219257|text|它们是一样的。string和int分别是String和Int32的语法别名。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1219258|entityMap^0|7|6|E|3|K|6|R|5|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]|$9|M|A|N|B|C]|$9|O|A|P|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|Q|8|@]|D|@]|E|$]]]|G|$]]

They're identical. <code>string</code> and <code>int</code> are syntactic aliases for <code>String</code> and <code>Int32</code> respectively.

blocks|key|1963989|text|字符串不是原生类型，只是字符串的别名。它们是一回事。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1963990|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

string is not a primative type but simply an alias for String. They are the same thing.

blocks|key|3404790|text|请注意，如果进入集成开发环境并将鼠标悬停在string上，您将看到它是由System.String定义的|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3404791|这是一个“别名”。一件事是另一件事的速记。int是字节的别名，Byte是Int32的别名，Char是char的别名，依此类推。|3404792|entityMap^0|L|6|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|M|8|@]|D|@]|E|$]]|$1|H|3|-4|5|6|7|N|8|@]|D|@]|E|$]]]|I|$]]

Notice that if you go into your IDE and hover your mouse over <code>string</code>, you will see that it is defined by System.String

This is an "alias"... one thing is shorthand for another thing. int is an alias for Int32, byte is an alias for Byte, char is an alias for Char, and so on and so forth.

blocks|key|1968746|text|IDE本身就是它们互换性的一个有趣的证明。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1968747|开始输入List<String>+list+=+new，然后看看IntelliSense的建议：List<string>。它甚至不会为您提供List<String>作为其中一个选择。|offset|length|style|CODE|1968748|为了回答你问题的第二部分，这是一个观点问题，出于许多原因，我更喜欢int和string而不是大写：|1968749|1968750|明亮的蓝色更明确，如果你正在快速阅读代码，你不能把类名误认为其他东西|unordered-list-item|1968751|我越不需要敲SHIFT%2Bkey，我越快键入|1968752|IntelliSense将自动完成小写名称，即使你以大写开头，所以对我来说，在同一行中看到同一个类的大小写版本是不美观的，甚至在同一项目中|1968753|+int类型本质上非常简单。我不愿强迫我的眼睛将其与其名称中有一个大写字母和两个数字(即Int32)联系在一起；它使它看起来太具体了，没有明显的原因|1968754|1968755|我的一位同事说，特别使用Int32和String确保了与未来.NET更新的兼容性；我完全不同意任何人的说法。请证明我是错的！|1968756|entityMap^0|0|4|N|1C|C|1Y|C|0|X|3|11|6|0|0|0|0|0|1|3|18|5|0|0|C|5|I|6|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Z|8|@$D|10|E|11|F|G]|$D|12|E|13|F|G]|$D|14|E|15|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|16|8|@$D|17|E|18|F|G]|$D|19|E|1A|F|G]]|9|@]|A|$]]|$1|J|3|-4|5|6|7|1B|8|@]|9|@]|A|$]]|$1|K|3|L|5|M|7|1C|8|@]|9|@]|A|$]]|$1|N|3|O|5|M|7|1D|8|@]|9|@]|A|$]]|$1|P|3|Q|5|M|7|1E|8|@]|9|@]|A|$]]|$1|R|3|S|5|M|7|1F|8|@$D|1G|E|1H|F|G]|$D|1I|E|1J|F|G]]|9|@]|A|$]]|$1|T|3|-4|5|6|7|1K|8|@]|9|@]|A|$]]|$1|U|3|V|5|6|7|1L|8|@$D|1M|E|1N|F|G]|$D|1O|E|1P|F|G]]|9|@]|A|$]]|$1|W|3|-4|5|6|7|1Q|8|@]|9|@]|A|$]]]|X|$]]

A funny proof for their interchangeability is the IDE itself. 
Start typing <code>List&lt;String&gt; list = new</code> then look at IntelliSense's suggestion: <code>List&lt;string&gt;</code>. It won't even give you <code>List&lt;String&gt;</code> as one of the choices.

To answer the second part of your question, which is an opinion matter, I prefer <code>int</code> and <code>string</code> over upper-case for many reasons: 

<ul>
<li>The bright blue color is more definitive and if you're fast-reading code you cannot mistake the class name for something else </li>
<li>The lesser I need to hit SHIFT+key, the faster I type </li>
<li>IntelliSense will auto-complete the lower-case names, even if you start with uppercase, so to me it's aesthetically unpleasing to see upper- and lower-case versions of the same class in the same line, or even in the same project</li>
<li>The type <code>int</code> is very simple in nature, and I would hate to force my eyes to associate that with having an upper-case letter and two digits in its name (i.e. <code>Int32</code>); it makes it look too specific for no obvious reason </li>
</ul>

A colleague of mine said specifically using <code>Int32</code> and <code>String</code> ensures compatibility with future .NET updates; I disagree with whoever says that completely. Prove me wrong, please!

blocks|key|1964113|text|String.Format()需要“使用系统”，但string.Format()不需要。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1964114|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

String.Format() requires "using Systems;" but string.Format() doesn't.

As far as I can tell, any static member of a class like <code>String</code> or <code>Int32</code> can also be accessed from the related primitive data type. So, <code>String.Format</code> is the same as <code>string.Format</code>, and <code>Int32.MaxValue</code> is the same as <code>int.MaxValue</code>.

Is there a difference between these two forms? Is one preferred to the other? Even if they are identical, is one generally considered more readable?

Edit: Since they are identical, is one preferred from a human perspective? Would you rather see <code>String.Format</code> or <code>string.Format</code> when reading someone else's code?

What is the difference between String.Format and string.Format (and other static members of primitive data types)?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

据我所知，像String或Int32这样的类的任何静态成员也可以从相关的原始数据类型访问。因此，String.Format与string.Format相同，Int32.MaxValue与int.MaxValue相同。这两种形式之间有区别吗？其中一个比另一个好吗？即使它们是相同的，是否通常被认为更具可读性？编辑:既然它们是相同的，从人类的角度来看是首选的吗？在读取别人的代码时，您更愿意看到Strin

问String.Format和string.Format (以及原始数据类型的其他静态成员)之间的区别是什么？
EN

回答 8

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问String.Format和string.Format (以及原始数据类型的其他静态成员)之间的区别是什么？EN

回答 8

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问String.Format和string.Format (以及原始数据类型的其他静态成员)之间的区别是什么？
EN