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>
Next I looked at the generated assembly using ILDASM, at very end of the MANIFEST section was the following entry to bundle the JavaScript resource into the assembly:
.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>
I also had to change the JavaScript file. The changes required are explained in the following three steps.
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
Modifications to the extender file (AmericanSSNExtender.vb):
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 behavior file has the javascript code (ms-ajax class). At the start of the javascript code a namespace is registered and any reference to the behavior class needs to be qualified by the registered namespace. Change the default namespace registered <Project Name> to the root namespace and change all references to it too.
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.
Please login to rate or to leave a comment.