Skip to main content

A Deep Dive into C# Property

A property acts as a wrapper around a field. It is used to assign and read the value from a field by using set and get accessors. The code block for the get accessor is executed when the property is read and the code block for the set accessor is executed when the property is assigned a new value. A property can be created for a public, private, protected and internal field.
Unlike fields, properties do not denote storage locations and you cannot pass a property as a ref or out parameter.
  1. using System;
  2.  
  3. class Example
  4. {
  5. string name;
  6. public string Name
  7. {
  8. get { return name; }
  9. set { name = value; }
  10. }
  11. }
  12.  
  13. class Program
  14. {
  15. static void Main()
  16. {
  17. Example obj= new Example();
  18. obj.Name = "Dot Net Tricks"; // called set { }
  19. Console.WriteLine(obj.Name); // called get { }
  20. }
  21. }

When to use

  1. Need to validate data before assigning it to a field.
  2. Need to do intermediate computation on data before assigning or retrieving it to a field.
  3. Need to log all access for a field.
  4. Need to protect a field by reading and writing .

Different types of properties

Properties can be divided into three categories read-only, write-only, and read-write properties.
  1. Read-Only Property

    A read-only property allows you to only retrieve the value of a field. To create a read-only property, you should define the get accessor.
    1. class Example
    2. {
    3. string name;
    4. public string Name
    5. {
    6. get { return name; }
    7. }
    8. }
  2. Write-Only Property

    A write-only property allows you to only change the value of a field. To create a write-only property, you should define the set accessor.
    1. class Example
    2. {
    3. string name;
    4. public string Name
    5. {
    6. set{ name = value; }
    7. }
    8. }
  3. Read-Write Property

    A read-write property allows you to assign and read the value of a field. To create a read-write property, you should define the set and get accessors.
    1. class Example
    2. {
    3. string name;
    4. public string Name
    5. {
    6. get { return name; }
    7. set { name = value; }
    8. }
    9. }

Auto-implemented property

Auto-implemented properties was introduced with C# 3.0, which make property declaration more concise. Unlike standard property, in auto-implemented property, wrapped or backing field is automatically created by the compiler but it is not available for use by the class's members.
  1. public int Name { get; set; }
To make an auto-implemented property read-only or write-only, you need to specify both get and set accessors.
  1. public int ReadOnly { get; private set; }
  2. public int WriteOnly { private get; set; }

When to use Auto-implemented property

Simply, you need to store a value. No additional functionality can be added to either of the accessors.

Static property

You can also declare a property static. To make a static property you must ensure that the backing store field is also static. Typically, a static property is used to make a singleton class.
  1. public class Singleton
  2. {
  3. private static Singleton instance = new Singleton();
  4. private Singleton() { }
  5. public static Singleton GetInstance
  6. {
  7. get { return instance; }
  8. }
  9. }

Abstract property

An abstract property declaration does not provide an implementation of the property accessors. It leaves the accessors implementation to derived classes. Abstract properties are declared with in a abstract class or interface.
  1. public abstract class Person
  2. {
  3. public abstract string Name{ get; set;}
  4. }
  5.  
  6. class Student : Person
  7. {
  8. private string name;
  9. // Override Name property
  10. public override string Name
  11. {
  12. get { return name; }
  13. set { name = value; }
  14. }
  15. }
  1. public interface IPerson
  2. {
  3. string Name { get; set; }
  4.  
  5. }
  6.  
  7. class Student : IPerson
  8. {
  9. private string name;
  10.  
  11. // implement Name property
  12. public string Name
  13. {
  14. get { return name; }
  15. set { name = value; }
  16. }
  17. }

Comments

Popular posts from this blog

Accessing File Stored in Windows Azure Blob Storage Using jQuery

Did you know it was possible to access the Windows Azure Blob Storage directly from JavaScript, for example using jQuery? At first, it sounds obvious, since Blobs are after all accessible from a public UR. But in practice, there is a very big hurdle: the Web browser’s Same Origine Policy or SOP, that restricts JavaScript code to accessing resources originating from the same site the script was loaded from. This means that you will never be able to load a Windows Azure Blob using XMLHttpRequest for example! Fortunately, there is a popular workaround called JSONP (“JSON with Padding”). The idea behind this technique is that the script tag is not submitted to the SOP: an HTML page can thus load a JavaScript file from any site. So, if you expose your data in an “executable” form in JavaScript, a page will be able to load this data using a script tag. For example: <script type=”text/javascript” src=”http://www.sandeepknarware.in/exemple.jsonp”> </script> But how can ...

Support for debugging lambda expressions with Visual Studio 2015

Anyone who uses LINQ (or lambdas in general) and the debugger will quickly discover the dreaded message “Expression cannot contain lambda expressions”. Lack of lambda support has been a limitation of the Visual Studio Debugger ever since Lambdas were added to C# and Visual Basic.  With visual studio 2015 Microsoft has added support for debugging lambda expressions. Let’s first look at an example, and then I’ll walk you through current limitations. Example To try this yourself, create a new C# Console app with this code: using System.Diagnostics; using System.Linq; class Program { static void Main() { float[] values = Enumerable.Range(0, 100).Select(i => (float)i / 10).ToArray(); Debugger.Break(); } } Then compile, start debugging, and add “values.Where(v => (int)v == 3).ToArray()” in the Watch window. You’ll be happy to see the same as what the screenshot above shows you. I am using Visual Studio 2015 Preview and it has some limitati...

gcAllowVeryLargeObjects Element

There are numerous new features coming with .NET 4.5 and here, on this blog, you can find several posts about it. But the feature we are goint to talk about today is very exciting, because we were waiting for it more than 10 years. Since .NET 1.0 the memory limit of .NET object is 2GB. This means you cannot for example create array which contains elements with more than 2GB in total. If try to create such array, you will get the OutOfMemoryException. Let’s see an example how to produce OutOfMemoryException. Before that Open Visual Studio 2012, and create C# Console Application, like picture below. First lets create simple struct with two double members like example below: 1 2 3 4 5 6 7 8 9 10 11 12 public struct ComplexNumber {      public double Re;      public double Im;      public ComplexNumber( double re, double im)      {    ...