blocks|key|4363711|text|我个人希望这是一个bug。在这一点上，我们只能猜测团队为什么改变了行为。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4363712|然而，一般来说，在默认情况下实现“失败”代码有一个很好的理由:作为开发人员，您必须故意决定如何实现这段代码。如果一个方法的默认实现只返回default(T)，该怎么办？代码将“工作”，直到有人注意到“未实现”的代码。|offset|length|style|CODE|4363713|但我认为，对于属性，您现在通常可以说，自动实现的属性是一条可行的道路。在99%25的情况下，默认实现是正确的，这与上面对方法的推理相反。|4363714|entityMap^0|0|1W|A|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@$D|N|E|O|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

I personally hope this is a bug. At this point we can only guess why the team changed the behavior.

However, generally speaking, there is a good reason to implement 'failing' code by default: you, as a developer, has to deliberately make a decision on how to implement that piece of code. What if the default implementation of a method would just return <code>default(T)</code>? The code will 'work' until someone notices the 'not implemented' code.

I would argue though that for properties you generally can say nowadays that auto-implemented properties are the way to go. In 99% of the occurrences, the default implementation is the correct one, in contrary to the above reasoning for methods.

blocks|key|4364232|text|看起来他们只是缩短了接口属性的默认实现。在2017年之前的版本中，接口属性默认是这样实现的：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4364233|++++public+string+City
++++{
++++++++get
++++++++{
++++++++++++throw+new+NotImplementedException();
++++++++}

++++++++set
++++++++{
++++++++++++throw+new+NotImplementedException();
++++++++}
++++}|code-block|syntax|javascript|4364234|我一直认为这是对屏幕空间的浪费。就我个人而言，我不太喜欢这两种方法，但是用NotImplementedExceptions来清除接口实现是有意义的，这样可以迫使您实际使用它们做一些事情。|4364235|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

Looks like they just shortened the default implementation of interface properties. In versions prior to 2017, interface properties were implemented like this by default:

<pre><code> public string City
 {
 get
 {
 throw new NotImplementedException();
 }

 set
 {
 throw new NotImplementedException();
 }
 }
</code></pre>

Which I've always thought was a waste of screen real estate. Personally I'm not that fond of either method, but it makes sense to stub out interface implementations with NotImplementedExceptions to force you to actually do something with them.

blocks|key|4363824|text|自动生成的代码是测试驱动开发(TDD)方法的一部分。方法论规定--先使单元测试失败，然后再编写代码来修复问题。它是在测试和编码的循环中进行的。有了这些循环，任务就完成了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4363825|它也适用于那些遵循敏捷方法并频繁添加和部署功能的应用程序。几乎没有什么东西可以在开发中，其他相关的稳定组件将投入生产。正在进行的方法或属性使用未实现的标记进行标记。|4363826|[TestClass]+
public+class+UnitComp1+
{+
++++[TestMethod]+
++++public+void+SalaryCalculationTest()+
++++{+
++++++++Payroll+pr+=+new+Payroll();+
++++++++Assert.IsTrue(da.IsValidGrossAmount(2000),+"Invalid+gross+amount");+
++++}+
}+

//Cycle+1+-+Test+fails
public+class+Payroll
{
+++public+bool+IsValidGrossAmount(int+amount)
+++{
+++++throw+new+NotImplementedException();
+++}
}

//Cycle+2+-+Test+passes+(done)
public+class+Payroll
{
+++public+bool+IsValidGrossAmount(int+amount)
+++{
+++++return+amount+>+1000;
+++}
}|code-block|syntax|javascript|4363827|Check+out+more,+here|offset|length|4363828|entityMap|0|LINK|mutability|MUTABLE|url|https://www.apnastudy.com/publicforumdetails/AVuC8FjM84he5u4soIOC/what-is-purpose-of-auto-generating-notimplemented-exception-stub-in-c^0|0|0|0|0|K|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|@]|9|@$K|Y|L|Z|1|10]]|A|$]]|$1|M|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|N|$O|$5|P|Q|R|A|$S|T]]]]

The auto generated code is the part of the Test Driven Development (TDD) approach. The methodology dictates - fail the unit test first and then code to fix the issue. It goes on in cycles of test a bit and code a bit. With these cycles a task gets completed.

