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

From: Raterus (raterus_at_spam.org)
Date: 05/05/04 

Date: Wed, 5 May 2004 12:22:36 -0400

Thanks, I needed a good laugh today. That's a good one, rant about the lack of help you found on the newsgroup, then ask a question, but when you get to the problem, begin ranting again. Btw, no one is guranteed a response here, people that don't get responses are either a) clueless, and they post so much meaningless detail about their problem, people don't have time to wade through it all. aka YOU b) we're not free consulants, who will design your entire application for you. c) you were truly overlooked d) We don't like you

It's sounds to me that your problem is your problem, not asp.net's. You are clearly redirecting to a page that doesn't exist. Do you understand relative pathing?, are you sure you can just simple put Response.Redirect("SignInConfirm.aspx"), or is this resource in another folder, where you may have to do something like this. Response.Redirect("../anotherfolder/SignInConfirm.aspx") Did you spell it correctly?

If you want a response you need to establish yourself to the would-be volunteer readers that you are credible enough to have done these things! I don't think you have, you've immedately blamed it on Forms-Authentication and started bashing Microsoft, something I don't see how it could be related.

--Michael

"Burton Wilkins" <burton_wilkins@att.net> wrote in message news:D12311F7-18AD-460A-82C6-198171D77356@microsoft.com...
> Dear Community:
>
> Two days ago, I asked a reasonable question here on Microsoft's discussion board. I never got an answer, and from what I can see there are a lot of others posting questions and not really getting answers either. By an answer, I mean a response that deals with or offers a solution to a problem. An answer is for the one who asks not another question.
>
> ASP3 was such a poorly supported product, with so many problems, that Microsoft was on the verge of being served a class action suit because of perceived damages development companies and their investors suffered at the hands of Microsoft. Had that had happened, there would have been no Microsoft today. Microsoft did in fact have a hand in the .Com crash, and that contribution was ASP3. ASP3 had to be quickly replaced in the market quickly, and thus this was one of the key reasons for rushing .Net into Beta. Microsoft's existance as a corporation was at stake. .Net could be a good product, but if those running Microsoft's discussion board reduce it's product once again to mere beurocratic neglect, Microsoft will loose market share.
>
> If their are bugs in your product, try honest for a change. Admit to them. Don't waste developers time by allowing developers to pursue directions which you already know won't work. Benign neglect in this fashion is nothing more than stealing from your own customer base, as well as being cowardly and gutless. In short get your acts together, because you don't want to see this posting sent on to corporate.
>
> Now I am going to restate this issue and I expect a response other than foolishness.
>
> =============================================================================
>
> In ASP.Net, I would like to create something like a Wizard. The Web site is using forms-based authentication. That is one page leads to another page and to another page, with three buttons on the bottom of each page: Prior, Cancel, and Next as with most Wizards. However, when I click the “Prior” button that leads back to the previous ASP (possibly thus a Parent) page, I get this error whether I use a “Server.Transfer” or a “Response.Redirect”. Now the code which is blowing up is all but trivial. The Response.Redirect approach is as follows:
>
> Private Sub btnPrior_Click(ByVal sender As System.Object, ByVal e As System.Web.UI.ImageClickEventArgs) Handles btnPrior.Click
>
> Response.Redirect("SignInConfirm.aspx")
>
> End Sub
>
> If the Server.Transfer approach is this:
>
>
> Private Sub btnPrior_Click(ByVal sender As System.Object, ByVal e As System.Web.UI.ImageClickEventArgs) Handles btnPrior.Click
>
> Server.Transfer("SignInConfirm.aspx")
>
> End Sub
>
> Now here is the issue. If forms-based authentication is so buggy and week that it can't even handle a simple Response.Redirect or Server.Transfer to a prior page, then it is no product at all and we who are developers will seek alternate approaches. If that's the case, say so. Don't waste our time our the salaries of the companies who employ us. If you don't know, (a) take it to your supervisor, (b) escalate the case and (c) have a second response unit deal with the issue. If in fact forms-based authentication is this shallow, (d) do your company a favor and pass the issue on to developement and their management with instructions to clean up their mess. Show some backbone. Try being relavent. It may help to justify your salaries. As I mentioned in my my earlier posting, I checked Google on this issues, and there seems to be MANY messages by programmers on message boards all reporting the same problem, and nobody seems to have an answer. For Microsoft's support to stick it's head in the sand, and act like nobody knows what's going on is realy quite stupid. The word gets around and such incompetance in handling issues will hurt your company's share value. Answer this posting, and answer it responsibly.
>
>
> When Response.Redirect errors out, here is the message returns:
>
> Server Error in '/ClassicClasses/MembersArea' Application.
> ----------------------------------------------------------------------------
> ----
>
> The resource cannot be found.
> Description: HTTP 404. The resource you are looking for (or one of its
> dependencies) could have been removed, had its name changed, or is temporarily unavailable. Please review the following URL and make sure that it is spelled correctly.
>
> Requested Url: /ClassicClasses/MembersArea/SignInConfirm.aspx
>
> If the “Server Transfer” statement is used, the error message is this:
>
> If the “Server Transfer” statement is used, the error message is this:
>
> For Server.Transfer - this is the Error. ============================================================================
> ===========================
>
> Server Error in '/ClassicClasses/MembersArea' Application.
> ----------------------------------------------------------------------------
> ----
>
> Error executing child request for SignInConfirm.aspx.
> Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
>
> Exception Details: System.Web.HttpException: Error executing child request for SignInConfirm.aspx.
>
> Source Error:
>
>
> Line 164:
> Line 165: Server.Transfer("SignInConfirm.aspx")
> Line 166: 'Response.Redirect("SignInConfirm.aspx")
> Line 167:
>
>
> Source File: c:\inetpub\wwwroot\ClassicClasses\MembersArea\NewMember.aspx.vb
> Line: 166
>
> Stack Trace:
>
>
> [HttpException (0x80004005): Error executing child request for SignInConfirm.aspx.]
> System.Web.HttpServerUtility.ExecuteInternal(String path, TextWriter writer, Boolean preserveForm)
> System.Web.HttpServerUtility.Transfer(String path, Boolean preserveForm)
> System.Web.HttpServerUtility.Transfer(String path)
> MembersArea.NewMember.btnPrior_Click(Object sender, ImageClickEventArgs
> e) in c:\inetpub\wwwroot\ClassicClasses\MembersArea\NewMember.aspx.vb:166
> System.Web.UI.WebControls.ImageButton.OnClick(ImageClickEventArgs e)
>
> System.Web.UI.WebControls.ImageButton.System.Web.UI.IPostBackEventHandler.Ra
> isePostBackEvent(String eventArgument)
> System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler
> sourceControl, String eventArgument)
> System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData)
> System.Web.UI.Page.ProcessRequestMain()
>