E
Ed Courtenay
Reposting here as you can practically see the tumbleweed blow by in
microsoft.public.dotnet.framework.aspnet.webcontrols....
I've got a very simple custom control that requires a small section of
JavaScript to function at the client - nothing out of the ordinary.
In the overridden RenderContents method of my custom control I check
whether the required client script block has been registered with
Page.ClientScript.IsClientScriptBlockRegistered() and if not, register
it with Page.ClientScript.RegisterClientScriptBlock()
If I place the custom control on a web form, the script gets injected
into the page as expected and works as it should.
If, however, the control is placed onto a Master page the script doesn't
get injected and therefore the control fails to work; why is this
behaving differently when the control is placed on a Master page, and
what do I have to do to get it to work?
microsoft.public.dotnet.framework.aspnet.webcontrols....
I've got a very simple custom control that requires a small section of
JavaScript to function at the client - nothing out of the ordinary.
In the overridden RenderContents method of my custom control I check
whether the required client script block has been registered with
Page.ClientScript.IsClientScriptBlockRegistered() and if not, register
it with Page.ClientScript.RegisterClientScriptBlock()
If I place the custom control on a web form, the script gets injected
into the page as expected and works as it should.
If, however, the control is placed onto a Master page the script doesn't
get injected and therefore the control fails to work; why is this
behaving differently when the control is placed on a Master page, and
what do I have to do to get it to work?