R – Posting a web form to a different page in asp.net 3.5

.net-3.5form-submit

I am told that form.action attribute is being honored right now; so we can post a form to a different page. i have tried that, but i get an error to do with ViewState (I realise why).

What I am trying to find out for sure if I can in fact post to a different page w/o getting this error; otherwise I see no point for Microsoft to implement this "feature" at all,

Unfortunately, in my app i HAVE to post to a different IP, so I have to make this work. Any ideas?

I am completely baffled as to why honor form.action but not make it work – it's a soft of a half-baked feature. According to MS this is a known issue.

Refer to this:
here

Best Answer

So if your machine keys are the same and or you post without viewstate on the page, then you can cross post all day long.

So if you set the machine key in the machine config of both servers to the same value you should be good.

Related Solutions

.NET 3.5 SP1 changes for ASP.NET

http://weblogs.asp.net/scottgu/archive/2008/05/12/visual-studio-2008-and-net-framework-3-5-service-pack-1-beta.aspx

There is a section in there on the improvements for web development.. it can be vague as well but has links to videos and further information. I suggest checking it out.

.net – How to take more control in ASP.NET

This solution will give you programmatic access to the controls in their entirety including all attributes on the controls. Also, only the text box values will appear in the URL upon submission so your GET request URL will be more "meaningful"

<%@ Page Language="C#" AutoEventWireup="true" CodeBehind="JonSkeetForm.aspx.cs" Inherits="JonSkeetForm" %>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

<html xmlns="http://www.w3.org/1999/xhtml" >
<head runat="server">
    <title>Jon Skeet's Form Page</title>
</head>
<body>
    <form action="JonSkeetForm.aspx" method="get">
    <div>
        <input type="text" ID="text1" runat="server" />
        <input type="text" ID="text2" runat="server" />
        <button type="submit">Submit</button>
        <asp:Repeater ID="Repeater1" runat="server">
            <ItemTemplate>
                <div>Some text</div>
            </ItemTemplate>
        </asp:Repeater>
    </div>
    </form>
</body>
</html>

Then in your code-behind you can do everything you need on PageLoad

public partial class JonSkeetForm : System.Web.UI.Page
{
    protected void Page_Load(object sender, EventArgs e)
    {
        text1.Value = Request.QueryString[text1.ClientID];
        text2.Value = Request.QueryString[text2.ClientID];
    }
}

If you don't want a form that has runat="server", then you should use HTML controls. It's easier to work with for your purposes. Just use regular HTML tags and put runat="server" and give them an ID. Then you can access them programmatically and code without a ViewState.

The only downside is that you won't have access to many of the "helpful" ASP.NET server controls like GridViews. I included a Repeater in my example because I'm assuming that you want to have the fields on the same page as the results and (to my knowledge) a Repeater is the only DataBound control that will run without a runat="server" attribute in the Form tag.

Best Answer

Related Solutions

.NET 3.5 SP1 changes for ASP.NET

.net – How to take more control in ASP.NET

Related Topic