By design a RadWindowManager is a singleton, meaning that it expects to be the only one on the rendered page. This is why the scripts are included in the PromptTemplate for each template. I am logging the idea that this function should be in the RadWindowManager scripts file instead of the template, so our developers can review it. You can monitor, comment and vote on it to raise its priority here
. I have also updated your Telerik points for your suggestion.
This is not a lot of code and by using the approach Shinu quoted from this help article
should allow you to show the desired template from the desired control.
An alternative you can look into is this KB article
. You can create a public property in the master page that will return the RadWnidowManager there so its templates can be changed as needed. This can work if you do not need two different templates at once on a given page+master page combination. If you do - having several managers is the only option that requires little code. An lternative could be creating custom RadWindow dialogs whose ContentTemplate will resemble the desired dialog template and they will have the settings you desire (an example of such a dialog is shown here
, see the last section).
If you want to get updates on new releases, tips and tricks and sneak peeks at our product labs directly from the developers working on the RadControls for ASP.NET AJAX, subscribe to the blog feed