| Groups | Blog | Home |
dotnet general : Posting to another page attribute: PostTargetUrl
For this control below, <asp:Button runat="server" PostTargetUrl="page2.aspx" /> The Attribute: PostTargetUrl="page2.aspx" Is this PostTargetUrl Attribute going to be available in the <a> and Html Controls as well as opposed to just the <asp:Button> control? Lots of other controls, HTML controls, <a>, <img>, etc, would like to used to post forward....
Setting the form action attribute just isn't the ASP.NET way.
Of course there are a number of ways to pass values from one page to another, such as using the querystring, cookies, session, context, saving to a temporary table in the database between each page, etc. You'll have to decide which technique is best for your application. Here are several good articles on the subject to help you decide. http://msdn.microsoft.com/msdnmag/issues/03/04/ASPNETUserState/default.aspx http://www.aspalliance.com/kenc/passval.aspx http://www.dotnetjunkies.com/tutorials.aspx?tutorialid=600 http://www.dotnetbips.com/displayarticle.aspx?id=79 Here's one nice, simple way to pass values from one page to another: 'Add data to the context object before transferring Context.Items("myParameter") = x Server.Transfer("WebForm2.aspx") Then, in WebForm2.aspx: 'Grab data from the context property Dim x as Integer = CType(Context.Items("myParameter"),Integer) -- I hope this helps, Steve C. Orr, MCSD, MVP http://Steve.Orr.net Hire top-notch developers at http://www.able-consulting.com [quoted text, click to view] "anon" <anon@hotmail.com> wrote in message news:u2oi0$E6DHA.3664@tk2msftngp13.phx.gbl... > Post Forwarding question...... > > For this control below, > > <asp:Button runat="server" PostTargetUrl="page2.aspx" /> > > The Attribute: PostTargetUrl="page2.aspx" > > Is this PostTargetUrl Attribute going to be available in the <a> and Html > Controls as well as opposed to just the <asp:Button> control? > > Lots of other controls, HTML controls, <a>, <img>, etc, would like to used > to post forward.... > >
Yes, but setting the form action attribute is the BEST way to pass
information page to page. <asp:Button runat="server" PostTargetUrl="page2.aspx" /> The Attribute: PostTargetUrl="page2.aspx" It's fastest way and most simpliest way for form data next to like the querystring. It's definately K.I.S.S. type of architecture. It's got the best performance on an enterprise level or any level for that matter And it works, plain and simple. All of those other ways are messy hacks that have drawbacks one way or another and can makes your code far far more complicated than what it should be. All the other languages can do it this way, except .NET and because of that, it's a pain in the a** to get real life questionairre form data into a database. The fact that MS is addressing this issue head on is a testament to this major major screwup Now, let's get back to the ORIGINAL question... is PostTargetUrl going to be in the other HTML controls? That's what's important here and let's not SCREW it up like MS did with 1.0 and 1.1 [quoted text, click to view] "Steve C. Orr [MVP, MCSD]" <Steve@Orr.net> wrote in message news:ugeKxCF6DHA.504@TK2MSFTNGP11.phx.gbl... > Setting the form action attribute just isn't the ASP.NET way. > > Of course there are a number of ways to pass values from one page to > another, such as using the querystring, cookies, session, > context, saving to a temporary table in the database between each page, etc. > You'll have to decide which technique is best for your application. > Here are several good articles on the subject to help you decide. > http://msdn.microsoft.com/msdnmag/issues/03/04/ASPNETUserState/default.aspx > > http://www.aspalliance.com/kenc/passval.aspx > > http://www.dotnetjunkies.com/tutorials.aspx?tutorialid=600 > > http://www.dotnetbips.com/displayarticle.aspx?id=79 > > Here's one nice, simple way to pass values from one page to another: > > 'Add data to the context object before transferring > Context.Items("myParameter") = x > Server.Transfer("WebForm2.aspx") > > Then, in WebForm2.aspx: > > 'Grab data from the context property > Dim x as Integer = CType(Context.Items("myParameter"),Integer) > > -- > I hope this helps, > Steve C. Orr, MCSD, MVP > http://Steve.Orr.net > Hire top-notch developers at http://www.able-consulting.com > > > > "anon" <anon@hotmail.com> wrote in message > news:u2oi0$E6DHA.3664@tk2msftngp13.phx.gbl... > > Post Forwarding question...... > > > > For this control below, > > > > <asp:Button runat="server" PostTargetUrl="page2.aspx" /> > > > > The Attribute: PostTargetUrl="page2.aspx" > > > > Is this PostTargetUrl Attribute going to be available in the <a> and Html > > Controls as well as opposed to just the <asp:Button> control? > > > > Lots of other controls, HTML controls, <a>, <img>, etc, would like to used > > to post forward.... > > > > > >
I have to disagree with you. Processing forms is a simple matter now with
..NET and you no longer for to push people to another page just to save off the data. That is something I would consider more of a hack. In .NET it is a simple matter to respond to the OnClick event, which your validators will have validated the form and you are ready to process that data from simple server controls and store in the database. If any errors occur you have not left he page yet and can update a status field on the form informing them of the error while all their data is preserved. Once the data is successfully stored, you simply do a transfer to send them to a result page if you so desire or back to the main page. It really does not get much easier than this. And the process keeps all your server controls hooked for easy processing not to mention keeping your code clean only having to deal with a single page. The processing of regular form data has been a pain in the tush for over a decade! -- Rocky Moore www.HintsAndTips.com - Share your tips with the world! ~~~~~~~~~ Developer Tips Welcome! ~~~~~~~~~ [quoted text, click to view] "anon" <anon@hotmail.com> wrote in message news:#94R5ZJ6DHA.2480@TK2MSFTNGP12.phx.gbl... > Yes, but setting the form action attribute is the BEST way to pass > information page to page. > > <asp:Button runat="server" PostTargetUrl="page2.aspx" /> > The Attribute: PostTargetUrl="page2.aspx" > > It's fastest way and most simpliest way for form data next to like the > querystring. > It's definately K.I.S.S. type of architecture. > It's got the best performance on an enterprise level or any level for that > matter > And it works, plain and simple. > > All of those other ways are messy hacks that have drawbacks one way or > another and can makes your code far far more complicated than what it should > be. > > All the other languages can do it this way, except .NET and because of that, > it's a pain in the a** to get real life questionairre form data into a > database. > > The fact that MS is addressing this issue head on is a testament to this > major major screwup > > Now, let's get back to the ORIGINAL question... is PostTargetUrl going to be > in the other HTML controls? That's what's important here and let's not SCREW > it up like MS did with 1.0 and 1.1 > > > > > "Steve C. Orr [MVP, MCSD]" <Steve@Orr.net> wrote in message > news:ugeKxCF6DHA.504@TK2MSFTNGP11.phx.gbl... > > Setting the form action attribute just isn't the ASP.NET way. > > > > Of course there are a number of ways to pass values from one page to > > another, such as using the querystring, cookies, session, > > context, saving to a temporary table in the database between each page, > etc. > > You'll have to decide which technique is best for your application. > > Here are several good articles on the subject to help you decide. > > > http://msdn.microsoft.com/msdnmag/issues/03/04/ASPNETUserState/default.aspx > > > > http://www.aspalliance.com/kenc/passval.aspx > > > > http://www.dotnetjunkies.com/tutorials.aspx?tutorialid=600 > > > > http://www.dotnetbips.com/displayarticle.aspx?id=79 > > > > Here's one nice, simple way to pass values from one page to another: > > > > 'Add data to the context object before transferring > > Context.Items("myParameter") = x > > Server.Transfer("WebForm2.aspx") > > > > Then, in WebForm2.aspx: > > > > 'Grab data from the context property > > Dim x as Integer = CType(Context.Items("myParameter"),Integer) > > > > -- > > I hope this helps, > > Steve C. Orr, MCSD, MVP > > http://Steve.Orr.net > > Hire top-notch developers at http://www.able-consulting.com > > > > > > > > "anon" <anon@hotmail.com> wrote in message > > news:u2oi0$E6DHA.3664@tk2msftngp13.phx.gbl... > > > Post Forwarding question...... > > > > > > For this control below, > > > > > > <asp:Button runat="server" PostTargetUrl="page2.aspx" /> > > > > > > The Attribute: PostTargetUrl="page2.aspx" > > > > > > Is this PostTargetUrl Attribute going to be available in the <a> and > Html > > > Controls as well as opposed to just the <asp:Button> control? > > > > > > Lots of other controls, HTML controls, <a>, <img>, etc, would like to > used > > > to post forward.... > > > > > > > > > > > >
This where you are really clueless in the real world.
First, if you have a decent size form page and your post right back to the same page, the user can't find where the mistake is; especially is every other things is marked in red, *required Forms that are challenging also span several pages long....if you have a single page, that's a complete nightmare anyway you look at it. Second, IIS logging tells a lot without having to do this at a database...doing it your way is a perfomance hit. Third, the validation controls are pointless, they are not practically in the real world...maybe a simple for like signing up for a Hotmail account is good for you. But that form asks your for hardly any important information anyway. Fourth, if you have any important information to be inserted into a database it still has to validated service side anyway. It pays to have a separate validation page that can be a lot more intelligent to tell the users what's wrong and also on the server to initialize more validation routines for security hacks and more help for the user. I can go on and on, but I don't....almost ALL .NET top notch guru authors developers SUCK at web development anyway......they have poor user interface skills and can't communicate to the common user if their life depended upon it....look at the failure of adoption of ASP.NET in the real world...Mr. Gates said it himself..".NET is slow going" and took 3 years to get to this point to have a decent list of .NET examples. The fact that Microsoft's ASP.NET 2.0 is directly addressing this need to post to another page shows you how clueless you are to REAL life business web application and I am glad they, Microsoft, isn't listening to you or the MVP's, .NET authors and the like, who PREACHED over and over again the the complete stupidity of Postback. Now, they have to eat HUMBLE PIE..... [quoted text, click to view] "Rocky Moore" <gRockyMoore@hintsandtips.com> wrote in message news:erQeV6K6DHA.1504@TK2MSFTNGP12.phx.gbl... > I have to disagree with you. Processing forms is a simple matter now with > .NET and you no longer for to push people to another page just to save off > the data. That is something I would consider more of a hack. > > In .NET it is a simple matter to respond to the OnClick event, which your > validators will have validated the form and you are ready to process that > data from simple server controls and store in the database. If any errors > occur you have not left he page yet and can update a status field on the > form informing them of the error while all their data is preserved. Once > the data is successfully stored, you simply do a transfer to send them to a > result page if you so desire or back to the main page. > > It really does not get much easier than this. And the process keeps all > your server controls hooked for easy processing not to mention keeping your > code clean only having to deal with a single page. The processing of > regular form data has been a pain in the tush for over a decade! > > -- > Rocky Moore > www.HintsAndTips.com - Share your tips with the world! > ~~~~~~~~~ Developer Tips Welcome! ~~~~~~~~~ > > "anon" <anon@hotmail.com> wrote in message > news:#94R5ZJ6DHA.2480@TK2MSFTNGP12.phx.gbl... > > Yes, but setting the form action attribute is the BEST way to pass > > information page to page. > > > > <asp:Button runat="server" PostTargetUrl="page2.aspx" /> > > The Attribute: PostTargetUrl="page2.aspx" > > > > It's fastest way and most simpliest way for form data next to like the > > querystring. > > It's definately K.I.S.S. type of architecture. > > It's got the best performance on an enterprise level or any level for that > > matter > > And it works, plain and simple. > > > > All of those other ways are messy hacks that have drawbacks one way or > > another and can makes your code far far more complicated than what it > should > > be. > > > > All the other languages can do it this way, except .NET and because of > that, > > it's a pain in the a** to get real life questionairre form data into a > > database. > > > > The fact that MS is addressing this issue head on is a testament to this > > major major screwup > > > > Now, let's get back to the ORIGINAL question... is PostTargetUrl going to > be > > in the other HTML controls? That's what's important here and let's not > SCREW > > it up like MS did with 1.0 and 1.1 > > > > > > > > > > "Steve C. Orr [MVP, MCSD]" <Steve@Orr.net> wrote in message > > news:ugeKxCF6DHA.504@TK2MSFTNGP11.phx.gbl... > > > Setting the form action attribute just isn't the ASP.NET way. > > > > > > Of course there are a number of ways to pass values from one page to > > > another, such as using the querystring, cookies, session, > > > context, saving to a temporary table in the database between each page, > > etc. > > > You'll have to decide which technique is best for your application. > > > Here are several good articles on the subject to help you decide. > > > > > > http://msdn.microsoft.com/msdnmag/issues/03/04/ASPNETUserState/default.aspx > > > > > > http://www.aspalliance.com/kenc/passval.aspx > > > > > > http://www.dotnetjunkies.com/tutorials.aspx?tutorialid=600 > > > > > > http://www.dotnetbips.com/displayarticle.aspx?id=79 > > > > > > Here's one nice, simple way to pass values from one page to another: > > > > > > 'Add data to the context object before transferring > > > Context.Items("myParameter") = x > > > Server.Transfer("WebForm2.aspx") > > > > > > Then, in WebForm2.aspx: > > > > > > 'Grab data from the context property > > > Dim x as Integer = CType(Context.Items("myParameter"),Integer) > > > > > > -- > > > I hope this helps, > > > Steve C. Orr, MCSD, MVP > > > http://Steve.Orr.net > > > Hire top-notch developers at http://www.able-consulting.com > > > > > > > > > > > > "anon" <anon@hotmail.com> wrote in message > > > news:u2oi0$E6DHA.3664@tk2msftngp13.phx.gbl... > > > > Post Forwarding question...... > > > > > > > > For this control below, > > > > > > > > <asp:Button runat="server" PostTargetUrl="page2.aspx" /> > > > > > > > > The Attribute: PostTargetUrl="page2.aspx" > > > > > > > > Is this PostTargetUrl Attribute going to be available in the <a> and > > Html > > > > Controls as well as opposed to just the <asp:Button> control? > > > > > > > > Lots of other controls, HTML controls, <a>, <img>, etc, would like to > > used > > > > to post forward.... > > > > > > > > > > > > > > > > > > > >
Personally, I agree with you.
There are times where I designed asp forms that posted back to themselves, just like Asp.net where they'd detect IsPostBack and process form variables accordingly. However, there is always the OTHER way, whereas you collect information and pass that info on to ANOTHER form for processing... SEARCHING comes to mind... For example, when you want to search based on Mfr Part Number, you'd submit search parameters to a form that specialized in displaying and sorting via MANUFACTURERS, another scenario would be to search by Stocks, stock symbol vs company name... the form "posted" to would specialize on helping you find either the stock SYMBOL you're looking for, or a company name, and THEN the stock symbol, which probably would post back to an original "quote display" form that specialized only in displaying quotes. the asp.net postback mentality has been both nice AND problematic so I agree with "anon" in that it was a screwup only to force EVERYBODY to run through a "new" model, and ONLY that "new" model -- Eric Newton eric.at.ensoft-software.com www.ensoft-software.com C#/ASP.net Solutions developer [quoted text, click to view] "anon" <anon@hotmail.com> wrote in message news:%2394R5ZJ6DHA.2480@TK2MSFTNGP12.phx.gbl... > Yes, but setting the form action attribute is the BEST way to pass > information page to page. > > <asp:Button runat="server" PostTargetUrl="page2.aspx" /> > The Attribute: PostTargetUrl="page2.aspx" > > It's fastest way and most simpliest way for form data next to like the > querystring. > It's definately K.I.S.S. type of architecture. > It's got the best performance on an enterprise level or any level for that > matter > And it works, plain and simple. > > All of those other ways are messy hacks that have drawbacks one way or > another and can makes your code far far more complicated than what it should > be. > > All the other languages can do it this way, except .NET and because of that, > it's a pain in the a** to get real life questionairre form data into a > database. > > The fact that MS is addressing this issue head on is a testament to this > major major screwup > > Now, let's get back to the ORIGINAL question... is PostTargetUrl going to be > in the other HTML controls? That's what's important here and let's not SCREW > it up like MS did with 1.0 and 1.1 > > > > > "Steve C. Orr [MVP, MCSD]" <Steve@Orr.net> wrote in message > news:ugeKxCF6DHA.504@TK2MSFTNGP11.phx.gbl... > > Setting the form action attribute just isn't the ASP.NET way. > > > > Of course there are a number of ways to pass values from one page to > > another, such as using the querystring, cookies, session, > > context, saving to a temporary table in the database between each page, > etc. > > You'll have to decide which technique is best for your application. > > Here are several good articles on the subject to help you decide. > > > http://msdn.microsoft.com/msdnmag/issues/03/04/ASPNETUserState/default.aspx > > > > http://www.aspalliance.com/kenc/passval.aspx > > > > http://www.dotnetjunkies.com/tutorials.aspx?tutorialid=600 > > > > http://www.dotnetbips.com/displayarticle.aspx?id=79 > > > > Here's one nice, simple way to pass values from one page to another: > > > > 'Add data to the context object before transferring > > Context.Items("myParameter") = x > > Server.Transfer("WebForm2.aspx") > > > > Then, in WebForm2.aspx: > > > > 'Grab data from the context property > > Dim x as Integer = CType(Context.Items("myParameter"),Integer) > > > > -- > > I hope this helps, > > Steve C. Orr, MCSD, MVP > > http://Steve.Orr.net > > Hire top-notch developers at http://www.able-consulting.com > > > > > > > > "anon" <anon@hotmail.com> wrote in message > > news:u2oi0$E6DHA.3664@tk2msftngp13.phx.gbl... > > > Post Forwarding question...... > > > > > > For this control below, > > > > > > <asp:Button runat="server" PostTargetUrl="page2.aspx" /> > > > > > > The Attribute: PostTargetUrl="page2.aspx" > > > > > > Is this PostTargetUrl Attribute going to be available in the <a> and > Html > > > Controls as well as opposed to just the <asp:Button> control? > > > > > > Lots of other controls, HTML controls, <a>, <img>, etc, would like to > used > > > to post forward.... > > > > > > > > > > > >
Nobody forces you to specify runat server for any form or control.
So for anything like "search" functionality i am using exactly the same way as i would use in ASP. <form target="searchresult.aspx"><input type="text" name="word"></form> And i do not have any problem. And i can not aggree with you that ASP.NET forces to anyhting. You can always use ASP model (without post backs) with ASP.NET exaclty the same way as you would with ASP. George. [quoted text, click to view] "Eric Newton" <eric@ensoft-software.com> wrote in message news:ev9VDeM8DHA.1804@TK2MSFTNGP12.phx.gbl... > Personally, I agree with you. > > There are times where I designed asp forms that posted back to themselves, > just like Asp.net where they'd detect IsPostBack and process form variables > accordingly. > > However, there is always the OTHER way, whereas you collect information and > pass that info on to ANOTHER form for processing... SEARCHING comes to > mind... > > For example, when you want to search based on Mfr Part Number, you'd submit > search parameters to a form that specialized in displaying and sorting via > MANUFACTURERS, another scenario would be to search by Stocks, stock symbol > vs company name... the form "posted" to would specialize on helping you find > either the stock SYMBOL you're looking for, or a company name, and THEN the > stock symbol, which probably would post back to an original "quote display" > form that specialized only in displaying quotes. > > the asp.net postback mentality has been both nice AND problematic > > so I agree with "anon" in that it was a screwup only to force EVERYBODY to > run through a "new" model, and ONLY that "new" model > > > -- > Eric Newton > eric.at.ensoft-software.com > www.ensoft-software.com > C#/ASP.net Solutions developer > > "anon" <anon@hotmail.com> wrote in message > news:%2394R5ZJ6DHA.2480@TK2MSFTNGP12.phx.gbl... > > Yes, but setting the form action attribute is the BEST way to pass > > information page to page. > > > > <asp:Button runat="server" PostTargetUrl="page2.aspx" /> > > The Attribute: PostTargetUrl="page2.aspx" > > > > It's fastest way and most simpliest way for form data next to like the > > querystring. > > It's definately K.I.S.S. type of architecture. > > It's got the best performance on an enterprise level or any level for that > > matter > > And it works, plain and simple. > > > > All of those other ways are messy hacks that have drawbacks one way or > > another and can makes your code far far more complicated than what it > should > > be. > > > > All the other languages can do it this way, except .NET and because of > that, > > it's a pain in the a** to get real life questionairre form data into a > > database. > > > > The fact that MS is addressing this issue head on is a testament to this > > major major screwup > > > > Now, let's get back to the ORIGINAL question... is PostTargetUrl going to > be > > in the other HTML controls? That's what's important here and let's not > SCREW > > it up like MS did with 1.0 and 1.1 > > > > > > > > > > "Steve C. Orr [MVP, MCSD]" <Steve@Orr.net> wrote in message > > news:ugeKxCF6DHA.504@TK2MSFTNGP11.phx.gbl... > > > Setting the form action attribute just isn't the ASP.NET way. > > > > > > Of course there are a number of ways to pass values from one page to > > > another, such as using the querystring, cookies, session, > > > context, saving to a temporary table in the database between each page, > > etc. > > > You'll have to decide which technique is best for your application. > > > Here are several good articles on the subject to help you decide. > > > > > > http://msdn.microsoft.com/msdnmag/issues/03/04/ASPNETUserState/default.aspx > > > > > > http://www.aspalliance.com/kenc/passval.aspx > > > > > > http://www.dotnetjunkies.com/tutorials.aspx?tutorialid=600 > > > > > > http://www.dotnetbips.com/displayarticle.aspx?id=79 > > > > > > Here's one nice, simple way to pass values from one page to another: > > > > > > 'Add data to the context object before transferring > > > Context.Items("myParameter") = x > > > Server.Transfer("WebForm2.aspx") > > > > > > Then, in WebForm2.aspx: > > > > > > 'Grab data from the context property > > > Dim x as Integer = CType(Context.Items("myParameter"),Integer) > > > > > > -- > > > I hope this helps, > > > Steve C. Orr, MCSD, MVP > > > http://Steve.Orr.net > > > Hire top-notch developers at http://www.able-consulting.com > > > > > > > > > > > > "anon" <anon@hotmail.com> wrote in message > > > news:u2oi0$E6DHA.3664@tk2msftngp13.phx.gbl... > > > > Post Forwarding question...... > > > > > > > > For this control below, > > > > > > > > <asp:Button runat="server" PostTargetUrl="page2.aspx" /> > > > > > > > > The Attribute: PostTargetUrl="page2.aspx" > > > > > > > > Is this PostTargetUrl Attribute going to be available in the <a> and > > Html > > > > Controls as well as opposed to just the <asp:Button> control? > > > > > > > > Lots of other controls, HTML controls, <a>, <img>, etc, would like to > > used > > > > to post forward.... > > > > > > > > > > > > > > > > > > > >
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
December 2007
January 2008
February 2008
March 2008
April 2008
| home · blog · groups | Questions? Comments? Contact the dn |