Re: Complaint about Visual Basic IDE with ASP.net: Removal of Event Handlers

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Jay B. Harlow [MVP - Outlook] (Jay_Harlow_MVP_at_msn.com)
Date: 02/19/04


Date: Thu, 19 Feb 2004 08:00:58 -0600

Lynn,
> I want to make a complaint about the Visual Basic.Net
> IDE with ASP.net mode. The target of this complaint
> is the removal of event handlers from code behind pages
> unkown to my self which has caused me embarsement
> and my client loss of business.
Did you test your app after you modified it?

My understanding is this was fixed in VS.NET 2003. Are you using VS.NET 2002
or VS.NET 2003?

> It would also be nice if support would provided
> for using addhandler/removehandler for event
> mapping in the constructor. Preferably, one could
> switch between 'explicit' and 'implict' event handling
> this would be a very good option.
As a workaround you can manually use AddHandler/RemoveHandler (in the
constructor) yourself now.

Hope this helps
Jay

"Lynn Eriksen" <lynn@soundworks.com> wrote in message
news:8C5130FE-D2D6-4830-942F-0C91810D0304@microsoft.com...
> I want to make a complaint about the Visual Basic.Net IDE with ASP.net
mode. The target of this complaint is the removal of event handlers from
code behind pages unkown to my self which has caused me embarsement and my
client loss of business.
>
> Recently, I needed to add a Use Control containing copy right information
to the bottom of severl ASP.net web pages written in VisualBasic.net. The
user control was written as text in a .ascx file and drag/dropped to the
bottom of the page. No other controls on the pages were altered or moved.
During the course drag/dropping the user control, several event handlers on
sporadic were removed from there target members in the code behind page.
This created a 'broken' applicaton. No notice was given that these event
handlers were removed at the time that the user control was simply draged to
the bottom of the page.
>
> I find this behavior unnacceptable and I request that in the future that
notification be given that handlers have been removed, that possible broken
handlers be allowed to remain and to as to show an error in the IDE.
Intellisense is great, and I enjoy the feature. However, for it to be truly
reliable, it should not take away code or to think for me. How can a person
track what is broken if there is notification, or even an error? In fact,
since I did not move or rename my controls, the application would not have
broken if the IDE would not have erroneouly removed event handlers.
>
> It would also be nice if support would provided for using
addhandler/removehandler for event mapping in the constructor. Preferably,
one could switch between 'explicit' and 'implict' event handling this would
be a very good option.
>
> I do want to congratulate you on making a nice product that I have come to
enjoy and rely on, but I also must note that I find that feature of removing
handlers annoying at best and detramental at worst. I very much appreciate
Intellisense helping me write code; Intellisense taking away code is
unnacceptable.
>



Relevant Pages

  • Complaint about Visual Basic IDE with ASP.net: Removal of Event Handlers
    ... I want to make a complaint about the Visual Basic.Net IDE with ASP.net mode. ... The target of this complaint is the removal of event handlers from code behind pages unkown to my self which has caused me embarsement and my client loss of business. ...
    (microsoft.public.vsnet.ide)
  • Re: Mouse events not firing for constituent controls?
    ... user control using the "Public Event eventname", ... identical blocks, where the functionality previously was repeated on many ... I've got the event handlers in place (as part of the UC ... to do to get my PictureBox to respond to mouse events? ...
    (microsoft.public.vb.general.discussion)
  • RE: Using BackgroundWorker in a browsers hosted user control
    ... When the user control is used in a Windows application, ... ProgressChanged and RunWorkerComplete event handlers are executed by the UI ... RunWorkerComplete event handlers seem to be executed by the background work ... thread which executes the DoWork event handler. ...
    (microsoft.public.dotnet.framework.clr)
  • Re: Sorry, but not happy with D2007
    ... So it seems that the first solution is to make sure the IDE is very ... It's probably the most stable Delphi I've ever ... put stubs in the event handlers that I believe I'll need so that I ... Because you 'automatically' remove all empty events, ...
    (borland.public.delphi.non-technical)
  • Re: Upgrade Anxiety
    ... Like Tom, I've taken to adding variables by directly writing DDX_Control calls, because I ... don't have the patience to wait for the IDE to do it. ... reason I would want to start typing code until I've added all the event handlers! ...
    (microsoft.public.vc.mfc)