Re: Is ASP.Net a Supported Product. If so the response of this board is giving Microsoft a bad name.

From: Alex B (nospameroni_at_sparmerio.com)
Date: 05/06/04 

Date: Thu, 6 May 2004 18:06:42 -0400

How can you guys enable this guy by responding??! Search on google groups
for his name and you'll see all he does is flame a group until someone
responds ... yet has never offered help to anyone.

"Matt Berther" <mberther@hotmail.com> wrote in message
news:uU%23rEu4MEHA.1468@TK2MSFTNGP12.phx.gbl...
> Hello Burton,
>
> First off, I cant believe that I am even bothering to respond to this
thread. The arrogance that you have displayed is completely stunning. Of
course, it is more likely that the .NET framework has a bug in it than your
code. I'm sure your code has gone through countless hours of unit testing.
>
> > There is no problem with the name of the page the code is seeking to
> > branch to. It as simple as this, page "a.aspx" branches to page
> > "b.aspx". Then one clicks the prior button, and an error message
> > comes back stating that page "a.aspx" doesn't exist. Nonsense!!!
> > Page "a.aspx" is still there or I could not go back and run the test
> > over and over again. There is no complexity in the code, because the
> > failure occurs only in a single line of as ASP code. It is apparent
> > therefore, that due to some failure in .Net, it appears unable to find
> > a resource.
>
> This KB issue doesnt even remotely begin to describe your issue. In your
original post, you said nothing about using HttpContext.RewritePath. Also,
from your original post, your postback events *are* firing. The
Response.Redirect or Server.Transfer *is* occurring. They are just not
mapped to the right locations.
>
> Taken from the original post, please enter
http://localhost/ClassicClasses/MembersArea/SignInConfirm.aspx into your
browser and let me know what you get. I'd bet a dollar that you get a 404
error. At this point, you'll probably start blasting IIS, but before you do,
please locate the full path to SignInConfirm.aspx. If this page is in the
root folder, then replace your code with this:
>
> Response.Redirect("~/SignInConfirm.aspx");
>
> If it is nested in a folder hierarchy, please do something like this:
>
> Response.Redirect("~/path/to/SignInConfirm.aspx");
>
> where the path/to is replaced with the path to SignInConfirm.aspx...
>
> Now, in order to get this issue resolved for you, please make sure that
you respond to this thread with your results.
>
> > It appears that this is a known problem. In continuing to research
> > this issue, I found this Microsoft Knowledgebase Article #817036. A
> > work around is suggested, which I have not yet tested. The STATUS
> > reported is this: "Microsoft has confirmed that this is a bug in the
> > Microsoft products that are listed at the beginning of this article."
> > As of this writing, the issue has not been resolved.
>
> --
> Matt Berther
> http://www.mattberther.com