I created a custom search control that is intended to replace the default search SkinObject. So wherever a skin marks a SEARCH token, my new control would replace the default.

After creating the control, and successfully adding it to Extensions and assigning it to the SEARCH token, I noticed that my control still wasn't showing. Also, when I replaced the existing, older search control (I did this by renaming the Key value to something other than SEARCH), I noticed that the default still hadn't gone away.

So I went into the default.aspx file and noticed that, at least in MinimalEntropy, that there was a REGISTER tag pointing to the older search control. I changed it to my custom control's path, and voila - my control showed up.

This leads me to ask what the proper deployment method is for SkinObjects that replace default SkinObjects. Do I:

- Create my custom SkinObject with the SAME NAME as the one I am replacing? This doesn't seem right, but it saves me having to go in and manually update 25+ skin files.

- Or, have I missed a step in deployment? When following Mitch Sellar's example (his SCBreadCrumb article specifically), he mentions that the SkinObject will be deployed in the DesktopModules folder. But in this case, since its replacing a default object, I thought that simply specifying my control with the SEARCH token would update any other skins.

Sorry for the long winded question, hope it makes sense. This directly impacts my deployment model for a number of sites so I'm hoping there's an easy answer.