Skip to main content

Anonymous types - Examples

  • Simple
 var simple = "Simple Ann Type";
    string str= "Simple Ann Type";

Both the code are identical for MSIL
  • Array Initializer
var name = new string[] { "a","b","c" };
  1. Composite Anonymous Types
    We can think of this use of anonymous types as defining an inline class without all of the typing. 

  •    var Person = new {FirstName="Bill", LastName="Clinton"};

    1.           Console.WriteLine(Person);//will produce - {FirstName="Bill", LastName="Clinton"}

    2.           Console.WriteLine(Person.FirstName);//will produce - Bill

      1.           Console.WriteLine(Person.LastName);//will produce - Clinton

        1.           //Person.FirstName = "s"; - ERROR : Error 1 Property or indexer AnonymousType#1.FirstName' cannot be assigned to -- it is read only

        2.   Console.ReadLine();

          A nice feature added to anonymous types is the overloaded ToString method.So when you call Person.FirstName actually MSIL interprets it as Person.FirstName.ToString()
          Output of the Composite Type


          • In For Loops

        4.              var fibonacciSeries = new int[] { 1, 1, 2, 3, 5, 8, 13, 21 };
                      Console.WriteLine("normal For Loop");
                      for (var i = 0; i < fibonacciSeries.Length; i++)

                      Console.WriteLine("For Each Loop");
                      foreach (var fibo in fibonacciSeries)

                      Console.WriteLine("Linq in action - prints all the even numbers in the list");
                      foreach (var fvar in from fib1 in fibonacciSeries where fib1 % 2 == 0 select fib1)


          • Return from Functions

        5.             var newPerson = getPerson();
                      Type typ = newPerson.GetType();
                      Console.WriteLine(typ.GetProperty("FirstName").GetValue(newPerson, null));//will produce - Bill       

                  public static object getPerson()
                      var Person = new { FirstName = "Bill", LastName = "Clinton" };
                      return Person;

        6. Anonymous types can be returned from functions because the garbage collector (GC) cleans up any objects, but outside of the defining scope, the anonymous type is an
          instance of an object. As a practical matter, it is best to design solutions to use anonymous types within the defining scope.


          Popular posts from this blog

          PDCA & SCRUM (or Agile); Why is it important?

          The PDCA (Plan DO Check Act) cycle was made popular by Dr. W. Edwards Deming. This is a scientific cyclic process which can be used to improve the process (or product). This is cyclic in nature and usually time boxed. Plan  This is the first stage of the process. During this step the team discusses the objectives, the process and the clear conditions of exit (conditions of acceptance). This stage sets the measurable and achievable goals for the team. DO Team works together to achieve the objective set in the planning phase. Team works with the set of agreed process. Check Once the implantation is done team regroups and verifies the output and compares it to the agreed conditions of acceptance decided during the planning phase. The deviation, if any, is noted down. ACT If any deviation in planned tasks is observed during the Check stage, a root cause analysis is conducted. Team brainstorms and identifies the changes required to prevent such deviations in future. Team also

          Product Backlog: Should you write everything in user story format?

          I like user stories a lot. They help everyone talk the same language and results in a better product. User story alone does not constitute product requirement. User story is supposed to be a place holder for discussion which should happen between the team, Product Owner and the customer. This discussion result in a common understanding which along with the user story content is the product requirement. This format captures the essence of requirement without confusing the readers User Story is only one of the many different ways in which requirements can be represented. This is not mandatory in any Agile “process”. But many have made this mandatory. I have seen many spending countless hours trying to write the requirements in user story format when they could have easily written that in simple one-line sentence in few minutes.   I have seen team members refusing to even discuss the requirement until product owner rewrote the requirement in user story format. Once I

          Why is potentially shippable product quality important

          Agile teams work in iterations. During this period, they are supposed to work on product increments which can be “delivered” at the end of iteration. But how you know that the correct product was delivered? Many teams have different kinds of acceptance criteria and Definition of Done (DoD). But in many cases, this “done” is not the real “done” there might be some testing pending, some integration or review pending or anything else which prevents the actual use of the product increment. Many of these teams will need additional iterations to finish hardening their products. Many teams will implement different types of “gates” or approval steps to move to next stage. The free flow of product will be interrupted. They might end up doing mini waterfall within their agile process. Many don’t even realize this. This results in poor quality and requires additional effort to “harden” the product. Potentially Shippable Product increment The acceptance criteria and DoD should be modified