do you already see an inconsistency?:D

a little tip:
5. Use positive logic for your variable names instead of negative logic.

In that case, I’d prefer to declare only the int variable, for the QueryString won’t be modified among these lines, or to use more descriptive names:

int customerId;
int.TryParse(Request.QueryString["cid"], out customerId);

The key thing about hungarian notation isn’t types it’s context.

So in joel’s example he talks about strings that come from the user and have yet to be santised should begin with ‘us’. Strings that have been sanitised for cross site scripting attacks have the prefix ’s’.

So 2 strings usUsername and sUsername are the same type and most likely will have exactly the same data. However they have now some notion of context. A safe context and unsafe context.

Another example is desktop environment that has a window Foo within in. Within Foo is another window called Bar. Bar has 4 variables that represent the XY position within Foo and within the main desktop. They are t_x, t_x, p_x, p_y. The convention would be that the t means the xy position applies to the topmost window. It also states that p means that x and y apply to the xy position in the immediate parent.

In reality, hungarian notation is required far less in an object orientated system than it appears, misused, in most code bases.