"Joseph M. Newcomer" <newcomer@flounder.com> wrote in message
I saw that; I hope I never have to actually look at the source, because
I
suffer from a
condition called "Pascalepsy", which is characterized by falling to the
floor and foaming
at the mouth at the sight of Pascal code (I once maintained 11,000 lines
of some of the
worst-written Pascal code anyone had ever constructed; I slowly rewrote
it
into something
that was maintainable. For example, any Pascal code that uses 'with' is
unreadable and
unmaintainable; my first stage of rewriting was to remove, one at a
time,
every 'with'
clause I came across doing maintenance, then one weekend I killed them
ALL). When you
combined the defects of the programmer with the defects of the langauge,
the result was
over a year of pain.
joe
On Wed, 9 Sep 2009 19:50:05 -0700, "David Ching"
<dc@remove-this.dcsoft.com> wrote:
"r norman" <r_s_norman@comcast.net> wrote in message
news:kk25a557fld89l2oj32g41ajfo3sr1dp7v@4ax.com...
Naming a control in dotNet with an informative name is easily done at
the time of creation in the design phase -- when you first drag it
onto the dialog screen. From then on, you have no problems. If you
use the default names first in various places in the code and later
change the name, you do have problems. I find that behavior
acceptable.
Really? I never found that behavior; I would just right click on the
variable in the C# code and select Rename, and it would change the name
of
both the variable in my source code and also in the form (since the form
is
defined in a code-behind C# file and it's just as easy to change code in
that as in the file containing my code).
Perhaps this was offered by the Resharper or Visual Assist plug-in, but
I
really think it is natively there in VS2008 also.
-- David
Joseph M. Newcomer [MVP]
email: newcomer@flounder.com
Web: http://www.flounder.com
MVP Tips: http://www.flounder.com/mvp_tips.htm