Introduction

Having developed an atlas composite social security control - I wanted to change the root namespace from the default (<Project Name>) to the standard, followed at my company. I thought it would be simple enough; I was in for a big surprise. Basically I opened the project properties and replaced the Root namespace from "AmericanSSN" (this was my Project Name) to "AO.Web.UI.AtlasControls". I recompiled the project, included it in toolbox and dropped the composite control on an ASPX page, the control rendered fine at design time. When the page was loading at runtime, I got the "Unrecognized tag" error for "americanssn:AmericanSSNBehavior". Looking at the rendered HTML, I found that under the xml-script section generated by extender class, the page tag and behavior were rendered as:

<page ... xmlns:americanssn="americanssn"> <behaviors> <americanssn:AmericanSSNBehavior MyProperty="" ageRequestManagerID="_PageRequestManager" id="AmericanSSNControl1_SSNProperties" /> </behaviors> ... .mresource public AO.Web.UI.AtlasControls.AmericanSSNBehavior.js { // Offset: 0x00000000 Length: 0x00001AD0 }

Since I had changed the Root namespace, I had to change the extender file so that it renders the following:

<page... xmlns:ao.web.ui.atlascontrols="ao.web.ui.atlascontrols"> <behaviors> <ao.web.ui.atlascontrols:AmericanSSNBehavior MyProperty="" PageRequestManagerID="_PageRequestManager" id="AmericanSSNControl1_SSNProperties" /> </behaviors>

Step 1

Modifications to project properties:

Click on project properties and change the root namespace from <Project Name> to AO.Web.UI.AtlasControls.

Step 2

Modify the "Assembly Resource Attribute" region, click on the + sign to open the region and change the namespace qualifier of the JavaScript file from <Project Name> to the root namespace. This is necessary because web resources must be referenced with their fully qualifed name.

Modify the ClientScriptResource class attribute tag, change the prefix parameter from <Project Name> to the root namespace, change the namespace qualifier of the JavaScript file from to root namespace. The prefix is used in constructing the xml-scrpt section.

The sections marked in Red were replaced with those marked in Blue

The above was changed to:

Step 3

Modifications to behavior file (AmericanSSNBehavior.vb):

The sections marked in Red were replaced with those marked in Blue at different places in the JavaScript file.

The above was changed to:

The above was changed to:

The important thing to note in the following section is the changes to the Sys.TypeDescriptor.addType method. While changing the Extender file we had changed the prefix parameter of the ClientScriptResource class attribute. Notice that over there the namespace was small cased. That is what will get written to the HTML payload, and the Sys.TypeDescriptor.addType method will get executed when the page loads in the clients browser before the atlas framework script reads and parses the xml-script section. The atlas framework parser script is the one that throws the error "Unrecognized Tag" based on addType parameters. So this needs to changed as shown below:

The above was changed to:

Summary

This article described how to change namespace from the default namespace to a more realistic one for an Atlas Extender Control project.

Other articles in this category ASP.NET Ajax Grid and Pager Learn how to create a custom Ajax Grid and Pager with the Microsoft ASP.NET AJAX platform. JSON-Enabled WCF Services in ASP.NET 3.5 Dino Esposito overviews the integration between WCF and AJAX Using jQuery with ASP .NET A brief introduction to jQuery and ways in which we can integrate it into ASP .NET ASP.NET AJAX Control Development An in depth guide to developing controls with the ASP.NET AJAX ASP.NET Ajax Web Service Sharing some of the Common Issues of ASP.NET Ajax Web Services. You might also be interested in the following related blog posts Squeezing the last millisecond from the page load time read more Pattern Focus: MVP, MVC, MVWatever read more WPF Presence Controls for Office Communicator 2007 read more Ruminations on Multi-Tenant Data Architectures read more Silverlight 2 Beta 1 Controls Available, including Source and Unit Tests read more Adding Default Assemblies, Namespaces and Control Prefixes in Web.Config read more CruiseControl.NET Caching Old Project Locations SOLVED read more How to call controllers in external assemblies in an ASP.NET MVC application read more CS Dev Guide: How to Write a Custom Chameleon Control read more Ambiguous References in DefaultWsdlHelpGenerator.aspx read more

Top