Answer by DJClayworth for Shorter naming convention for types
In general I believe in classnames that accurately describe their function, and that's it's OK to have long names. If you think the names are really getting long, what I would suggest is finding a...
View ArticleAnswer by Ask Bjørn Hansen for Shorter naming convention for types
Don't remove the vowels or something crazy like that.I'm with the "stick with the long name" people.One thought is that if the names are that awkward, maybe some deeper rethinking of the system is needed.
View ArticleAnswer by mP. for Shorter naming convention for types
Some criticisms on your naming...Why DOES your component have the word "model" in its name - isnt that a bit redundant.Since your component seems to be a messaging hub of some sort why not include...
View ArticleAnswer by Jim Petkus for Shorter naming convention for types
If you need to go through that much effort to find an alternative name, you already have the correct name. Object/method/property names should be self documenting. If they do not describe their exact...
View ArticleAnswer by Don Branson for Shorter naming convention for types
Years ago when I was in a programming class, the prof quoted the statistic that a piece of code is typically read 600 times for each single time it got modified. Nowadays, I would assume that this is...
View ArticleAnswer by Pat for Shorter naming convention for types
I would just suggest using the most concise naming that describes the object. If EventModelSocketObjectReceivedEventArgs does that, move on. My 2 cents.
View ArticleAnswer by John MacIntyre for Shorter naming convention for types
Push some of it into the namespace.For example:EventModelSocketObjectReceivedEventArgsbecomesEventModel.Sockets.ReceivedEventArgs
View ArticleAnswer by David Basarab for Shorter naming convention for types
I for one use the long name. With intellisense typing out the name isn't that important, unless you are using a 15 inch monitor.If I had to reduce the name I might go with EvtMdlSck just make the work...
View ArticleAnswer by Marc Gravell for Shorter naming convention for types
Well, are the long names hurting something?(edit) two other thoughts:use var in C# 3.0 - that'll save half the widthif you are using the type multiple times in a file, consider a type alias if it is...
View ArticleShorter naming convention for types
I am developing a framework, and some of the objects have reaaally long names. I don't really like this, but I don't like acronyms either. I am trying to come up with a shorter name for...
View Article
