Not to start a flame war, but...

  • Thread starter Thread starter Frank Rizzo
  • Start date Start date
Hi Christoph,

Interesting.
But how about more complex controls.
For example, some 3rd party grid produces tons of wfd code.
And it is all handled by their designer which makes a breeze many tasks.
 
You can plan it on screen with forms designer, too :)
Click to expand...

Not as easily, IMO. You can't draw in the extra bits of information,
the grouping etc. You can't easily annotate it.
 
Pete said:
[snip]
Reasons:
1. Why is there no intellisense after I type an enum data type followed
by the = sign? Why do I have to type the type of the enum + “.” to get
the intellisense. I had a habit of giving enums verbose names (to make
the code self-documenting) and this habit is causing me to type one hell
of a lot more than I want to. Example:

this.WindowState = … where in the world is the intellisense. I have to
type the following to get it:
this.WindowState = FormWindowState.

This is ridiculous.
Click to expand...


Take a look at Visual Assist. It has improved intellisense. I find it
worthwhile for the intellisense improvements alone. But in the big scheme of
things, I find this to be a very minor annoyance at most and could hardly
justify changing languges over it.
Click to expand...

What's that? Where is it?
 
I think he is talking about:
http://www.wholetomato.com/va6/va6new.html

--
Miha Markic - RightHand .NET consulting & development
miha at rthand com
www.rthand.com

Frank Rizzo said:
Pete said:
[snip]
Reasons:
1. Why is there no intellisense after I type an enum data type followed
by the = sign? Why do I have to type the type of the enum + “.” to get
the intellisense. I had a habit of giving enums verbose names (to make
the code self-documenting) and this habit is causing me to type one hell
of a lot more than I want to. Example:

this.WindowState = … where in the world is the intellisense. I have to
type the following to get it:
this.WindowState = FormWindowState.

This is ridiculous.
Click to expand...


Take a look at Visual Assist. It has improved intellisense. I find it
worthwhile for the intellisense improvements alone. But in the big scheme of
things, I find this to be a very minor annoyance at most and could hardly
justify changing languges over it.
Click to expand...

What's that? Where is it?
Click to expand...
 
Erik said:
The three items you've listed are personal preferences, and pretty
indicative of the mentality of someone coming from a VB world (not meant as
a dig - just the truth).
Click to expand...

It is true that I came from VB world, but I entered it from the
C/C++/assembly background.
Actually, I'll give you item #1 - the lack of enum intellisense can be
annoying. But I guess this has been adressed.
Click to expand...

How has this been addressed? In Whidbey, you mean? In that case it
hasn't been addressed, cause I ain't programming in Whidbey and won't be
for at least a year anyway.

In any case, this is exactly why you have the option to use VB or C#.
Click to expand...

I'd love to have a third option: Brevity of C# without its
idiosyncrasies + VB productivity features.
 
Back
Top