Today, we are going to get the knowledge of expressions.
Expressions have one or more operands and zero or more operators that evaluate to a single value.
Statements – A complete instruction – assigment of an expressions to a variable, an increment / decrement etc.
Statement must end in semi-colon;
Whitespace is ignored (use for humans)
Again let’s have a look at again on microsoft.com.
An expression is a sequence of one or more operands and zero or more operators that can be evaluated to a single value, object, method, or namespace. Expressions can consist of a literal value, a method invocation, an operator and its operands, or a simple name. Simple names can be the name of a variable, type member, method parameter, namespace or type.
Expressions can use operators that in turn use other expressions as parameters, or method calls whose parameters are in turn other method calls, so expressions can range from simple to very complex. Following are two examples of expressions:
((x < 10) && ( x > 5)) || ((x > 20) && (x < 25));
System.Convert.ToInt32("35");
Expression values
In most of the contexts in which expressions are used, for example in statements or method parameters, the expression is expected to evaluate to some value. If x and y are integers, the expression x + y evaluates to a numeric value. The expression new MyClass() evaluates to a reference to a new instance of a MyClass object. The expression myClass.ToString() evaluates to a string because that is the return type of the method. However, although a namespace name is classified as an expression, it does not evaluate to a value and therefore can never be the final result of any expression. You cannot pass a namespace name to a method parameter, or use it in a new expression, or assign it to a variable. You can only use it as a sub-expression in a larger expression. The same is true for types (as distinct from System.Type objects), method group names (as distinct from specific methods), and event add and remove accessors.
Every value has an associated type. For example, if x and y are both variables of type int, the value of the expression x + y is also typed as int. If the value is assigned to a variable of a different type, or if x and y are different types, the rules of type conversion are applied. For more information about how such conversions work, see Casting and Type Conversions.
Overflows
Numeric expressions may cause overflows if the value is larger than the maximum value of the value’s type. For more information, see Checked and Unchecked and Explicit Numeric Conversions Table.
Operator precedence and associativity
The manner in which an expression is evaluated is governed by the rules of associativity and operator precedence. For more information, see Operators.
Most expressions, except assignment expressions and method invocation expressions, must be embedded in a statement. For more information, see Statements.
Literals and simple names
The two simplest types of expressions are literals and simple names. A literal is a constant value that has no name. For example, in the following code example, both 5 and "Hello World" are literal values:
// Expression statements.
int i = 5;
string s = "Hello World";
For more information on literals, see Types.
In the preceding example, both i and s are simple names that identify local variables. When those variables are used in an expression, the variable name evaluates to the value that is currently stored in the variable’s location in memory. This is shown in the following example:
int num = 5;
System.Console.WriteLine(num); // Output: 5
num = 6;
System.Console.WriteLine(num); // Output: 6
Invocation expressions
In the following code example, the call to DoWork is an invocation expression.
DoWork();
A method invocation requires the name of the method, either as a name as in the previous example, or as the result of another expression, followed by parenthesis and any method parameters. For more information, see Methods. A delegate invocation uses the name of a delegate and method parameters in parenthesis. For more information, see Delegates. Method invocations and delegate invocations evaluate to the return value of the method, if the method returns a value. Methods that return void cannot be used in place of a value in an expression.
Query expressions
The same rules for expressions in general apply to query expressions. For more information, see LINQ Query Expressions.
Lambda expressions
Lambda expressions represent “inline methods” that have no name but can have input parameters and multiple statements. They are used extensively in LINQ to pass arguments to methods. Lambda expressions are compiled to either delegates or expression trees depending on the context in which they are used. For more information, see Lambda Expressions.
Expression trees
Expression trees enable expressions to be represented as data structures. They are used extensively by LINQ providers to translate query expressions into code that is meaningful in some other context, such as a SQL database. For more information, see Expression Trees.
Expression body definitions
C# supports expression-bodied members, which allow you to supply a concise expression body definition for methods, constructors, finalizers, properties, and indexers. For more information, see Expression-bodied members.
Remarks
Whenever a variable, object property, or object indexer access is identified from an expression, the value of that item is used as the value of the expression. An expression can be placed anywhere in C# where a value or object is required, as long as the expression ultimately evaluates to the required type.
Basic Programmer 