Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Maybe you can find the solution here in <a href="http://forums.asp.net/t/1305800.aspx" rel="nofollow noreferrer">this ASP.NET Forum post</a> (Known Issues / Breaking Changes for ASP.NET in .NET 3.5 Service Pack 1).</p> <h2>Issue</h2> <p>The HtmlForm action attribute is now honored when defined in declarative markup. </p> <h2>Reason</h2> <p>3.5 SP1 added a settable Action property to the HtmlForm type. This new feature makes it much easier for developers to explicitly set the form’s action attribute for scenarios where a developer wants to use a different Url than the normal postback-generated Url. However this change also means that if the action attribute has been set in an .aspx page’s declarative markup, ASP.NET will use the setting from the markup when rendering a <code>&lt;form /&gt;</code> element. </p> <h2>Workaround</h2> <p>Previous versions of ASP.NET always ignored the action attribute if it was present in the declarative markup for a <code>&lt;form /&gt;</code> element. Developers should remove the action attribute from their declarative markup to return to the original behavior where ASP.NET renders the postback Url. </p> <h2>Example</h2> <p>Before (the action attribute was ignored by ASP.NET as dead code): </p> <pre><code>&lt;form name="form1" method="post" runat="server" action="test.aspx"&gt;&lt;/form&gt; </code></pre> <p>3.5 SP1 (remove the action attribute to have ASP.NET render the postback Url): </p> <pre><code>&lt;form name="form1" method="post" runat="server"&gt;&lt;/form&gt; </code></pre>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload