blocks|key|745883|text|如果您认为以后可能需要更复杂的getter或setter，自动属性语法使您无需重新编译所有调用方即可进行升级。然而，从字段(成员变量)移动到属性是一个突破性的变化。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|745884|Eric+Lippert+addresses+the+topic.+Twice.|offset|length|745885|entityMap|0|LINK|mutability|MUTABLE|url|http://blogs.msdn.com/b/ericlippert/archive/2009/01/14/automatic-vs-explicit-properties.aspx|1|http://blogs.msdn.com/b/ericlippert/archive/2009/01/16/future-proofing-a-design.aspx^0|0|0|X|0|Y|6|1|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@$D|R|E|S|1|T]|$D|U|E|V|1|W]]|A|$]]|$1|F|3|-4|5|6|7|X|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|M]]|N|$5|I|J|K|A|$L|O]]]]

If you think you might need a more complicated getter or setter later, the automatic property syntax lets you upgrade without recompiling all callers. Moving from a field (member variable) to a property is a breaking change, however.

<a href="http://blogs.msdn.com/b/ericlippert/archive/2009/01/14/automatic-vs-explicit-properties.aspx" rel="noreferrer">Eric Lippert addresses the topic.</a> <a href="http://blogs.msdn.com/b/ericlippert/archive/2009/01/16/future-proofing-a-design.aspx" rel="noreferrer">Twice.</a>

blocks|key|961845|text|public+int+i+{get+;+set;}|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|961846|创建int类型的自动属性i|unstyled|offset|length|style|CODE|961847|它的缩写是|961848|private+int+_i;
public+int+i
{
+++++get{+return+_i;}
+++++set{+_i+=+i}
}+|961849|entityMap^0|0|2|3|C|1|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$B|C]]|$1|D|3|E|5|F|7|R|8|@$G|S|H|T|I|J]|$G|U|H|V|I|J]]|9|@]|A|$]]|$1|K|3|L|5|F|7|W|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|X|8|@]|9|@]|A|$B|C]]|$1|O|3|-4|5|F|7|Y|8|@]|9|@]|A|$]]]|P|$]]

<pre><code>public int i {get ; set;}
</code></pre>

creates auto property <code>i</code> of type <code>int</code>

which is short for

<pre><code>private int _i;
public int i
{
 get{ return _i;}
 set{ _i = i}
} 
</code></pre>

blocks|key|961904|text|您所描述的语法称为auto属性。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|961905|在.NET+2.0引入该语法之前，我们创建了如下属性：|961906|int+_myVar;
int+MyVar
{
++++get+{+return+_myVar;+}
++++set+{+_myVar+=+value;+}
}|code-block|syntax|javascript|961907|.NET+2.0引入了简写语法，允许编译器自动创建支持变量(上面例子中的_myVar)|offset|length|style|CODE|961908|int+MyVar
{
++++get;
++++set;
}|961909|像这样设置变量和属性之间的关键区别在于，我们可以控制属性的获取和设置(例如，只读属性，或者在将值设置为属性时调用函数)。|961910|entityMap^0|0|0|0|10|6|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|V|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|W|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|X|8|@$K|Y|L|Z|M|N]]|9|@]|A|$]]|$1|O|3|P|5|F|7|10|8|@]|9|@]|A|$G|H]]|$1|Q|3|R|5|6|7|11|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|T|$]]

The syntax you are describing is known as an auto property.

Before the syntax was introduced in .NET 2.0, we created a property like so:

<pre><code>int _myVar;
int MyVar
{
 get { return _myVar; }
 set { _myVar = value; }
}
</code></pre>

.NET 2.0 introduced the shorthand syntax, allowing the compiler to automatically create the backing variable (<code>_myVar</code> in my example above)

<pre><code>int MyVar
{
 get;
 set;
}
</code></pre>

The key difference between setting a variable and a property such as this is that we can control the getting and setting of the property (read only properties, or a function call whenever a value is set to the property, for example.)

blocks|key|746193|text|它基本上是面向对象编程的概念。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|746194|当您使用int时；(此字段可视为字段，此字段可以是内部使用，也可以从当前类外部使用，具体取决于访问修饰符)。(公共、私有、受保护)|746195|现在，当你使用get；set时，它是class的属性。它也可以设置为与其他类不同，但它是类似于访问方法，它还提供了其他功能，如属性更改通知等等。|746196|当你不想对它进行任何控制时，使用filed，但如果你想控制它，那就使用属性。还可以将get和set与public、private和protected一起使用，这也可以提供更灵活的封装方式。|746197|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

It is basically concept of Object Oriented Programming.

when you use int i; ( This consider as field and this field can be internal usage as well as it can be use from outside current class depending upon access modifier. (Public , Private , Protected) 

Now when you use get; set; it is property of class. It can also set from other class but diffrence it is access like method and it provide other functionality like notification of property change and all that.

Use filed when you don't want any control over it but if you want to control then use property. Also you can have get and set with public , private and protected which can also 
provide more flexibility interm of encaptulation.

blocks|key|746314|text|让我们暂时忘掉属性...您真正要问的问题(您甚至可能不知道)是，为什么首先需要属性(或者其他语言中的getter和setter)？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|746315|这是为了推广encapsulation。|offset|length|746316|属性只是为getter和setter提供了更好的语法，也就是访问器(实际上，属性只是在幕后包装了set()和get()方法)。|746317|在c#+3中，c#团队提出了自动属性，因为大量的属性不会对变量做任何事情(没有额外的逻辑)，所以自动属性对于该场景来说是速记。|746318|entityMap|0|LINK|mutability|MUTABLE|url|http://en.wikipedia.org/wiki/Encapsulation_%2528object-oriented_programming%2529^0|0|6|D|0|0|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@$D|T|E|U|1|V]]|A|$]]|$1|F|3|G|5|6|7|W|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|X|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q]]]]

Lets forget properties for a second... The real question you're asking (and you might not even know it) is why do you need properties (or getters and setters in some other languages) in the first place?

It's to promote <a href="http://en.wikipedia.org/wiki/Encapsulation_%28object-oriented_programming%29">encapsulation</a>.

Properties just offer a nicer syntax for getters and setters, aka accessors (and indeed, a property just wraps set() and get() methods under the hood).

In c# 3 the c# team came up with auto properties, because the vast number of properties don't do anything with the variables (no additional logic), so auto properties are short hand for that scenario.

blocks|key|746391|text|基本上，它增加了开销，以换取附加事件的能力。除此之外，它还增加了复杂性和冗长，这使得代码更难阅读。如果您需要添加验证处理程序，这是一种很好的方法。在某些情况下。在大多数情况下，您知道(并且希望知道)变量(成员)正在被修改的确切位置。如果不这样做，那么您就会遇到代码管理问题，而不是语言问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|746392|认为一切“面向对象”都更好的想法是错误的。大多数开发人员正在逐渐理解这一点。我从事这项工作已经30年了，我可以告诉你，100次中有98次--简单是更好的。把你的编程精力花在不会增加不必要的复杂性的高效算法上，你会走得更远，并在趋势中生存下来。|746393|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Basically, it adds overhead in exchange for the ability to attach an event. Apart from that, it adds complexity and verbosity, which makes code more difficult to read. If you need to add validation handlers, it is a neat way to do it. In some cases. In most cases, you know (and want to know) exactly where a variable (member) is being modified. If you don't, then you have a code management problem, not a language issue.

The idea that everything "object oriented" is better, is false. Most developers are coming to understand that. I've been doing this work for 30 years, and I can tell you that 98 times out of 100 - simple is better. Spend your coding effort on efficient algorithms that don't add unnecessary complexity, and you will go far and survive trends.

I'm failing to understand what the difference is between initializing a variable, getting its value like this:

<pre><code> //define a local variable.
 int i;

 i= 0;
 Console.WriteLine(i);
</code></pre>

and the get; set; usage:

<pre><code>public int i
{
 get;
 set;
}

i = 0;
Console.WriteLine(i);
</code></pre>

I've read some articles, but don't understand when I would use it.

When to use get; set; in c#

编译器

我不明白初始化一个变量，像这样获取它的值有什么不同： //define a local variable.   int i;   i= 0;   Console.WriteLine(i);和get；set；用法：public int i{   get;   set;}i = 0;Console.WriteLine(i)...

问何时在c#中使用get；set；
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问何时在c#中使用get；set；EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问何时在c#中使用get；set；
EN