Introducing the .NET Framework Standard Library Annotated Reference Vol1

re: Introducing the .NET Framework Standard Library Annotated Reference Vol1

Corrado Cavalli — Thu, 25 Mar 2004 19:23:00 GMT

Congratulations!,
Can't wait to read it... :-)

re: Introducing the .NET Framework Standard Library Annotated Reference Vol1

Eric — Thu, 25 Mar 2004 19:49:00 GMT

Wait, I'm confused. I thought the whole point of ApplicationException was to serve as a base for all application-specific exceptions... All of the Microsoft examples for custom exceptions (including this one: http://msdn.microsoft.com/msdnmag/issues/02/11/NETExceptions/default.aspx) inherit from ApplicationException. Is JR's annotation incorrect, or are all of the examples wrong?

re: Introducing the .NET Framework Standard Library Annotated Reference Vol1

Don — Thu, 25 Mar 2004 19:50:00 GMT

I'm confused. Are these comments indended for the programming public, or microsoft employees? I thought ALL custom exceptions should inherit from ApplicationException and you should never write code to catch Exception.

re: Introducing the .NET Framework Standard Library Annotated Reference Vol1

Roy J. Salisbury @ VsDevCentral — Thu, 25 Mar 2004 20:29:00 GMT

Brad,

How about sharing the TOC from the book. As soon as I read your blog entry I clicked on over to Amazon to purchase it, but was confused by the title:

.NET Framework Standard Library Annotated Reference, Volume 1: Base Class Library and Extended Numerics Library, 1/e

I'm not exactly sure what Vol 1 covers. You stated that Vol 2 would be an update for Whidbey/Longhorn, but the title for Vol 1 dosent sound like it has everything "pre-whidbey".

.NET Framework Standard Library Annotated Reference Vol1

Robert Hurlbut's .Net Blog — Fri, 26 Mar 2004 00:03:00 GMT

re: ApplicationException

Martin Liversage — Thu, 25 Mar 2004 21:07:00 GMT

When first reading Mr. Richters advice on not using ApplicationException I was stunned, but it actually make sense. If you create some application specific exceptions you may want to derive these exceptions from a common base class in order to be able to catch them all in a single catch clause. Deriving this common exception from ApplicationException doesn't add anything useful to your exception hierarchy - it just deepens it. Off course, you may also want to use a library you have written providing a different set of exceptions, but you rarely want to treat these exceptions in the same way as you treat your application exceptions. Except in cases where there is some form of coupling, but then you need to consider that in your exception design. I now realize that ApplicationException doesn't add anything useful to the mix.

I'm sure that Mr. Abrams selected the ApplicationException sample not because it is the first in the book, but because Mr. Richters annotation can be seen as "sensational" and it will attract a lot of attention to this blog entry. :^) I can already see the /. headline: .NET guru uncovers huge flaw in MS coding guidelines (just kidding.)

re: Introducing the .NET Framework Standard Library Annotated Reference Vol1

Darrell — Thu, 25 Mar 2004 21:14:00 GMT

Roy - he didn't say Vol 2 would be an update for Whidey/Longhorn. He said sales "will help my case to produce volume II, update for Whidbey\Longhorn, etc." The commas mean Vol 2, and/or Whidbey update, and/or Longhorn update, etc.

re: Introducing the .NET Framework Standard Library Annotated Reference Vol1

Eric — Thu, 25 Mar 2004 21:28:00 GMT

"When first reading Mr. Richters advice on not using ApplicationException I was stunned, but it actually make sense. If you create some application specific exceptions you may want to derive these exceptions from a common base class in order to be able to catch them all in a single catch clause. Deriving this common exception from ApplicationException doesn't add anything useful to your exception hierarchy - it just deepens it."

