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

I've experienced the same problem, and find it very frustrating. This issue has seriously made me loose faith in this product, but more this has caused my client to loose faith in the product we developed for them. It makes our system seem unreliable, since this issue happens at reandom and is completely unpredicatable.

This basically means with every recompile one needs to check every button to see if it still has it's event handlers
Also looking on the microsoft site at: http://msdn.microsoft.com/vstudio/downloads/updates/datalossifx.asp

Lynn,
[quoted text, click to view]
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?

[quoted text, click to view]
As a workaround you can manually use AddHandler/RemoveHandler (in the
constructor) yourself now.

Hope this helps
Jay


[quoted text, click to view]
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.
[quoted text, click to view]
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.
[quoted text, click to view]
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.
[quoted text, click to view]
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.
[quoted text, click to view]
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.
[quoted text, click to view]