P
psb
about a year ago, I was head deep in vb6/com+ hell. THEN, I started doing
asp.net development and went the opposite direction by only putting
transactions in the stored procs. Unfortunately, I can't isolate everything
in one db call. I started testing the Transaction=txType attribute in the
Page directive.
<%@ Page Language="vb" Transaction="Required"....%>
This page is basically a couple of datagrids (parent/child) and viewstate is
enabled for all elements on the page. I am having some strange problems.
When it errors out, I do a
Throw New Exception(strErrorMsg).
This causes the page to go to the ErrorPage.aspx defined in the web.config.
When I click the back button or type the URL and refresh the original aspx
page, I get another error, "Cannot execute transacted code" I can't execute
the page at all from anywhere. It is like this until IISRESET. I have read
in a few places that calling the SetComplete()/SetAbort() is not needed, but
something is hanging IIS out to dry.
has anyone had any problems similar to this??
~PSB
asp.net development and went the opposite direction by only putting
transactions in the stored procs. Unfortunately, I can't isolate everything
in one db call. I started testing the Transaction=txType attribute in the
Page directive.
<%@ Page Language="vb" Transaction="Required"....%>
This page is basically a couple of datagrids (parent/child) and viewstate is
enabled for all elements on the page. I am having some strange problems.
When it errors out, I do a
Throw New Exception(strErrorMsg).
This causes the page to go to the ErrorPage.aspx defined in the web.config.
When I click the back button or type the URL and refresh the original aspx
page, I get another error, "Cannot execute transacted code" I can't execute
the page at all from anywhere. It is like this until IISRESET. I have read
in a few places that calling the SetComplete()/SetAbort() is not needed, but
something is hanging IIS out to dry.
has anyone had any problems similar to this??
~PSB