ArgumentNullException and ArgumentException

Brad Abrams ArgumentNullException and ArgumentException | Wood TV Stand

Brad Abrams ArgumentNullException and ArgumentException | Wood TV Stand — Mon, 01 Jun 2009 20:52:33 GMT

PingBack from http://woodtvstand.info/story.php?id=1343

Documentation bug for HttpServerUtility.Transfer

SampoSoft .NET — Wed, 15 Sep 2004 04:00:00 GMT

re: Internet, Intranet e le redirezioni

StrangeLog - Il blog di Andrea Saltarello — Mon, 13 Sep 2004 18:13:00 GMT

re: ArgumentNullException and ArgumentException

Brian Grunkemeyer — Mon, 05 Apr 2004 22:05:00 GMT

About the Missing & Empty constructors - there is no real difference. Whether the constructors are internal or private has no impact to the public API, especially since these classes are private. I suspect this was required in our original design, but never got fixed when we revamped these classes, about the same time we removed Variant from the public namespace about 2.5 years into writing V1. Either that, or it was an earlier compiler limitation. (We went through two separate compilers for V1 before we ported our source to C#.)

But this is a little odd, and I'll make these constructors are private.

re: ArgumentNullException and ArgumentException

Adrian Florea — Sun, 04 Apr 2004 22:25:00 GMT

Why this singleton System.Reflection.Missing has the constructor internal instead of private? Same question for the internal class System.Empty.

re: ArgumentNullException and ArgumentException

Kit George — Sat, 06 Mar 2004 00:00:00 GMT

With regards to Ilya's question (why not add EndsWith/Startswith overloads that accept a char), there's simply not much of a gain here. We actually have a feature request for this, but it's lower down on our priority stack.

On Rich's Random.Next issue: yup, this is an unfortunate one. But basically, we can't change this behavior, for breaking change reasons. However, I just entered a feature request for us to consider either a new method, or a new overload (consider obsoleting this one).

re: ArgumentNullException and ArgumentException

RichB — Wed, 03 Mar 2004 17:43:00 GMT

Random.Next(0,1);

does not return numbers in the set {0..1}. It returns numbers in the set {0..0}. Arghh!

Windows.Management

Mike Krings — Tue, 02 Mar 2004 23:12:00 GMT

Publishing WMI Classes is nearly unrecoverable in case of a failure:

If the WMI class is not yet registered and the user is not in the Admin group, a simple System.Exception is thrown. No real chance to gracefully handle this, as the only hint on the source of the error is the error message.

If publishing fails because of an Security exception, the Exception raised is a COMException (shouldn't it be a ComException ?) with a WMI specific (not System.Management published) HRESULT of 0x80041003.

Looks like a real hasty transformation of the WMI API.

re: ArgumentNullException and ArgumentException

Ilya Ryzhenkov — Sun, 29 Feb 2004 05:29:00 GMT

My favorite is internal bool EndsWith(char value) in String class. Why it would be internal? Also, there is no bool StartsWith(char value).

re: ArgumentNullException and ArgumentException

Brad Abrams — Sun, 29 Feb 2004 00:20:00 GMT

Mike, on the issues with SmtpServer, you will be happy to know that in Whidbey we will be adding a much better mail support to the platform that does, I am told, fix this problem.