Welcome to the Lounge

OriginalGriff wrote:

It helps you at every turn: it prompts you with method names and properties, it helps remind you of function parameters, and it tells you when you misspell something as you go along. It handles indentation, and it works exactly the same when debugging as it does when you are editing.

Int32.Parse(Session["someInteger"].ToString());

• Session could be null if session state is disabled for the application or the request;
• Session["someInteger"] could be null if the session's timed out (or you've misspelled the key);
• If you stored an Int32 in Session["someInteger"], drop the .ToString / .Parse and just unbox the value;
• If you didn't store an Int32 in Session["someInteger"] (why the elephant not?!) then Int32.Parse could throw a FormatException or an OverflowException;
• Even if you did store an Int32 in Session["someInteger"], the current culture settings might^* prevent Int32.Parse from correctly parsing the result of the .ToString() call;
• If you're not already doing it, this should be hidden behind a façade class;