Adding event handlers

[Lloyd Sheen]

Perhaps I am missing something or it does not exist. I am used to VB.NET
and when you have a windows form you can easily create a handler using the
drop down list. This does not seem to exist in VS2003 for C#. Double
clicking a control will bring up a stub for the "default" action.

Is there an interface in the IDE which gives this information so that I can
create the code (you know using the RAD) tool or is notepad about as useful?
I have had many problems with the IDE (icons go missing etc so if this
exists it may just be not noticed by me).

Using XP Pro, VS 2003

Lloyd Sheen

 

[David]

Perhaps I am missing something or it does not exist. I am used to
VB.NET and when you have a windows form you can easily create a
handler using the drop down list. This does not seem to exist in
VS2003 for C#. Double clicking a control will bring up a stub for the
"default" action.

Is there an interface in the IDE which gives this information so that
I can create the code (you know using the RAD) tool or is notepad
about as useful? I have had many problems with the IDE (icons go
missing etc so if this exists it may just be not noticed by me).

Click on the control in the designer window. Now, in the properties
window, click on the icon at the top that looks like a little lightning
bolt. You'll then have a list of all the events in the current control.
You can either type in the handler, or just double click the text area
and the IDE will create the handler for you.

As an aside, I really don't see why VB and C# couldn't share the same
interface here, especially now that we have essentially version 2.0 of
Visual Studio.NET.

 

[Lloyd Sheen]

Thanks, and I totally agree. All the hype about the platform seems to have
forgotten that all the dot.net languages should share a common interface or
the idea of a common IDE is lost.

Lloyd Sheen

 

[Vijaye Raji]

The idea of a platform that's common for all languages still exists. The
issue here is, Visual Studio IDE has not caught up with the commonality
exposed by .Net Framework.

There are a few good reasons for this. You cannot expect a Visual Basic
programmer to completely change his/her style of programming and learn
everything overnight to cope up with a platform change.

The common interface is still in the pipeline and will be here when Whidbey
(the next version of Visual Studio) is out.

-vJ

Thanks, and I totally agree. All the hype about the platform seems to have
forgotten that all the dot.net languages should share a common interface or
the idea of a common IDE is lost.

Lloyd Sheen

 

[David]

The idea of a platform that's common for all languages still exists.
The issue here is, Visual Studio IDE has not caught up with the
commonality exposed by .Net Framework.

There are a few good reasons for this. You cannot expect a Visual
Basic programmer to completely change his/her style of programming and
learn everything overnight to cope up with a platform change.

It's not a big deal, but adding the events icon to the property window
in VB.NET wouldn't force anybody to change their style of programming,
and ditto for adding events to the text editor drop-down boxes in C#.

I understand they're different products and different teams, but if you
have to switch between VB and C# on a regular basis some of the
differences just seem gratuitous. Things like the lack of build events
in VB just seem strange, but things like the subtle differences in
intellisense drive me batty on a daily basis.