ansaurus

Question

Getting server side javascript over client side

Answer 1

+1 A:

Make sure you didn't forget <form runat="server" ID="Form1"></form> at the end of the <head> tag!

As you can read in Using JavaScript Along with ASP.NET 2.0 under "The Difference Between Page.ClientScript.RegisterStartupScript and Page.ClientScript.RegisterClientScriptBlock" they rely on the location of the form tag.

We have shown two different methods for placing JavaScript functions on an ASP.NET page—so what is the difference? The main difference is that the RegisterStartupScript method places the JavaScript at the bottom of the ASP.NET page right before the closing element. The RegisterClientScriptBlock method places the JavaScript directly after the opening element in the page. So what difference does this make? It can make quite a bit of difference, as we will see.

Dror 2009-11-10 12:10:13

I know that ASP.NET can be weird — but would that really fix the problem of forms not being allowed inside the head element?

David Dorward 2009-11-10 12:12:04

The form may as well be in the body - not necessarily in the head...

Dror 2009-11-10 12:22:05

Thanks Dror! You have provided such a useful information.

IrfanRaza 2009-11-10 12:49:48

Answer 2

+1 A:

One way to do it would be to place a literal control above your textbox, and assign the script to it in the code behind:

literal1.Text = "<script>function maskDate() {...}</script>";

The benefit to this, is you would not need to have to reference the script file with some tricky relative paths depending on where your usercontrol is used.

Josh Pearce 2009-11-10 12:21:40

Thanks Josh! Thats a nice idea.

IrfanRaza 2009-11-10 12:48:03

ansaurus

tags:

views:

answers:

Getting server side javascript over client side

related questions