That's true, and it certainly makes sense (my custom exceptions are all inherited from a single application base exception class) -- I'm just confused as to why <strong>every single example</strong> Microsoft has put out -- in the MCSD books, in the MSDN samples, in the very documentation for the ApplicationException class -- says that ApplicationException should always be the base class for all custom exceptions. It's a simple change to make if you have a single custom exception base class (you just change its inheritance to System.Exception instead of System.ApplicationException and voila), but given that it's such a simple change I have no idea why this hasn't been changed in any of the docs, even for 1.1. Will the docs reflect this in 2.0, or is this some super secret initiation ritual to prove you're not a .Net newbie? :)

re: Introducing the .NET Framework Standard Library Annotated Reference Vol1

Roy J. Salisbury @ VsDevCentral — Thu, 25 Mar 2004 22:28:00 GMT

Darrell..

You are correct, I had mis-read that. Thanks for pointing that out. But the idea behind the post stands (the TOC, and just what is actually covered in the book).

I hate getting "Vol ??" type books until all the volumns are available, unless the volums are seperated on a specific line (Vol 1 - WinForms, Vol 2 - .NET CF, Vol 3 - ASP.NET, ect).

.NET Framework Standard Library Annotated Reference Vol1 Book

Andrew Stopford's Weblog — Fri, 26 Mar 2004 01:48:00 GMT

re: Introducing the .NET Framework Standard Library Annotated Reference Vol1

Ivan Towlson — Fri, 26 Mar 2004 08:10:00 GMT

Brad, what is the balance between the "here are the types and signatures and code fragments" stuff and the annotations or behind-the-scenes insights? The latter sound useful and interesting, but I already have the former in MSDN. Put another way, how much of the book is "added value" over the main Framework documentation?

re: Introducing the .NET Framework Standard Library Annotated Reference Vol1

Brad Abrams — Fri, 26 Mar 2004 11:56:00 GMT

Thanks for all the comments on the book, I can already see that this book is going to be a fun source of blogging fodder! I tried to maintain a very minium level of editorial discretion on the annotations. My goal was to get folks that were heavily involved in the design of the BCL to comment candidly from their point of view. There are no annotations that are wrong technically, but that does not mean they are all the Microsoft official postion.

That said, I happen to agree with Jeff on ApplicationException. IMHO, the biggest problem is there is such a fine line between applications and libraries and that line will get more fuzzy overtime. Is Word an application or a library? There is nothing that will break if you inherit from ApplicationExeption, but it is also true that nothing in the system depends on Exceptions driving from ApplicationException. Martin Liversage sums it up well, ApplicationException just does not provide a much value.

As for the TOC, I will get that posted soon (I am actually OOF on vacation right now)

Right – Vol2 will cover the Xml, Reflection and Runtime Infrastructure libraries.

Ivan, There are around 100 annotations in the book and a TON of samples we added over and above what is in the standard\docs. You may find this isn’t trye for you, but I have found the page layout, diagrams, ILASM signatures, etc do at significant value as well.

Oh, yes, someone on my team suggested I included this books Amazon sales rank with each post so we can track it overtime. It was ~3,000 when I did the original post.
Current Amazon Sales Rank: 1,026

re: Introducing the .NET Framework Standard Library Annotated Reference Vol1

Brad Abrams — Fri, 26 Mar 2004 12:06:00 GMT

In lieu of the full TOC, I thought just a list of the types covered in Vol1 would help folks. Does that help?

