Events not firing

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Ashhad Syed - 07 Apr 2005 01:13 GMT

I am new to ASP.NET (VB) but have previously programmed a lot in VB. I am
running across a strange problem but cannot seem to figure out what is
causing it. I am curious to know if anyone else has come across the same
problem.

Essentially I will have a WebForm that is working perfectly (with lots of
code and controls on it) and then all of a sudden during the course of
development on that form the button click events and drop down list change
events, etc stop firing (ie the code behind them is not executing). The code
is still compiling fine. I even tried changing the control name, creating a
new event and then copied the previous code in the auto created event
subroutine. But I could not get the form to work. I basically had to start
with a previously saved copy of the form.

This has happened multiple times and many times I had not even changed the
already working controls or the code. However, it seems that this happens
sometimes after I add new controls to the form.

Has anyone else experienced this with the VSNET 2003? Any suggestions on how
I can debug this problem.

Reply to this Message

RK - 07 Apr 2005 16:05 GMT

Hi,
I think you are missing keywork Handles button.Click
check the button click event.

> I am new to ASP.NET (VB) but have previously programmed a lot in VB. I am
> running across a strange problem but cannot seem to figure out what is
[quoted text clipped - 16 lines]
> Has anyone else experienced this with the VSNET 2003? Any suggestions on how
> I can debug this problem.

Reply to this Message

RFPulsifer - 26 May 2005 22:48 GMT

Yes, RK, he is missing his "Handles button.click" clause. However, the real
point is that the page was working fine (indicating that the "Handles"
clauses were in place), then, all of a sudden everything stops working. What
is happening is that VS is deleting all of the Handle clauses by itself
without warning or notification. This has happen to us twice and we still do
not know why. Today's episode involved an ASP.NET page with a very lengthy
bit of code behind. In Design view I added (dragged and dropped) a button and
immediately decided that I didn't need it after all. Hitting F5 to go into
debug caused a rebuild and NOTHING was working. This project is all but
finished and we're just going through and disabling some buttons to guide the
user thru, and has been working for some weeks. After a couple of breakpoints
failed to stop the action I checked the subroutines and ALL of the "Handles
cntrl.event" clauses were gone!
The question is... this a bug, or a feature? and HOW DO WE SHUT IT OFF???
<\rant>
Anyone know? I can't find mention of this "feature" in the help files for
Visual Studio 2003. Is this Intellisense run amuck?? How can we avoid this?
We now spend more time making backups than we do writing new code as we don't
know when it will strike again.

> Hi,
> I think you are missing keywork Handles button.Click
[quoted text clipped - 20 lines]
> > Has anyone else experienced this with the VSNET 2003? Any suggestions on how
> > I can debug this problem.

Reply to this Message

Events not firing

Free Magazines