I am currently getting an exception in a proxy I generated. This is the
third issue I have stumbled upon; each of the previous issues was because
of "invalid" WSDL or schema. Which leads me to a bigger question...
Is it just me or does this architecture seem way to hard to debug?
It seems like
I like the performance argument and I agree with everything Ian had to say
except his conclusion ;-).
In many cases I am hoping people will TRY to derive from my classes and help
me to refactor the base class implementation. Is it really my job to
prevent someone from deriving in a way which I f
Nothing on DotNet-Web, so trying advanced...
When I am debugging an ASP.NET page and hit an exception, I would like the
same behavior I get when debugging a WinForms application. That is, the
debugger pops up on the offending line. This does not happen in ASP.NET
because of the default error ha
