This is just a quick little rant on my part. In my opinion a property should be used for simply getting/setting of a value. You should NOT have any logic inside your getter/setter (ok, I will add a 'caviot' to this rule and say that I am ok with doing string formatting on the getter). If you...
I just read Ron Jefferies latest post entitled My Named Cloud is Better Than Your Named Cloud and it got me riled up enough to post something I've been meaning to write about for at least a couple of years. His post touches on the point I'd wanted to make, but doesn't quite say it as simply...
I know this may seem like old hat to many, but trust me not all organizations/projects are setup to allow you to easily pull the code from your source repository and compile. I know it is sad, but if you ask me, this is just the tip of the ice burg in terms of what is ultimately wrong with our...
Before I get started, I personally am a fan of using #regions in my code. I think it cleans up everything, allowing me to only see what I want to see. I also know that many of you disagree with me, and that is fine. Here are 2 posts that voice their disapproval for regions if you are interested...
Today I was refactoring some sql procs along with the corresponding .net code that called the procs. My primary focus was to implement some new business rules (ways to get totals) in the proc. In doing so, I completely re-wrote the proc. In the end the return values (column names) were the...
Pretty much any developer with half a brain (or any real world experience) knows that you MUST keep your source code in some sort of source code repository. There are many of them out there, VSS, Vault, TFS, CVS, SVN, the list goes on. If putting your code (C#, C++, VB, etc) into a source control system...