August 2005 Entries
A last minute change was done with .Net 2.0 nullable types. Read it here. Glad they did it
As a regular member of the local MS forum here in our place, I felt that I am always the "bad guy" when answering post. Well maybe because I am a new comer unlike most of the people there. I always got flamed when opposing to these ideas: Architecture - That having the connection string in the client (Win Form) or putting all those SqlCommands in the UI (Web/Win) is the correct way of doing things. - That using a WEB SERVICE to manage/centralize the connection string is the way to go. - That SQLHelper...
int? i = null; object obj = "some string..."; obj = i; if (obj == null) { MessageBox.Show("true..."); } else { MessageBox.Show("false..."); } OK, why is it that obj == null is false? Is it because i is a value type and obj is an object type? I don't think it's because the variable i is a value type since this will defeat the purpose of nullable types