Browse by Tags

single letter variable names

If j(i) < 1 Then m = m + j(i - 1) Else m = m + j(i - 1) - 1 Single letter variables are good for iterators, but if integer variables will involve coditions such as the statement above, better use a more descriptive variable or refactor the said line...

Published Mon, Jan 01 2007 11:37 AM by jokiz

Filed under: techie, design guidelines

to derive or not to derive from ApplicationException

remember the rule to always derive custom exceptions from ApplicationException? so you thought that the CLR never throws an ApplicationException? Krzysztof Cwalina (co-author of Brad Adams in the famous Framework Design Guidelines book) blogs about the...

Published Tue, Jun 06 2006 10:13 PM by jokiz

Filed under: .NET, design guidelines

Do not call overridable methods in constructors

I noticed that Resharper 2.0 highlighted (meaning it is against a rule) a call to a virtual method in a constructor in one of my business objects. It gave me the following information information in msdn ( http://msdn2.microsoft.com/en-us/library/ms182331...

Published Thu, May 05 2006 9:12 PM by jokiz

Filed under: .NET, design guidelines, resharper

String Property construct

anybody who is also using this construct for string properties? we rarely want our string properties to be null and since it is a reference type, we have to have handling for it. can you see any disadvantage of such construct? [code language="C#"] public...

Published Tue, Apr 04 2006 12:25 PM by jokiz

Filed under: .NET, design guidelines

TDS Protocol

For most of you who have been using stored procedures and following the MS guidelines in .NET Application Development, you must have been using SET NOCOUNT ON as stated in Chapter 12 of the Improving .NET Application Performance and Scalability . Although...

Published Sun, Feb 02 2006 2:24 AM by jokiz

Filed under: .NET, SQL, design guidelines

Naming Guidelines

In response to dehranph's comment on my previous post ( http://community.devpinoy.org/blogs/joeycalisay/archive/2005/11/08/401.aspx ), it reminded me of the naming guidelines in .NET. His comment was about the DeleteCustomer method which has a Customer...

Published Thu, Nov 11 2005 12:16 AM by jokiz

Filed under: .NET, design guidelines

OOP-Encapsulation issues

As I was refactoring some of our codes, what struck me was the idea of object oriented programming particularly encapsulation. For example, we have this Customer object which is distinct with its CustomerID property. We needed to have versioning for the...

Published Tue, Nov 11 2005 11:14 PM by jokiz

Filed under: .NET, design guidelines, oop

ArgumentNullException - API design hall of shame

I have read this before but just want to make a permanent reference to it in this blog. Brad Adams explains why the ArgumentNullException class violates the Design Guidelines here for not following the exception constructor patterns. http://blogs.msdn...

Published Wed, Jun 06 2005 9:21 AM by jokiz

Filed under: .NET, design guidelines

Designing .NET Class Libraries Series

I've seen a part of this (Brad Adams presentation on Naming) perhaps a month ago, I just discovered that it is a part of a good set of webcasts worth seeing. Can't wait to see Brian Pepin's presentation (design time guru). http://msdn.microsoft.com/netframework...

Published Mon, Apr 04 2005 6:30 PM by jokiz

Filed under: .NET, design guidelines

Code Complete 1st edition

I was reading Steve McConnell's first edition of Code Complete and the book is highly recommended. Although the sample uses old languages like pascal and c, and some topics does not apply to current programming languages, I love the way he presents his...

Published Thu, Apr 04 2005 6:18 PM by jokiz

Filed under: .NET, design guidelines

Hungarian Notation

I started programming with C and used Hungarian notation since then. It was very helpful back then to instantly know what type the variable is from its name. When I started programming in .NET using Visual Studio, Intellisense made a major breakthrough...

Published Tue, Mar 03 2005 8:42 AM by jokiz

Filed under: .NET, design guidelines

Property Naming WTF

I got tired of seeing a common property of our controls (since it is part of an interface) and this week, I got fed up and can’t take it anymore seeing them. AlignmentInContainer You might suggest ContainerAlignment but layout properties obviously relates...

Published Fri, Mar 03 2005 3:53 PM by jokiz

Filed under: .NET, design guidelines, controls, rants

Rethrowing exceptions, the right way

I have read the Exception Handling Best Practices article in .NET in CodeProject and all this time I thought that rethrowing exceptions is this way: [code language="C#"] try { // Some code that throws an exception } catch (Exception ex) { // some code...

Published Mon, Feb 02 2005 3:04 PM by jokiz

Filed under: .NET, techie, tips, best practices, design guidelines, exceptions

Syndication

Recent Posts

Tags

News

Archives

single letter variable names

to derive or not to derive from ApplicationException

Do not call overridable methods in constructors

String Property construct

TDS Protocol

Naming Guidelines

OOP-Encapsulation issues

ArgumentNullException - API design hall of shame

Designing .NET Class Libraries Series

Code Complete 1st edition

Hungarian Notation

Property Naming WTF

Rethrowing exceptions, the right way