Personally, I would use a partial view and ASP Content Placeholder.
Views / Shared has a partial view of EditorScripts.ascx that contains tags that define the scripts that will be included in your editing pages.
Then place the placeholder in the Site.Master <head> , something like this:
<asp:ContentPlaceHolder ID="HeadContent" runat="server" />
In any view you want / need scripts, enter this code:
<asp:Content ContentPlaceHolderID="HeadContent" runat="server"> <% Html.RenderPartial("EditorScripts"); %> </asp:Content>
This is not an ideal solution and not as dynamic as we would like. The reason for using a partial view is that if you decide to update or add more scripts for these views, you only need to update them in one place.
Another way would be to have an Editor.Master page containing these scripts and other editor-specific topics, then this wizard uses Site.Master as the main page. Then all editor views will have Editor.Master as the main page.
NTN
Alastair pitts
source share