blocks|key|4569319|text|在这种情况下，我通常使用抽象类。创建您的基抽象类，然后从新控件继承它。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4569320|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|$]]

In this situation I usually use abstract classes. Create your base abstract class and then inherit it from your new controls.

blocks|key|4569349|text|您可以在接口上定义属性：interface+properties|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|4569350|public+interface+ISampleInterface
{
++++//+Property+declaration:
++++string+Name
++++{
++++++++get;
++++++++set;
++++}
}|code-block|syntax|javascript|4569351|entityMap|0|LINK|mutability|MUTABLE|url|http://msdn.microsoft.com/en-us/library/64syzecx(VS.80).aspx^0|C|K|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@$A|R|B|S|1|T]]|C|$]]|$1|D|3|E|5|F|7|U|8|@]|9|@]|C|$G|H]]|$1|I|3|-4|5|6|7|V|8|@]|9|@]|C|$]]]|J|$K|$5|L|M|N|C|$O|P]]]]

You can define properties on interfaces: <a href="http://msdn.microsoft.com/en-us/library/64syzecx(VS.80).aspx" rel="nofollow noreferrer">interface properties</a> 

<pre><code>public interface ISampleInterface
{
 // Property declaration:
 string Name
 {
 get;
 set;
 }
}
</code></pre>

blocks|key|1112897|text|您可以在接口中声明属性，如下所示：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1112898|public+interface+IMyInterface
{
+++string+Name+{+get;+set;+}
+++int+Age+{+get;+set;+}
}|code-block|syntax|javascript|1112899|然而，在这种情况下，听起来抽象类会更好。|1112900|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|$]]

You can declare a property in an interface as below:

<pre><code>public interface IMyInterface
{
 string Name { get; set; }
 int Age { get; set; }
}
</code></pre>

However, in this situation it sounds like an abstract class would be better.

blocks|key|504293|text|在接口上指定属性是完全可能的|type|unstyled|depth|inlineStyleRanges|entityRanges|data|504294|interface+IFoo+{
++string+Name+{+get;+set;+}+
++string+Age+{+get;+}+//+Read+Only
}|code-block|syntax|javascript|504295|但除此之外，你是对的。接口不指定任何行为，因此只能定义“抽象”方法和属性。实现必须在每个单独的实现者上完成。这就是为接口的灵活性付出的代价。|504296|如果所有子类之间的行为确实相同，那么我通常会选择抽象类。或者通常是一种组合。即定义接口和实现该接口的基本实现。|504297|class+Foo+:+IFoo+{+
++private+string+_name;
++public+Name+{+get+{+return+_name;+}+set+{+_name+=+value;+}+}
++public+Age+{+get+{+return+42;+}+}
}|504298|这使您可以灵活地快速实现，可以选择使用接口来处理由于某种原因无法从Foo派生的类。|504299|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|S|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|T|8|@]|9|@]|A|$]]|$1|K|3|L|5|D|7|U|8|@]|9|@]|A|$E|F]]|$1|M|3|N|5|6|7|V|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

It's definitely possible to specify a property on an interface

<pre><code>interface IFoo {
 string Name { get; set; } 
 string Age { get; } // Read Only
}
</code></pre>

But otherwise you are correct. Interfaces specify no behavior and hence can only define "abstract" methods and properties. The implementation must be done on every single implementor. That's the price that is paid for flexibility in interfaces.

If the behavior is truly identical between all of the child classes then I usually go for an abstract class. Or often a combination. Namely define an interface and a base implementation which implements that interface. 

<pre><code>class Foo : IFoo { 
 private string _name;
 public Name { get { return _name; } set { _name = value; } }
 public Age { get { return 42; } }
}
</code></pre>

This allows you the flexibility of a quick implementation with the choice of usincg an interface for classes that for some reason cannot derive from Foo.

blocks|key|4569484|text|.Net不允许多重继承，但是您可以使用“继承层次结构”来组织您的基类。这就是.Net本身的布局。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4569485|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|$]]

.Net doesn't allow multiple inheritance, but you can use an "inheritance hierarchy" to organize your base classes. This is how .Net itself is laid out.

blocks|key|4569535|text|我自己来自C%2B%2B背景，在那里多重继承是允许的，并且可以广泛地使用，所以我经常遇到和你一样的问题。你需要做的第一件事是阅读mix-+is+is这里你会注意到你自己一直在使用它们，而没有命名它们。第二步是在你需要的时候开始识别你的混入，你经常会发现你也可以通过组合来使用它们。第三步是使用组合来实现它们。是的，我也讨厌这样，但如果你想使用.NET+(或Java或...)，那就没有办法了:)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4569536|你应该使用inheritence的目的不是为了你的混合，而是为了实际识别你的项目的东西。我建议查看一些常见控件(文本框和类似控件)的.NET层次结构，以获得一些灵感。|4569537|祝好运|4569538|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|$]]

I myself come from a C++-background where multi-inheritance is allowed and used extensibly, so I often ran into the same problems as you. 
The first thing you need to do is to read up on mix-ins - here you'll prolly notice that you've used them yourself all along, without ever naming them.
Second step is to start to recognize your mixins whenever you need them, and you'll often find out that you might as well use them via composition.
Third step is to implement them using composition... Yes, i hate this too, but there's no way around it if you wanna go .NET (or Java or...) :)

What you should use inheritence for is not for your mixins, but for stuff that actually identifies your items. I recommend looking at the .NET hierachy for some of the common controls (textbox and the likes) to get some inspiration.

Good luck

I'm working on building my own base user interface classes. On them, I want them to all have similar "common" properties and methods. I could define an interface class, but interface appears to only allow abstract methods, and no properties.

I don't want to copy the otherwise exact same code to each class, but not sure how to implement... Ex: I want this common stuff to be applicable to Buttons, Textbox, Checkbox, Listbox, etc user controls.

Suggestions???

Common Properties and Methods assigned to different subclass types

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

我正致力于构建自己的基本用户界面类。在它们上，我希望它们都具有类似的“公共”属性和方法。我可以定义一个接口类，但是接口似乎只允许抽象方法，没有属性。我不想将完全相同的代码复制到每个类中，但不确定如何实现……例如:我希望这个通用的东西适用于按钮、文本框、复选框、列表框等用户控件。建议？

问分配给不同子类类型的通用属性和方法
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问分配给不同子类类型的通用属性和方法EN