“It is a truth universally acknowledged, that an ASP.NET page in possession of a component, must be in want of a form.”
I’ve just come across this sticky little scenario in one of my projects:
So what we’ve got looks like this:class="brush: xml; title: ; notranslate" title=""></p>
</pre> The variation from [James Byrd’s original article](http://www.nerdymusings.com/LPMArticle.asp?ID=27) comes from which form we submit. In the original, James posts the global form (in our example Form1) and instructs the reader to simply blank out any values they may not want to communicate to the third party. This seems overly permissive to me, especially in a potentially dynamic environment where you may have hundreds of components and as such my version simply selects the target form from the page before passing it through the validator and performing the submit action. The postback event is avoided, the third party only gets the data they need and the world is a happier place.