System.ApplicationException
System.ArgumentException
System.ArgumentNullException
System.ArgumentOutOfRangeException
System.ArithmeticException
System.Array
System.ArrayTypeMismatchException
System.AsyncCallback
System.Attribute
System.AttributeTargets
System.AttributeUsageAttribute
System.Boolean
System.Byte
System.Char
System.CharEnumerator
System.CLSCompliantAttribute
System.Collections.ArrayList
System.Collections.Comparer
System.Collections.DictionaryEntry
System.Collections.Hashtable
System.Collections.ICollection
System.Collections.IComparer
System.Collections.IDictionary
System.Collections.IDictionaryEnumerator
System.Collections.IEnumerable
System.Collections.IEnumerator
System.Collections.IHashCodeProvider
System.Collections.IList
System.Console
System.Convert
System.DateTime
System.Decimal
System.Delegate
System.Diagnostics.ConditionalAttribute
System.DivideByZeroException
System.Double
System.DuplicateWaitObjectException
System.Enum
System.Environment
System.EventArgs
System.EventHandler
System.Exception
System.ExecutionEngineException
System.FlagsAttribute
System.FormatException
System.GC
System.Globalization.DateTimeFormatInfo
System.Globalization.DateTimeStyles
System.Globalization.NumberFormatInfo
System.Globalization.NumberStyles
System.Globalization.UnicodeCategory
System.IAsyncResult
System.ICloneable
System.IComparable
System.IDisposable
System.IFormatProvider
System.IFormattable
System.IndexOutOfRangeException
System.Int16
System.Int32
System.Int64
System.InvalidCastException
System.InvalidOperationException
System.InvalidProgramException
System.IO.Directory
System.IO.DirectoryNotFoundException
System.IO.EndOfStreamException
System.IO.File
System.IO.FileAccess
System.IO.FileLoadException
System.IO.FileMode
System.IO.FileNotFoundException
System.IO.FileShare
System.IO.FileStream
System.IO.IOException
System.IO.MemoryStream
System.IO.Path
System.IO.PathTooLongException
System.IO.SeekOrigin
System.IO.Stream
System.IO.StreamReader
System.IO.StreamWriter
System.IO.StringReader
System.IO.StringWriter
System.IO.TextReader
System.IO.TextWriter
System.MarshalByRefObject
System.Math
System.NotFiniteNumberException
System.NotSupportedException
System.NullReferenceException
System.Object
System.ObjectDisposedException
System.ObsoleteAttribute
System.OutOfMemoryException
System.OverflowException
System.Random
System.RankException
System.SByte
System.Security.CodeAccessPermission
System.Security.IPermission
System.Security.Permissions.CodeAccessSecurityAttribute
System.Security.Permissions.EnvironmentPermission
System.Security.Permissions.EnvironmentPermissionAccess
System.Security.Permissions.EnvironmentPermissionAttribute
System.Security.Permissions.FileIOPermission
System.Security.Permissions.FileIOPermissionAccess
System.Security.Permissions.FileIOPermissionAttribute
System.Security.Permissions.PermissionState
System.Security.Permissions.SecurityAction
System.Security.Permissions.SecurityAttribute
System.Security.Permissions.SecurityPermission
System.Security.Permissions.SecurityPermissionAttribute
System.Security.Permissions.SecurityPermissionFlag
System.Security.PermissionSet
System.Security.SecurityElement
System.Security.SecurityException
System.Security.VerificationException
System.Single
System.StackOverflowException
System.String
System.SystemException
System.Text.ASCIIEncoding
System.Text.Decoder
System.Text.Encoder
System.Text.Encoding
System.Text.StringBuilder
System.Text.UnicodeEncoding
System.Text.UTF8Encoding
System.Threading.Interlocked
System.Threading.Monitor
System.Threading.SynchronizationLockException
System.Threading.Thread
System.Threading.ThreadAbortException
System.Threading.ThreadPriority
System.Threading.ThreadStart
System.Threading.ThreadState
System.Threading.ThreadStateException
System.Threading.Timeout
System.Threading.Timer
System.Threading.TimerCallback
System.Threading.WaitHandle
System.TimeSpan
System.Type
System.TypeInitializationException
System.UInt16
System.UInt32
System.UInt64
System.UnauthorizedAccessException
System.ValueType
System.Version

CLR: .NET Framework Standard Library Annotated Reference Vol 1 Finally ships

Ken Brubaker — Fri, 26 Mar 2004 15:45:00 GMT

There is agreement among the BCL folks that ApplicationException was a mistake.

re: Introducing the .NET Framework Standard Library Annotated Reference Vol1

Darrell — Fri, 26 Mar 2004 13:13:00 GMT

Roy - yeah, I agree. I like buying Volume 1-x all at the same time. For example, the Essential .NET Vol 1 with Don Box, where's Vol 2, huh?

Ny bok av Brad Abrams

