Embed JavaScript in Custom ASP.NET Server Controls

As ASP.NET evolves, using ASP.NET WebForms is still the most popular way to serve up ASP.NET. One of the biggest benefits of ASP.NET WebForms is the fact that we can use re-usable code in several ways including in a compiled server control. What you may not know is that server controls can be quite powerful and can allow referencing JavaScript files. But, if you’re distributing your controls or do not have the means to host your JavaScript files on a content delivery network (CDN), you may want to package the files with your control.

So, let’s start from the beginning. Let’s assume that we’re building a sample web application to test our control output. We’ll create a brand new solution in Visual Studio 2012 along with an ASP.NET Empty Web Application. After the project is created, we’ll add another new project: an ASP.NET Server Control project called ‘OurSuperCoolControlSuite’.

After our server control project has been added, we’ll see a .cs file (or .vb file if we are using Visual Basic) named ServerControl1.cs. For this example, let’s rename this to GreetingControl.cs. I then have updated my GreetingControl.cs to include a basic input text element that calls some custom JavaScript when the input element loses focus to show a Greeting alert. Here’s what the GreetingControl.cs looks like:

GreetingControl.cs

   1: using System;
   2: using System.Collections.Generic;
   3: using System.ComponentModel;
   4: using System.Linq;
   5: using System.Text;
   6: using System.Threading.Tasks;
   7: using System.Web;
   8: using System.Web.UI;
   9: using System.Web.UI.WebControls;
  10:  
  11: namespace OurSuperCoolControlSuite
  12: {
  13:     [DefaultProperty("Text")]
  14:     [ToolboxData("<{0}:GreetingControl runat=server></{0}:GreetingControl>")]
  15:     public class GreetingControl : WebControl
  16:     {
  17:         [Bindable(true)]
  18:         [Category("Appearance")]
  19:         [DefaultValue("")]
  20:         [Localizable(true)]
  21:         public string Text
  22:         {
  23:             get
  24:             {
  25:                 String s = (String)ViewState["Text"];
  26:                 return ((s == null)? "Jason" : s);
  27:             }
  28:  
  29:             set
  30:             {
  31:                 ViewState["Text"] = value;
  32:             }
  33:         }
  34:  
  35:         protected override void OnPreRender(EventArgs e)
  36:         {
  37:             Page.ClientScript.RegisterClientScriptResource(typeof(GreetingControl), "OurSuperCoolControlSuite.Scripts.Greeting.js");
  38:             Page.ClientScript.RegisterStartupScript(typeof(Page), "ControlFocus", "document.getElementById('" + this.ClientID + "').focus();", true);
  39:         } 
  40:  
  41:         protected override void RenderContents(HtmlTextWriter output)
  42:         {
  43:             output.RenderBeginTag(HtmlTextWriterTag.Div);
  44:             output.AddAttribute(HtmlTextWriterAttribute.Type, "text");
  45:             output.AddAttribute(HtmlTextWriterAttribute.Id, this.ClientID);
  46:             output.AddAttribute(HtmlTextWriterAttribute.Name, this.ClientID);
  47:             output.AddAttribute(HtmlTextWriterAttribute.Value, this.Text);
  48:             output.AddAttribute("onBlur", "greetMe(this.value);");
  49:             output.RenderBeginTag(HtmlTextWriterTag.Input);
  50:             output.RenderEndTag();
  51:             output.RenderEndTag();
  52:         }
  53:     }
  54: }

Next, we’ll add a Scripts folder to this same project. We don’t have to, but this allows us to organize our JavaScript files better. So, if you look in the code snippet above, you’ll notice on Line 37, we’re using ClientScript.RegisterClientScriptResource. This method takes two attributes: a type and a string of the resource. For the type, it’s best to use the class name of the control you are building. The reasoning behind this is that if you are sharing the same script across multiple controls, you may run into some strange behavior as the embedded resource will be shared between all of the controls using the same type. This means that if your end users are using two different controls that use the same resource on the same page and that resource contains a variable to store a value, the value is used between both controls. The second attribute is our JavaScript file. Now, in a minute, we’ll add Greeting.js to our Scripts folder. But, we can have multiple Greeting.js files in our application. So, to clarify which one we would like to use, we need to specify the assembly name, folder structure, and JavaScript file name. In this case, our default namespace and assembly are both OurSuperCoolControlSuite. The folder structure is just Scripts. We’ll separate these using periods to get OurSuperCoolControlSuite.Scripts.Greeting.js.

Let’s add that JavaScript file now and change the Build Action of the file in the properties window to ‘Embedded Resource’.

Greeting.js

   1: function greetMe(value) {
   2:     alert('Welcome, ' + value);
   3: }

We’re almost there. We have our JavaScript embedded into the binary and we’re looking to register the script file in our control, but at this point we haven’t specified that this resource is available to the Web. So, just to keep all of our assembly information together in AssemblyInfo.cs by adding the following to that file (found in the Properties folder):

[assembly: WebResource("OurSuperCoolControlSuite.Scripts.Greeting.js", "text/javascript")]

Now, let’s compile our server control project OurSuperCoolControlSuite.

Going back to our ASP.NET Web project, let’s add a new ASP.NET WebForm called default.aspx. We’ll switch to design mode as this refreshes the Toolbox window. We should now see our control appear at the top of the toolbox as shown below:

image

Finally, let’s drag our control to the designer. We’ll leave all of the default values of the control and simply run our Web application to see what we’ve done. When we leave the input control, we’ll get our JavaScript alert like we’re expecting:

image

So, let’s check out the rendered markup:

   1:  
   2:  
   3: <!DOCTYPE html>
   4:  
   5: <html xmlns="http://www.w3.org/1999/xhtml">
   6: <head><title>
   7:  
   8: </title></head>
   9: <body>
  10:     <form method="post" action="default.aspx" id="form1">
  11: <div class="aspNetHidden">
  12: <input type="hidden" name="__VIEWSTATE" id="__VIEWSTATE" value="ujUKHFd/M66UGv4J0cHNpTYhArBWf9fbtT2EnoPIeBCTvKsxnv8RhqWiclz4isaDVA5RGAq34QhgzP1u00nUnc2G+uo9cHBXO93wo4KVt0g=" />
  13: </div>
  14:  
  15:  
  16: <script src="/WebResource.axd?d=-P4RDcgXkNOn_YBSzQs9QnlpUkuyKvL9dN_aN24z9gNtNbp8N0RegRa0qyC9MB1-76d6lcsPvf-em95iFJrp2hesCfrTWRkCgd7vEMF3yI3Rfc_Eyywc7m9bEtxaWp_rVl_WDYbyF97Ehy42Q0Z1WQ2&amp;t=634880155251801752" type="text/javascript"></script>
   1:  
   2:     <div>
   3:     
   4:         <span id="GreetingControl1"><div>
   5:     <input type="text" id="GreetingControl1" name="GreetingControl1" value="Jason" onBlur="greetMe(this.value);" />
   6: </div></span>
   7:     
   8:     </div>
   9:     
  10:  
  11: <script type="text/javascript">
  12: //<![CDATA[
  13: document.getElementById('GreetingControl1').focus();//]]>
</script>
  17: </form>
  18: </body>
  19: </html>

Notice that in Line 16, we have a script reference. This reference is using an HttpHandler named WebResource.axd. Our JavaScript file has been referenced through this URL.


What’s cool about this is that we now have a self-contained server control that has an embedded JavaScript file.


So, if you’d like to skip right to the demo without building it yourself, feel free to download the solution using the link below.


Enjoy!



Download



Leave a Reply

Your email address will not be published. Required fields are marked *


*

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>