Warning From Explicitly Implementing an Interface with Optional Paramters?

The problem with optional arguments in C# is whether the callee sees the object as a TestClass or an ITestInterface . In the first case, the values declared in the class apply. In the second case the values declared in the interface apply.

It is because the compiler uses the statically available type information to construct the call. In case of an explicit interface implementation the method is never called 'for a class', always 'for an interface.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.