blocks|key|1519769|text|调试抽象类|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|1519770|没有什么可以阻止您调试抽象类，当调试您的子类时，调试器会根据需要自动将您重定向到父类的实现。|1519771|设计类层次结构|1519772|虽然在.NET中继承起来很简单，但如果没有清晰的类层次结构，它很快就很难维护。|1519773|继承并不是确保在OO中重用的唯一方法。|1519774|下面几个建议可能会有所帮助：|1519775|1519776|确保你的基类有一个清晰的继承深度较低的responsibility|unordered-list-item|1519777|Keep。|1519778|倾向于composition而不是继承。(使用interfaces可能是一个不错的选择)|CODE|1519779|1519780|entityMap|0|LINK|mutability|MUTABLE|url|http://en.wikipedia.org/wiki/Object_composition^0|0|5|0|0|0|7|0|0|0|0|0|0|0|N|A|3|B|0|0|0^^$0|@$1|2|3|4|5|6|7|17|8|@$9|18|A|19|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|1A|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|1B|8|@$9|1C|A|1D|B|C]]|D|@]|E|$]]|$1|J|3|K|5|6|7|1E|8|@]|D|@]|E|$]]|$1|L|3|M|5|6|7|1F|8|@]|D|@]|E|$]]|$1|N|3|O|5|6|7|1G|8|@]|D|@]|E|$]]|$1|P|3|-4|5|6|7|1H|8|@]|D|@]|E|$]]|$1|Q|3|R|5|S|7|1I|8|@]|D|@]|E|$]]|$1|T|3|U|5|S|7|1J|8|@]|D|@]|E|$]]|$1|V|3|W|5|S|7|1K|8|@$9|1L|A|1M|B|X]]|D|@$9|1N|A|1O|1|1P]]|E|$]]|$1|Y|3|-4|5|6|7|1Q|8|@]|D|@]|E|$]]|$1|Z|3|-4|5|6|7|1R|8|@]|D|@]|E|$]]]|10|$11|$5|12|13|14|E|$15|16]]]]

Debugging the abstract class

There is nothing preventing you from debugging the abstract class, when debugging your child classes the debugger will automatically redirect you to parent class's implementation as required.

Designing class hierarchies

Although simple to inherit in .NET, it can quickly become difficult to maintain if you don't have a clear class hierarchy. 

Inheritance is not the only way to ensure re-use in OO.

A couple of recommendations that might help:

<ul>
<li>Make sure your bases classes have a clear responsibility</li>
<li>Keep the depth of your inheritance low.</li>
<li>Tend to favour <a href="http://en.wikipedia.org/wiki/Object_composition" rel="nofollow">composition</a> over inheritance. (Using <code>interfaces</code> might be a good choice)</li>
</ul>

blocks|key|341418|text|如果你需要测试它，你可以做以下两件事之一：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|341419|1)你可以拥有非抽象的基类，这样基类就可以被实例化并进行测试。|341420|2)在您的测试项目中，您可以在基础上创建一个模拟包装器并测试模拟。|341421|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

If you need to test it, you can do one of two things: 

1) You can have base classes that are not abstract, so the base can be instantiated and therefore tested.

2) In your test project you can make a mock wrapper around the base and test the mock.

blocks|key|341462|text|type|unstyled|depth|inlineStyleRanges|entityRanges|data|341463|既然不可能实例化这样的类，那么如何调试它呢？|blockquote|341464|341465|341466|如果你问的是如何实际测试它(即单元测试)，我通常会编写一个从基类继承的测试类，并以这种方式对其进行测试。如果你问的是实际的调试，那么一旦你在一个正在运行的应用程序中用一个子类实例化了它，那么它与任何其他类没有什么不同。这有意义吗？|341467|341468|开发基类有什么实际的考虑因素吗？|341469|341470|341471|多年来，我听到了两种观点:+1)将任何常见的东西放入基类中；2)如果基类不是真正的继承，就不要创建基类。我倾向于前者的设计/编码，但#2确实有它的优点，因为它在某种程度上可以使设计变得反直觉。只有我的0.02美元...|341472|entityMap^0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|-4|4|5|6|Q|7|@]|8|@]|9|$]]|$1|A|3|B|4|C|6|R|7|@]|8|@]|9|$]]|$1|D|3|-4|4|5|6|S|7|@]|8|@]|9|$]]|$1|E|3|-4|4|5|6|T|7|@]|8|@]|9|$]]|$1|F|3|G|4|5|6|U|7|@]|8|@]|9|$]]|$1|H|3|-4|4|5|6|V|7|@]|8|@]|9|$]]|$1|I|3|J|4|C|6|W|7|@]|8|@]|9|$]]|$1|K|3|-4|4|5|6|X|7|@]|8|@]|9|$]]|$1|L|3|-4|4|5|6|Y|7|@]|8|@]|9|$]]|$1|M|3|N|4|5|6|Z|7|@]|8|@]|9|$]]|$1|O|3|-4|4|5|6|10|7|@]|8|@]|9|$]]]|P|$]]

