blocks|key|3845566|text|这是一个很难给出一般答案的问题。属性是另一种语言功能，如果使用得当，它会非常强大，但也有可能被滥用。我从来没有看到过一个令人信服的理由完全抛弃属性的使用，也确实没有理由认为它们是一个坏主意。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3845567|事实上，事实恰恰相反。属性允许将框架特定的信息添加到元数据中。无法通过类型层次结构轻松表达的信息。这极大地增强了使用属性的框架的能力。|3845568|我肯定看到过一两个实现，人们滥用了它们，但并不壮观。你能说得更具体些吗？有没有你正在谈论的特定属性/框架。|3845569|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|$]]

This is a hard question to give a general answer for. Attributes are another language feature that are incredibly powerful when used correctly but do have the potential for abuse. I haven't ever seen a compelling reason to dump the use of attributes altogether and really no reason to think they are a bad idea. 

In fact the exact opposite is true. Attributes allow for adding framework specific information into the metadata. Information that simply cannot be easily expressed via a type hierarchy. This dramatically increases the power of frameworks that use attributes. 

I've certainly seen an implementation or two where people abused them a bit but nothing spectacular. Can you be more specific? Are there specific attributes / frameworks you're talking about.

blocks|key|3845619|text|当涉及到定义关于我的代码的元数据时，我发现它们非常有用。我使用它们为插件架构生成自定义报告，并与第三方代码进行通信。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3845620|我想你可以按惯例做任何事情，但我喜欢它们。|3845621|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 find them extremely useful when it comes to defining meta-data about my code. I use them to generate custom reports, for plug-in architectures, and for communicating to third-party code.

I suppose you can do everything by convention, but I like them.

blocks|key|1171660|text|好吧，如果ASP.NET+MVC是可以参考的，我会说不用担心。在这个框架中使用反射和属性做了很多事情，所以我看不出它有任何问题。MVC是一个相当新的框架，它被广泛使用。从验证输入、处理错误，到非常棒的ActionFilter属性，它们都有很多。所以不，我个人认为他们没有什么问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1171661|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|$]]

Well, if ASP.NET MVC is anything to go by, I'd say don't worry about it. So much is done in that Framework using reflection and attributes, that I don't see any issues with it. MVC is a fairly new framework, and it's used all over the place. From validating input, handling errors, to the very awesome ActionFilter attribute, there's alot of them. So no, I personally see nothing wrong with them.

blocks|key|1171697|text|这是一个相当宽泛的问题，就像“我应该在砂锅里放奶酪吗”；对这两个问题的答案都是“这取决于你做的是什么”。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1171698|如果您大量使用添加，并且几乎像使用声明性编程范例一样使用它们，那么在此过程中您可能会遇到麻烦。无论它是来自于反射中的某个地方的速度减慢，还是仅仅是一般的可维护性，每个人都在猜测。|1171699|当它们合适的时候，就像所有的东西都else...use它们，使你的代码更有效率或可读性。不要为了使用而使用它们，也不要为了抛弃它们而放弃它们。|1171700|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|$]]

That's a pretty broad question, like "should I put cheese in my casserole"; The answer to both is "it depends on what you're making".

If you're making heavy use of addributes and using them almost like a declarative programming paradigm, then you're probably going to run into trouble along the way. Whether it comes from a slowdown somewhere in reflection or just general maintainability is anybody's guess.

It's like everything else...use them when they're appropriate and make your code more efficient or readable. Don't use them for the sake of using them, and don't abandon them for the sake of abandoning them.

blocks|key|3845767|text|我看到在ASP.NET+MVC中大量使用了属性。事实上，切换到MVC使我大大增加了对属性的使用。我不确定你对反属性反弹的看法是从哪里来的，但我肯定不会从MS那里看到它，至少在MVC方面是这样。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3845768|我特别喜欢属性可以用来提供横切行为(方面)的方式，这些横切行为(方面)可以跨越那些如此修饰的控制器/动作。看到MVC是如何在动作调用之前和之后处理属性调用的，我相信这是让方面在MVC中工作的首选方法。|3845769|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 see heavy use of Attributes in ASP.NET MVC. In fact, switching to MVC has caused me to increase my use of Attributes significantly. I'm not sure where your perception of anti-Attribute backlash is coming from, but I certainly don't see it from MS, at least with respect to MVC.

I particularly like the way that Attributes can be used to provide cross-cutting behavior (aspects) across those controller/actions that are so decorated. Seeing how MVC is built to handle attribute invocation before and after action invocation, I've got to believe that this is the preferred way to get aspects to work in MVC.

