ASP.NET 2005 Postback Madness

[Shawn B.]

Greetings,

We have a very large web application (300+ pages) (insurance software) that
was ported from ASP.NET 1.1 to 2.0 via the Web Application Project add-in.
There are some pages that the postbacks inexplicably don't function as
intended. What happens is the postbacks do one of two things: 1) they act
like a redirect and request the same page losing the query string parameters
and the IsPostBack registers as false or 2) the attempt to do a proper
postback but the ASP.NET engine throws an exception stating something to the
effect of there not being a postback event handler or something (I don't
remember the details).

With regards to #1, the only way to correct the problem I've found thus far
is to create the page from scratch and not copy/paste any of the HTML. But
that isn't feasible, there are too many pages and these pages are
complicated pieces of "art" such that it is impracticle to rewrite the
entire application.

Does anyone here know what the cause of the problem is and perhaps a better
way to solve it?
Thanks,
Shawn

[Cowboy \(Gregory A. Beamer\)]

Consider the web application project (www.asp.net) with 1.1 apps going to
2.0. It compiles the same way and reduces issues.

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
http://gregorybeamer.spaces.live.com

*************************************************
Think outside of the box!
*************************************************
"Shawn B." <le****@html.comwrote in message
news:ex**************@TK2MSFTNGP04.phx.gbl...

Greetings,

We have a very large web application (300+ pages) (insurance software)
that was ported from ASP.NET 1.1 to 2.0 via the Web Application Project
add-in. There are some pages that the postbacks inexplicably don't
function as intended. What happens is the postbacks do one of two things:
1) they act like a redirect and request the same page losing the query
string parameters and the IsPostBack registers as false or 2) the attempt
to do a proper postback but the ASP.NET engine throws an exception stating
something to the effect of there not being a postback event handler or
something (I don't remember the details).

With regards to #1, the only way to correct the problem I've found thus
far is to create the page from scratch and not copy/paste any of the HTML.
But that isn't feasible, there are too many pages and these pages are
complicated pieces of "art" such that it is impracticle to rewrite the
entire application.

Does anyone here know what the cause of the problem is and perhaps a
better way to solve it?
Thanks,
Shawn

[Shawn B.]

Consider the web application project (www.asp.net) with 1.1 apps going to

2.0. It compiles the same way and reduces issues.

yes, I'm using this utility and I believe the problem I'm experiencing is a
defect with WAP but maybe not. In any case, I'm wondering if someone else
has experienced this and knows a much more suitable workaround than the only
one I know of that solves the problem.
Thanks,
Shawn

[James Geurts]

If you had AutoEventWireup set to false w/ the 1.1 version, I would look at
that. The conversion utility changes AutoEventWireup to true by default and
your Page_Load handlers might be getting called twice. Just something to
look into...

Jim
"Shawn B." wrote:

Greetings,

We have a very large web application (300+ pages) (insurance software) that
was ported from ASP.NET 1.1 to 2.0 via the Web Application Project add-in.
There are some pages that the postbacks inexplicably don't function as
intended. What happens is the postbacks do one of two things: 1) they act
like a redirect and request the same page losing the query string parameters
and the IsPostBack registers as false or 2) the attempt to do a proper
postback but the ASP.NET engine throws an exception stating something to the
effect of there not being a postback event handler or something (I don't
remember the details).

With regards to #1, the only way to correct the problem I've found thus far
is to create the page from scratch and not copy/paste any of the HTML. But
that isn't feasible, there are too many pages and these pages are
complicated pieces of "art" such that it is impracticle to rewrite the
entire application.

Does anyone here know what the cause of the problem is and perhaps a better
way to solve it?
Thanks,
Shawn