<blockquote>
 Since it's not possible to instantiate
 such a class then how to debug it ?
</blockquote>

If you are asking how to actually test it then (i.e. Unit Test), I usually write a test class that inherits from the base class and test it that way. If you are asking about actually debugging then it is no different than any other class once you have instantiated it with a child class in a running application. Does that make sense?

<blockquote>
 Is there any practical considerations
 for developing base-classes ?
</blockquote>

Over the years I've heard two schools of though on this: 1) anything common put into a base class and 2) Don't make a base class if it is not a true inheritance. I tend to design/code to the former but #2 does have its merits in that it can make a design counter intuitive to some extent. Just my $0.02...

blocks|key|1519628|text|我会创建一个模拟对象，让它继承你的新抽象。您甚至可以使用模拟框架来实现这一点。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1519629|除非您使用Rhino+Mocks(我个人最喜欢的模拟框架)之类的工具，否则请随时使用它来运行您的单元测试。|1519630|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|$]]

I would make a mock object that you make to inherit from your new abstract. You could even use a mocking framework to do this. 

Keep it on hand to run your unit tests against, that is unless you use something like Rhino Mocks(my personal favorite mocking framework).

blocks|key|4005360|text|若要调试基类，请创建其中一个派生类的实例并通过该实例进行调试。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4005361|您还可以考虑创建另一个派生类，它除了从基类继承之外不做任何事情，这样您就可以对其进行测试。|4005362|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|$]]

To debug the base class, create an instance of one of the derived classes and debug through that.

You might also consider creating another derived class which doesn't do anything except inherit from the base class so you can test it.

blocks|key|1522235|text|首先，它不需要是抽象的，你的类就可以继承它，如果它不是抽象的，你可以实例化它。否则，只需在具体实现中调试它即可|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1522236|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|$]]

Firstly, it doesn't need to be abstract for your classes to inherit from it, and if it isn't abstract you can instantiate it. Otherwise just debug it form within a concrete implementation

blocks|key|341308|text|您可以在测试夹具程序集中创建一个派生版本(我假设您正在对基类进行单元测试，因此需要单独实例化它)，只是为了测试基类的功能。派生版本将提供测试基础所需的任何附加基础设施。您可以决定创建几个派生版本来测试抽象库的不同方面。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|341309|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|$]]

You could create a derived version in your test fixture assembly (I'm assuming you are unit testing the base, hence the need to instantiate it individually) just for the purposes of testing the functionality of the base class. The derived version would provide any additional infrastructure needed to test the base. You may decide to create several derived versions to test different aspects of the abstract base.

blocks|key|4005446|text|您可以使用从它继承的派生类来调试它。在调试它时，您需要记住所做的任何更改，并检查结果行为是否仍由所有派生类共享。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4005447|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|$]]

You would debug it by using the derived classes that inherit from it. When debugging it you will need to keep in mind any changes that you make and review if the resulting behaviour is still shared by all derived classes.

I wrote a class to do something and after a while I found that many other classes share the functionality so decided to implement a base-class (abstract in C#) and put all shared into it.

Since it's not possible to instantiate such a class then how to debug it ?

Is there any practical considerations for developing base-classes ?

Base-Class implementation considerations

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

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

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

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

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

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

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

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

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

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

社区新版编辑器体验调研

我写了一个类来做一些事情，过了一段时间，我发现许多其他类共享了这个功能，所以我决定实现一个基类(C#中的抽象)，并将所有共享放入其中。既然不可能实例化这样的类，那么如何调试它呢？开发基类有什么实际的考虑因素吗？

问基类实现注意事项
EN

回答 8

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问基类实现注意事项EN

回答 8

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问基类实现注意事项
EN