It also applies to those applications that follow agile methodology with frequent feature addition and deployments. Few things could be under development and other associated stable components go to production. The in-progress methods or properties are marked with not implemented tag.

<pre><code>[TestClass] 
public class UnitComp1 
{ 
 [TestMethod] 
 public void SalaryCalculationTest() 
 { 
 Payroll pr = new Payroll(); 
 Assert.IsTrue(da.IsValidGrossAmount(2000), "Invalid gross amount"); 
 } 
} 

//Cycle 1 - Test fails
public class Payroll
{
 public bool IsValidGrossAmount(int amount)
 {
 throw new NotImplementedException();
 }
}

//Cycle 2 - Test passes (done)
public class Payroll
{
 public bool IsValidGrossAmount(int amount)
 {
 return amount &gt; 1000;
 }
}
</code></pre>

<a href="https://www.apnastudy.com/publicforumdetails/AVuC8FjM84he5u4soIOC/what-is-purpose-of-auto-generating-notimplemented-exception-stub-in-c" rel="nofollow noreferrer">Check out more, here</a>

blocks|key|4363897|text|所以，我知道这是一个古老的问题，但看起来Visual+Studio2017现在允许你在两种风格(throw和普通的老式get;set;)之间进行选择。(我使用的是2017社区的15.7.5+)。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4363898|为此，请转到Tools=>Options=>Text+Editor=>C#=>Advanced，并滚动到底部，在那里您应该有一个Implement+Interface+or+Abstract+Class部分。|4363899|在其中，您可以将When+generating+properties单选按钮设置为默认的“首选抛出属性”，或通过选择“首选自动属性”设置为旧样式。|4363900|下面是在Options设置中查找它的位置：|4363901|📷|atomic|4363902|​|4363903|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/8a51729c9c3f975e1f3c45932ec42cf2.png|imageAlt^0|1C|5|1N|8|0|1S|11|0|8|Q|0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|Z|8|@$9|10|A|11|B|C]|$9|12|A|13|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|14|8|@$9|15|A|16|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|17|8|@$9|18|A|19|B|C]]|D|@]|E|$]]|$1|J|3|K|5|6|7|1A|8|@]|D|@]|E|$]]|$1|L|3|M|5|N|7|1B|8|@]|D|@$9|1C|A|1D|1|1E]]|E|$]]|$1|O|3|P|5|6|7|1F|8|@]|D|@]|E|$]]|$1|Q|3|-4|5|6|7|1G|8|@]|D|@]|E|$]]]|R|$S|$5|T|U|V|E|$W|X|Y|-4]]]]

So, I know this is an old question, but it looks like Visual Studio 2017 now allows you to choose between the two styles (<code>throw</code> vs plain old <code>get;set;</code>). (I'm using 15.7.5 of 2017 Community).

To do this, go to Tools=>Options=>Text Editor=>C#=>Advanced, and scroll to the bottom, where you should have an <code>Implement Interface or Abstract Class</code> section.

Inside of that, you can set the <code>When generating properties</code> radio button to either the default "prefer throwing properties", or to the old style by selecting "prefer auto properties".

Here's where to look for it in the Options setting:
<a href="https://i.stack.imgur.com/vdgva.png" rel="noreferrer"><img src="https://i.stack.imgur.com/vdgva.png" alt="enter image description here"></a>

I'm using VS2017 Community and it just received an update yesterday. Today I wanted to implement an interface and now the implementation looks like this:

<pre><code>public string City 
{ 
 get =&gt; throw new NotImplementedException(); 
 set =&gt; throw new NotImplementedException(); 
}
</code></pre>

Instead of this (what I expected):

<pre><code>public string City { get; set; }
</code></pre>

Why this change? Not sure if this is specific to C#7 or VS or whatever. I just know that the auto implementation of interfaces has changed over the last week or so.

My interface:

<pre><code>public interface IMyInterface
{
 string City { get; set; }
}
</code></pre>

Implement interface includes throw new NotImplementedException... why?

Visual Studio

单元测试

我正在使用VS2017社区，昨天刚刚收到一个更新。今天我想实现一个接口，现在的实现如下所示：public string City {     get => throw new NotImplementedException();     set => throw new NotImplementedException(...

问实现接口包括抛出新的NotImplementedException...为什么？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问实现接口包括抛出新的NotImplementedException...为什么？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问实现接口包括抛出新的NotImplementedException...为什么？
EN