Home/ Questions/Q 8093141
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-05T20:26:25+00:00

I have a web project in Asp.net MVC where in many pages, there is

  • 0

I have a web project in Asp.net MVC where in many pages, there is drop down list controls. When the value of these drop down list changes, a request to the controller action must be made to refresh some div tags.

To do that, I use the $(document).ready() function of jquery and I create a function like this:

$("#ComboBox").change(function() { /* do something here */ });

$.get('@Url.Action("Action", "Controller")', function (result) { 
    // TODO: process the results of the server side call
});

The problem is I don’t want to create a big javascript file that contains a list of all things that must be done in all pages when the document ready event of jquery occurs.

For example, in one page, I have a combobox that create a request to the action x of the controller x and in another page another combobox that create a request to the action y of the controller y.

I’m not sure if this is a good strategy to create a distinct javascripf file for each of these pages.

What can I do? Create a javascript for each specific document ready function? If I put all the functions in the same document ready function of the same javascript file, what about conflict naming in id and class referred by control with jquery? And if all the functions are in the same javascript, what about page that don’t use 90% of the functions in the document ready function.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    When javascript gets more and more bigger in the client side you should really think about maintenance. jQuery is really easy to use but the problem is suddenly you will see the callbacks/handlers in many places makes difficult to manage. I would suggest you to use some kind of MVC library in the client side like Backbone.js that helps to organize the code in a better way.

    The second this as the development perspective we should separate out the complete javascript used in the application into separate files module/controller wise. You could use minification frameworks that helps to combine all the javascript into single file.

    The ASP.NET MVC 4 itself has the support of bindling/minification that helps you to combine and minify a set of js or css files.

    http://ofps.oreilly.com/titles/9781449320317/ch_ClientOptimization.html#BundlingAndMinification
    http://weblogs.asp.net/scottgu/archive/2011/11/27/new-bundling-and-minification-support-asp-net-4-5-series.aspx

    • 0