The blog has moved to the new site F10Debug.com

Wednesday, April 15, 2015

Part 5: C#.Net interview question and answers



Part 1 - C#.Net interview questions and answers

Part 2 - C#.Net interview questions and answers

Part 3 - C#.Net interview questions and answers

Part 4 - C#.Net interview questions and answers

74. In which namespace, all .NET collection classes are contained?

75. What are methods?

76. Properties in C# and advantages of it ?

77. What are different types of arguments?

78. What is Out Keyword in C#?

79. What are access modifiers?
a) Public
b) Private
c) Protected
d) Internal
e) Protected Internal

80. How can we call the base method without creating an instance?

81. What is ‘this’ pointer?

82. Whether static method can use non static members?

83. How many instances can be created for an abstract class? Zero OR
Can we create object / instances of abstract class? No

84. Can a method be overloaded based on different return type but same argument type? No

85. What is the function of 'this' operator?

86. What are abstract methods?

87. What is difference between Static and Non-Static fields of a class?

88. What are inner classes and what is the practical implementation of inner classes?

89. Difference between bool and Boolean?

90. What is serialization? How do we implement serialization actually?

91. What’s the top .NET class that everything is derived from? System.Object.

92. What is the difference between int.Parse and int.TryParse methods?

93. Default modifier of Enum and Interface ? Public

94. What is the Default Modifier for Structure? Internal

95. What is the Default Modifier for methods, fields, and properties? Private

96. What is the escape sequence of null character? \0

97. IEnumarable vs Iqueriable?

98. system.string vs string?


Part 1 - C#.Net interview questions and answers

Part 2 - C#.Net interview questions and answers

Part 3 - C#.Net interview questions and answers

Part 4 - C#.Net interview questions and answers


2 comments:

  1. Great questions to make sure you're hiring programmers who know their fundamentals! Might want to throw in a few difficult questions though too, just to mix it up a bit. In my opinion, these questions are common knowledge. Instead of having a question ask for a definition type response, what if you gave a scenario that describes a piece of code, and ask what is being used that allows the code to work properly, or something similar? Perhaps even put in a few incorrect lines and see if they're picked up on. This would show experience with using these principles, instead of just the memorization of them, which won't help much in practice. Other than that, these are great!

    ReplyDelete
    Replies
    1. @Nick - I agree with you, but it depends on person to person, who is taking interview.

      But this is what i saw in last 7 yrs of experience. :)


      Delete