Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I noticed that when overriding virtual methods in C# using Visual Studio, the IDE automatically adds the base.Method() call. On the other hand, when overriding abstract methods, the IDE automatically adds a NotImplementedException().
Why does VS automatically adds the base.Method() call when overriding virtual methods? Is it best practice to call the base method?
That depends if you still need the base behaviour to occur. This decision would be made on a case by case basis. There’s no hard and fast rule, although some patterns would expect a call to the base method (correct implementation of the IDisposable pattern works this way)