Dag König — Fri, 26 Mar 2004 21:02:00 GMT

Han har precis släppt en ny tjock bok som jag direkt beställde ifrån Amazon. .NET Framework Standard Library Annotated Reference Vol 1, heter den. Vilken titel. Mums. Introducing the .NET Framework Standard Library Annotated Reference Vol1

Custom Base Exception Class

Mark Treadwell — Sat, 27 Mar 2004 06:10:00 GMT

re: Introducing the .NET Framework Standard Library Annotated Reference Vol1

Roy J. Salisbury @ VsDevCentral — Sat, 27 Mar 2004 20:01:00 GMT

Brad - The list you posted is should be fine instead of the TOC. That, along with your other post about what is/may be planned for vol 2 is enough for me to purchase it.

Darrell - Yea. I have that one as well. I guess I am that way because the company I used to work for (TurboPower Software) wrote a library once (Essentials, Vol I) with every intention of doing more, but never did. It turned into a running joke in the company.

re: Introducing the .NET Framework Standard Library Annotated Reference Vol1

Avery Moore — Mon, 29 Mar 2004 19:33:00 GMT

Congrats on the book. The The Java Class Libraries, Volume 1 used to be one of my favorite java references from back in my java days.

re: Introducing the .NET Framework Standard Library Annotated Reference Vol1

Ben — Thu, 01 Apr 2004 08:21:00 GMT

Why can't you print the poster that comes as a PDF on the accompanying CD? The book I can obviously understand ;) but the poster ?

re: Introducing the .NET Framework Standard Library Annotated Reference Vol1

Brad Abrams — Thu, 01 Apr 2004 14:23:00 GMT

Thanks for your comment Ben... There is a printed poster bound into the book that can easily be detached... does that help?

Custom Base Exception Class

Mark Treadwell — Fri, 02 Apr 2004 04:28:00 GMT

TOC for the SLAR

Brad Abrams — Wed, 07 Apr 2004 05:04:00 GMT

TOC for the SLAR

Brad Abrams — Thu, 08 Apr 2004 07:48:00 GMT

RE: System.Exception and System.ApplicationException

Eli Robillard's World of Blog. — Mon, 10 May 2004 20:10:00 GMT

Design Guidelines: Something for Everyone

Mark Treadwell — Wed, 19 May 2004 04:16:00 GMT

Design Guidelines: Something for Everyone

Mark Treadwell — Wed, 19 May 2004 04:23:00 GMT

re: rethrow for debugging

jaybaz_MS's WebLog — Sat, 22 May 2004 04:58:00 GMT

re: Update: C# Coding Standards v1.13

Lance's Whiteboard — Wed, 18 Aug 2004 02:58:00 GMT

Best practices on custom exceptions? (where we derive it from?)

Blogging About .NET — Thu, 04 Nov 2004 16:15:00 GMT

re: What's wrong with this code? (#3)

Eric Gunnerson's C# Compendium — Fri, 19 Nov 2004 12:44:00 GMT

re: What's wrong with this code? (#3)

Eric Gunnerson's C# Compendium — Tue, 23 Nov 2004 22:07:00 GMT

Comments on the CLI standard

Brad Abrams — Fri, 07 Jan 2005 18:55:00 GMT

re: Exception Management

Edward Ferron's WebLog — Tue, 08 Feb 2005 16:19:00 GMT

From the Dallas user's group meeting

Brad Abrams — Fri, 11 Feb 2005 17:23:00 GMT

Creating

Rolando Ramirez's WebLog — Mon, 11 Apr 2005 17:28:24 GMT

Creating

Rolando Ramirez's WebLog — Mon, 11 Apr 2005 17:33:13 GMT

Custom Base Exception Class - V1 (VB)

.NET Hobbyist Programmer — Sun, 10 Jul 2005 06:21:08 GMT

ThinkSharp.org » Blog Archive » Custom Exceptions and Serialization.

ThinkSharp.org » Blog Archive » Custom Exceptions and Serialization. — Fri, 10 Mar 2006 15:24:09 GMT

