I’ve always named my user controls XXXControl.ascx, but today I saw another experienced developer use “UCXXX.ascx”…I think the “UCXXX” approach is more consistent with naming Sprocs (UP_XXX, for example), but the “XXXControl” approach is more in line w/ VS’s default behavior (in VS, when you create a new control, the name is “WebUserControl.ascx”. What is the more conventional way?
I’ve always named my user controls XXXControl.ascx, but today I saw another experienced developer
Share
It mostly depends on you and what you’re comfortable with, unless the architect has decided otherwise and proposed some company standards. Both are good.
As for my personal touch, I prefer
XxxControl, as I prefer to name a labelFirstNameLabelinstead oflblFirstName.As for .NET, it sounds like the
XxxControlis the prefered approach since VS names it this way. Here are some links I hope will guide you.As for the stored procedure naming, you have to consider that database programming and object programming have quite nothing in common when it comes to standards. So I wouldn’t rely on stored procedures and database objects to name my GUI objects.