I'm working on a web site that contains a button. Originally, this button had an event handler that performed some processing and then called
, which in turn caused the current page to be replaced with the file being written. This was not the desired behavior, so I added a
element to bring up the other page in a new window. Imagine my dismay to discover that specifying a
causes the page to NOT fire the Click event for the button.
My work around is comprised of two steps:
0) In the page being navigated FROM, move the code out of the event handler into a public method.
1) In the page being navigated TO, add the following line to the
or for VB:
I've been paid as a programmer since 1982 with experience in Pascal, and C++ (both self-taught), and began writing Windows programs in 1991 using Visual C++ and MFC. In the 2nd half of 2007, I started writing C# Windows Forms and ASP.Net applications, and have since done WPF, Silverlight, WCF, web services, and Windows services.
My weakest point is that my moments of clarity are too brief to hold a meaningful conversation that requires more than 30 seconds to complete. Thankfully, grunts of agreement are all that is required to conduct most discussions without committing to any particular belief system.