blocks|key|623861|text|属性实际上有两个目的:作为用户可见的东西，以及作为编译器发出的东西。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|623862|我假设你说的是用户可见的属性。|623863|一般来说，我会说用户可见的属性并不理想。|623864|大多数时候，它们被用来在C#之上嵌入某种形式的自定义语言。DLINQ属性就是一个很好的例子。从消费者的角度来看，一种更好的方法是向宿主语言添加一流的支持。这最终会让人感觉自然得多。(与所有疯狂的linq-+to+-sql属性相比，具有对定义表和外键的语言支持要容易得多)。|623865|然而，在现实中，对于大多数开发人员来说，扩展编程语言的成本太高了。好处并不会超过成本。|623866|也许有一天C#会有元编程功能，这将使做这类事情变得容易。|623867|然而，目前这种能力还不存在。|623868|这给你留下了3个选择：|623869|623870|Use+attributes|ordered-list-item|623871|使用动态语言，并在运行时生成代码|623872|只是不使用生成式编程|623873|623874|通常情况下，#1最终是最容易做出的选择，即使它并不理想。|623875|entityMap^0|0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|12|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|13|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|14|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|15|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|16|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|17|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|18|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|19|8|@]|9|@]|A|$]]|$1|P|3|-4|5|6|7|1A|8|@]|9|@]|A|$]]|$1|Q|3|R|5|S|7|1B|8|@]|9|@]|A|$]]|$1|T|3|U|5|S|7|1C|8|@]|9|@]|A|$]]|$1|V|3|W|5|S|7|1D|8|@]|9|@]|A|$]]|$1|X|3|-4|5|6|7|1E|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|6|7|1F|8|@]|9|@]|A|$]]|$1|10|3|-4|5|6|7|1G|8|@]|9|@]|A|$]]]|11|$]]

There are really two purposes of attributes: as user visible things, and as things emitted by a compiler.

I assume you are talking about user visible attributes. 

In general, I would say that user visible attributes are not ideal.

Most of the time they are used to embed some form of custom language on top of C#. DLINQ attributes are a good example of this. A better approach, from the consumer's perspective, would be to add first class support to the host language. That would end up feeling much more natural. (having language support for defining tables and foreign keys would be much easier to work with then all the crazy linq-to-sql attributes).

In reality, however, extending a programing language is too cost prohibitive for most developers. The benefits just don't out weigh the costs.

Perhaps someday C# will have meta-programing features, which will make doing that kind of thing easy.

At the moment, however, that capability does not exist.

This leaves you with 3 options:

<ol>
<li>Use attributes</li>
<li>Use a dynamic language, and generate code at runtime</li>
<li>Just don't use generative programing</li>
</ol>

Usually #1 ends up being the easiest choice to make, even if it isn't ideal.

blocks|key|623914|text|我个人认为，像大多数语言功能一样，属性也有自己的位置，但可能会被滥用或误用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|623915|在正确的框架中，它们是无价的。它们无疑简化了像DI框架这样的东西(MEF就是一个很好的例子)，并且对于测试框架这样的事情非常非常有用。|offset|length|623916|然而，我认为疯狂地添加用户定义的属性可能有些夸张。我个人喜欢使用属性，但尽量将它们的使用保持在最低限度，并且只在最有意义的地方使用它们。|623917|entityMap|0|LINK|mutability|MUTABLE|url|http://www.codeplex.com/MEF^0|0|X|3|0|0|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]]|A|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]]]

I personally think attributes, like most language features, have their place, but can be abused or misused.

In the correct framework, they are invaluable. They definitely simplify things like DI frameworks (<a href="http://www.codeplex.com/MEF" rel="nofollow noreferrer">MEF</a> is a great example), and are very, very useful for things like testing frameworks.

I think going crazy adding user defined attributes can be overkill, however. I personally love using attributes, but try to keep their usage to a minimum, and only use them where they make the most sense.

I have based many designs and frameworks that use C# Attributes over the past 4 or 5 years.

But lately I see many people openingly discouraging their use or changing their frameworks to reduce the need or use of them.

I found them to be a godsend but now I am starting to wonder what I am missing.

To clarify: 
Use Convention over Configuration is becoming a major principle to follow especially in the ORM field. Is this area you can map fields with a config file (XML), use an attribute, or have a common naming convention that maps directly to fields in your database tables. I don't have any references to quote but I have read some backlash against adding another Attribute to the mix.

But I feel over the three choices I just listed that Attributes still make the most sense. A Config file is harder to maintain and a common naming convention ties you to the implementation of the database field. Attributes are placed exactly where they are needed and the implemntation can change without disconnecting from where it is used.

Do you think C# attributes (or similar mechanisms) are a good idea or do you discourage the use of them?

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

在过去的4到5年里，我已经开发了很多使用C#属性的设计和框架。但最近，我看到许多人公开反对使用它们，或者改变他们的框架，以减少对它们的需求或使用。我发现它们是天赐之物，但现在我开始想知道我错过了什么。需要澄清的是:使用约定而不是配置正在成为一个需要遵循的主要原则，尤其是在ORM领域。您可以使用配置文件(XML)映射字段...

问您认为C#属性(或类似的机制)是一个好主意，还是不鼓励使用它们？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问您认为C#属性(或类似的机制)是一个好主意，还是不鼓励使用它们？EN