ansaurus

Question

body runat="server" causing compilation error

Answer 1

+5 A:

You need to add this in the code behind;

protected void Page_Load(object sender, EventArgs e)
{
     body.Attributes.Add("onload", "someJavaScriptFunction();");
}

Adding runat="server" to a tag makes it a server tag, even if it isn't one of the explicitly prefixed ones (e.g. <asp:Panel />). On server tags, any onXXXX event handlers handle the server-side events, not the client-side events (except for when "client" is explicitly called out, such as with OnClientClick for buttons).

Dead account 2009-04-07 13:22:47

OK, I can see how that would work - but why does adding runat="server" mean I need to use this approach?

Richard Ev 2009-04-07 13:25:51

I think because it's looking for the Body_SomeJavaScriptFunction method in the code behind, because you told it to "run at server" ?

Dead account 2009-04-07 13:27:47

Correct... I appended your answer Ian, hope you don't mind :)

Daniel Schaffer 2009-04-07 13:32:49

No problem. I've hit my 200 rep points for the day so I guess I better get on with some work :)

Dead account 2009-04-07 13:35:54

Well appended Daniel, thanks!

Richard Ev 2009-04-07 13:49:47

Answer 2

+3 A:

It is also an option to set:

<head>
  <script language="text/javascript">
    window.onload = function() { someJavaScriptFunction(); }
  </script>
</head>

This is happening because ASP is trying to interpret the script inside the body tag as part of the code in the page. As though it were C# / VB...

John Gietzen 2009-04-07 13:24:20

This doesn't answer the questions "What is going on here?" and "why does the ASP.NET compiler care about this?"

Cerebrus 2009-04-07 13:44:13

This is the approach that I went with in the end, in my scenario.

Richard Ev 2009-04-07 13:50:21

ansaurus

tags:

views:

answers:

body runat="server" causing compilation error

related questions