.NET Framework Exclusive Interview Questions and Answers (46) - Page 3

VAR is a implicit way of defining variable in .NET.Implicit means indirect way of defining variable types.

VAR is used primarily in 2 kinds of scenarios: -

Also view the following video on use of "VAR" keyword in .NET and C#: -

Reflection helps us to browse methods, properties and function of a given class or assembly on run time. You can also invoke the methods and functions using reflection. Below is a simple sample code where we are browsing in run time through methods and function of “MyClass”.

MyClass objMyClass = new MyClass();

// Get the class type

Type parameterType = objMyClass.GetType();

string name = parameterType.Name;

// Browse through members

foreach (MemberInfo objMemberInfo in parameterType.GetMembers())

{

	Console.WriteLine(objMemberInfo.Name);



}

// Browse through properties.

foreach (PropertyInfo objPropertyInfo in parameterType.GetProperties())

{

	Console.WriteLine(objPropertyInfo.Name);



}

If you want to invoke method and function you need to use the invoke member function as shown in the below code.

parameterType.InvokeMember("Display",BindingFlags.Public | BindingFlags.NonPublic | BindingFlags.InvokeMethod | BindingFlags.Instance,null, objMyClass, null);

Also see the following video on use of "VAR" keyword in .NET and C#: -

I use the following things for debugging c# applications using visual studio :-

1. step over if we want to move one step after other.
2. step in , if we want to move in to a function.
3. Step out , if we want to move out of the function.
4. Add watch and Quick watch to see the variable data.
5. Intellitrace to back trace debugging history.

Below is a simple video which explains the above 5 debuging tips in .NET

No, Garbage collector only claims memory for managed code i.e. code which is in IL code format. Any other component which is not developed using .NET framework is outside the control of garbage collector.

See the below garbage collector video for more details: -

There are 3 generations in garbage collector generation 0, 1 and 2. Generation 0 are fresh created objects, generation 1 are objects which are bit older than gen 0 and gen 2 are the oldest objects

See the below garbage collector video for more details: -

Background thread die off when the main thread is killed while foreground thread continue irrespective if the main thread dies or exists.

Below is a simple video which demonstrates what is threading and difference between background and foreground thread.