.net-attributes

I know that attributes are extremely useful. There are some predefined ones such as [Browsable(false)] which allows you to hide properties in the properties tab. Here is a good question explaining attributes: What are attributes in .NET? What are the predefined attributes (and their namespace) you actually use in your projects? Vivek [DebuggerDisplay] can be really helpful to quickly see customized output of a Type when you mouse over the instance of the Type during debugging. example: [DebuggerDisplay("FirstName={FirstName}, LastName={LastName}")] class Customer { public string FirstName;

I am using XmlSerializer to write and read an object to xml in C#. I currently use the attributes XmlElement and XmlIgnore to manipulate the serialization of the object. If my xml file is missing an xml element that I require, my object still deserializes (xml -> object) just fine. How do I indicate (preferably via Attributes) that a certain field is "required"? Here is a sample method of what I am using currently: [XmlElement(ElementName="numberOfWidgets")] public int NumberThatIsRequired { set ...; get ...; } My ideal solution would be to add something like an XmlRequired attribute. Also, is

What is difference between DisplayName attribute and Display attribute in ASP.NET MVC? Spock They both give you the same results but the key difference I see is that you cannot specify a ResourceType in DisplayName attribute. For an example in MVC 2, you had to subclass the DisplayName attribute to provide resource via localization. Display attribute (new in MVC3 and .NET4) supports ResourceType overload as an "out of the box" property. Darin Dimitrov DisplayName sets the DisplayName in the model metadata. For example: [DisplayName("foo")] public string MyProperty { get; set; } and if you use

I am learning C# 3.5 and I want to know what [STAThread] does in our programs? Noldorin The STAThreadAttribute is essentially a requirement for the Windows message pump to communicate with COM components. Although core Windows Forms does not use COM, many components of the OS such as system dialogs do use this technology. MSDN explains the reason in slightly more detail: STAThreadAttribute indicates that the COM threading model for the application is single-threaded apartment. This attribute must be present on the entry point of any application that uses Windows Forms; if it is omitted, the