PingBack from http://www.thinksharp.org/2006/03/09/custom-exceptions/

FAQ: Why do some sources recommend extending ApplicationException while FxCop does not? [Michael Fanning, David Kean]

Visual Studio Managed Code Analysis (FxCop) — Thu, 06 Apr 2006 06:31:08 GMT

TypesShouldNotExtendCertainBaseTypes fires on types that derive from ApplicationException and DoNotRaiseReservedExceptionTypes...

FAQ: Why do some sources recommend extending ApplicationException while FxCop does not? [Michael Fanning, David Kean]

Visual Studio Managed Code Analysis (FxCop) — Thu, 12 Oct 2006 19:52:12 GMT

TypesShouldNotExtendCertainBaseTypes fires on types that derive from ApplicationException and DoNotRaiseReservedExceptionTypes

shiftMode » Blog Archive » Microsoft changes it’s ApplicationException stance

shiftMode » Blog Archive » Microsoft changes it’s ApplicationException stance — Fri, 11 May 2007 18:49:42 GMT

PingBack from http://shiftmode.com/2007/05/microsoft-changes-its-applicationexception-stance.html

Goodbye ApplicationException!

knom's developer corner — Tue, 15 May 2007 15:42:25 GMT

While researching on Visual Studio Static Code Analysis topics I come over blog posts by Brad Abrams

Scott’s Blog » Don’t Derive from ApplicationException

Scott’s Blog » Don’t Derive from ApplicationException — Fri, 13 Jul 2007 14:50:04 GMT

PingBack from http://scottlaw.knot.org/blog/?p=218

Thachvv’s Weblog Exception Handling Best Practices in .NET «

Thachvv’s Weblog Exception Handling Best Practices in .NET « — Sun, 05 Aug 2007 19:15:32 GMT

PingBack from http://thachvv.wordpress.com/2007/08/05/exception-handling-best-practices-in-net/

Thachvv’s Weblog Creating Custom Exceptions in .NET «

Thachvv’s Weblog Creating Custom Exceptions in .NET « — Sun, 05 Aug 2007 20:10:56 GMT

PingBack from http://thachvv.wordpress.com/2007/08/05/creating-custom-exceptions-in-net/

Exception Best Practices - Say No To ApplicationException?

Joel Ross — Thu, 20 Sep 2007 04:19:40 GMT

Exception Best Practices - Say No To ApplicationException?

Exception Handling Best Practices in .NET

Mainz — Sun, 20 Jan 2008 12:18:07 GMT

Contrary to common belief, creating reliable, robust software is not something near to impossible. Notice that I'm not referring to bug-free software, intended to control nuclear power plants. I'm referring to common business software, which can run unattended

[.NET] Create custom Exception in .NET « MtRock.cs Paradise 16

[.NET] Create custom Exception in .NET « MtRock.cs Paradise 16 — Fri, 15 Feb 2008 10:10:59 GMT

PingBack from http://mtrockcs.wordpress.com/2008/02/15/net-create-custom-exception-in-net/

Exception: Gerne will ich einem Exception noch eine Information mitgeben | hilpers

Tue, 20 Jan 2009 19:02:34 GMT

PingBack from http://www.hilpers.com/261906-exception-gerne-will-ich-einem

MrQ (Mister Q) » Blog Archive » Exceptions in .Net

MrQ (Mister Q) » Blog Archive » Exceptions in .Net — Mon, 20 Apr 2009 08:23:07 GMT

PingBack from http://mrq.qbsoft.co.za/?p=23

?????????? ???????????? ???? ??????????????????????: ?????????? 3 - ???????????????????? ?????????????????? | DevLanfear - .NET ????????????????????

Fri, 15 May 2009 20:02:44 GMT

PingBack from http://devlanfear.com/archives/892

Brad Abrams Introducing the NET Framework Standard Library Annotated | Insomnia Cure

Tue, 09 Jun 2009 01:14:38 GMT

PingBack from http://insomniacuresite.info/story.php?id=9175