Home/ Questions/Q 7414503
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-29T07:06:38+00:00

Is it better to load ALL my resources in my base layout/template view, or

  • 0

Is it better to load ALL my resources in my base layout/template view, or directly in the partial view I load in ajax?

Exemple:

_layout:

[...]

    <head>
        <script src="file.js"></script>
        <link href="file.css"></link >
    </head>

[...]

OR

_layout:

[...]

    <head>
    </head>

[...]

partialView (loaded later in AJAX):

<div>
    <script src="file.js"></script>
    <link href="file.css"></link > 
</div>
Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    What you would normally be doing is pushing some script resources into a list on the viewbag, and then get your template to go through that list and generate the script include for you.

    On the partial:

    @{
    ViewBag.ScriptIncludes = ViewBag.ScriptIncludes ?? new List<string>();
    ViewBag.ScriptIncludes.add("script1.js");
}

    In the layout (_Layout.cshtml)

    @if (ViewBag.ScriptIncludes != null)
{
    foreach (string url in ViewBag.ScriptIncludes)
    {
        <script src="@url" type="text/javascript"></script>
    }
}

    In normal circumstances this allows you to associate scripts with partial which is quite nice, and is a good idea if you are only refreshing a partial which exists on the page on page load.

    The scripts should be preloaded on the page. You shouldn’t be reloading scripts by getting a script resource via ajax and injecting it into the page. Ideally you wouldn’t be getting html over ajax either, but some people find this acceptable. You only want to inject the html into the page and not more scripts. If you have event handlers on the items inside the partial view, consider attaching the event handlers to the container instead of the elements individually.

    However, given that you are reloading potentially any view, I think you are better off including your scripts in the head. This will ensure that you don’t find any conflicting scripts later on. Your site is essentially an application that costs the user a small overhead to load initially but does not need to be refreshed.

    • 0