MvcScriptManager Wiki & Documentation Rss Feed

Updated Wiki: Home

thuang — Tue, 27 Oct 2009 05:07:59 GMT

Project Description

MvcScriptManager is aimed to port certain key features available in AjaxControlToolkit's ToolkitScriptManager into the current ASP.NET MVC Framework. You will be able to use it as a control in your ASP.NET MVC application.

Features

Script combination (or concatenation). Scripts declared with MvcScriptManager will be combined on the fly into a single script file request when the page is rendered.
Script minification (or crunching) in release mode. Minification process is done only once at the first request that references the specific script. Subsequent requests will use the crunched script content in cache (see #5 for detail). Crunching can be enabled/disabled for each script.
Render localized resources for stand-alone script files. Localized strings will be appended to the script if specified.
Support configurable HTTP compression and expiration setting when outputing scripts.
Script caching with file dependency. Script file content is cached so that rendering combined script file will be much more performant. Cache dependency is linked to the physical file therefore any script update in the file system will be reflected in the cache instantly.
Support rendering scripts in debug/release mode based on the running environment.
Resolving different paths for stand-alone script files.
Support multiple MvcScriptManagers on a single page (or master page). Support both Master and Slave rendering mode so that scripts declared with one ScriptManager can be rolled over to another one for rendering.
Suport web farm scenario.

What MvcScriptManager Won't Offer

Below are the things MvcScriptManager doesn't (and probably won't) offer in case you are used to using the ScriptManager and assume these features are included:

Support for ASP.NET Ajax extensibility model. In my opinion, with ASP.NET MVC Framework and jQuery, writing ajax script/extender controls is no longer necessary.
Support for embedded script files. We should avoid embedding script files in assembly anyway because updates of script will require a rebuild of the project which is not ideal.
Provide access to web methods from script by registering web services. This is overhead and you can totally avoid it by either using jQuery’s AJAX utilities or Sys.Net.WebServiceProxy class available in ASP.NET AJAX client library.
Support UpdatePanel and partial-page Rendering.

How to Use MvcScriptManager

Please see the attached Readme.pdf.

Updated Wiki: Home

thuang — Tue, 27 Oct 2009 05:06:56 GMT

Project Description

Features

Script combination (or concatenation). Scripts declared with MvcScriptManager will be combined on the fly into a single script file request when the page is rendered.
Script minification (or crunching) in release mode. Minification process is done only once at the first request that references the specific script. Subsequent requests will use the crunched script content in cache (see #5 for detail). Crunching can be enabled/disabled for each script.
Render localized resources for stand-alone script files. Localized strings will be appended to the script if specified.
Support configurable HTTP compression and expiration setting when outputing scripts.
Script caching with file dependency. Script file content is cached so that rendering combined script file will be much more performant. Cache dependency is linked to the physical file therefore any script update in the file system will be reflected in the cache instantly.
Support rendering scripts in debug/release mode based on the running environment.
Resolving different paths for stand-alone script files.
Support multiple MvcScriptManagers on a single page (or master page). Support both Master and Slave rendering mode so that scripts declared with one ScriptManager can be rolled over to another one for rendering.

What MvcScriptManager Won't Offer

Below are the things MvcScriptManager doesn't (and probably won't) offer in case you are used to using the ScriptManager and assume these features are included:

Support for ASP.NET Ajax extensibility model. In my opinion, with ASP.NET MVC Framework and jQuery, writing ajax script/extender controls is no longer necessary.
Support for embedded script files. We should avoid embedding script files in assembly anyway because updates of script will require a rebuild of the project which is not ideal.
Provide access to web methods from script by registering web services. This is overhead and you can totally avoid it by either using jQuery’s AJAX utilities or Sys.Net.WebServiceProxy class available in ASP.NET AJAX client library.
Support UpdatePanel and partial-page Rendering.

How to Use MvcScriptManager

Please see the attached Readme.pdf.

Updated Wiki: Home

thuang — Mon, 15 Jun 2009 05:58:22 GMT

Project Description

Features

Script combination (or concatenation). Scripts declared with MvcScriptManager will be combined on the fly into a single script file request when the page is rendered.
Script minification (or crunching) in release mode. Minification process is done only once at the first request that references the specific script. Subsequent requests will use the crunched script content in cache (see #5 for detail). Crunching can be enabled/disabled for each script.
Render localized resources for stand-alone script files. Localized strings will be appended to the script if specified.
Support configurable HTTP compression and expiration setting when outputing scripts.
Script caching with file dependency. Script file content is cached so that rendering combined script file will be much more performant. Cache dependency is linked to the physical file therefore any script update in the file system will be reflected in the cache instantly.
Support rendering scripts in debug/release mode based on the running environment.
Resolving different paths for stand-alone script files.
Support multiple MvcScriptManagers on a single page (or master page). Support both Master and Slave rendering mode so that scripts declared with one ScriptManager can be rolled over to another one for rendering.

What MvcScriptManager Won't Offer

Below are the things MvcScriptManager doesn't (and probably won't) offer in case you are used to using the ScriptManager and assume these features are included:

Support for ASP.NET Ajax extensibility model. In my opinion, with ASP.NET MVC Framework and jQuery, writing ajax script/extender controls is no longer necessary.
Support for embedded script files. We should avoid embedding script files in assembly anyway because updates of script will require a rebuild of the project which is not ideal.
Provide access to web methods from script by registering web services. This is overhead and you can totally avoid it by either using jQuery’s AJAX utilities or Sys.Net.WebServiceProxy class available in ASP.NET AJAX client library.
Support UpdatePanel and partial-page Rendering.

How to Use MvcScriptManager

Please see the attached Readme.pdf.

Who's using this code/library?

If you use this code in your project, please drop me a message.

Updated Wiki: Home

thuang — Fri, 05 Jun 2009 06:39:53 GMT

Project Description

Features

Script combining. Scripts declared with MvcScriptManager will be dynamically combined into a single script file request when the page is rendered.
Render localized resources for stand-alone script files. Localized strings will be appended to the script if specified.
Support script crunching in release mode. Crunching can be enabled/disabled for each script.
Support configurable HTTP compression and expiration setting when outputing scripts.
Script content caching with file dependency. Script file content is cached so that rendering combined script file will be much more performant. Cache dependency is linked to the physical file therefore any script update in the file system will be reflected in the cache instantly.
Support rendering scripts in debug/release mode based on the running environment.
Resolving different paths for stand-alone script files.
Support multiple MvcScriptManager's on a single page (or master page). Support both Master and Slave rendering modes:
- Master rendering mode – will render <Script/> tag, and include all scripts from itself and those from its slave(s).
- Slave rendering mode – will not render anything. But appends current instance’s scripts to preceding Master instance. This property is useful, especially when you have one or more ScriptManagers declared in the master page(s), and you are declaring another ScriptManager in the specific (non-master) page to add more scripts, but you want to hand over the rendering to the ScriptManager inside the master page only. In this case, you can set the ScriptManager's RenderMode in master page to Master, and the ScriptManager's RenderMode in the specific page to Slave.

What MvcScriptManager Won't Offer

Below are the things MvcScriptManager doesn't (and probably won't) offer in case you are used to using the ScriptManager and assume these features are included:

Support for ASP.NET Ajax extensibility model. In my opinion, with ASP.NET MVC Framework and jQuery, writing ajax script/extender controls is no longer necessary.
Support for embedded script files. We should avoid embedding script files in assembly anyway because updates of script will require a rebuild of the project which is not ideal.
Provide access to web methods from script by registering web services. This is overhead and you can totally avoid it by either using jQuery’s AJAX utilities or Sys.Net.WebServiceProxy class available in ASP.NET AJAX client library.
Support UpdatePanel and partial-page Rendering.

How to Use MvcScriptManager

Please see the attached Readme.pdf.

Who's using this code/library?

If you use this code in your project, please drop me a message.

Updated Wiki: Home

thuang — Thu, 04 Jun 2009 23:32:53 GMT

Project Description

Features

Script combining. Scripts declared with MvcScriptManager will be dynamically combined into a single script file request when the page is rendered.
Render localized resources for stand-alone script files. Localized strings will be appended to the script if specified.
Support script crunching in release mode. Crunching can be enabled/disabled for each script.
Support configurable HTTP compression and expiration setting when outputing scripts.
Script content caching with file dependency. Script file content is cached so that rendering combined script file will be much more performant. Cache dependency is linked to the physical file therefore any script update in the file system will be reflected in the cache instantly.
Support rendering scripts in debug/release mode based on the running environment.
Resolving different paths for stand-alone script files.
Support multiple MvcScriptManager's on a single page (or master page).

What MvcScriptManager Won't Offer

Below are the things MvcScriptManager doesn't (and probably won't) offer in case you are used to using the ScriptManager and assume these features are included:

Support for ASP.NET Ajax extensibility model. In my opinion, with ASP.NET MVC Framework and jQuery, writing ajax script/extender controls is no longer necessary.
Support for embedded script files. We should avoid embedding script files in assembly anyway because updates of script will require a rebuild of the project which is not ideal.
Provide access to web methods from script by registering web services. This is overhead and you can totally avoid it by either using jQuery’s AJAX utilities or Sys.Net.WebServiceProxy class available in ASP.NET AJAX client library.
Support UpdatePanel and partial-page Rendering.

How to Use MvcScriptManager

Please see the attached Readme.pdf.

Who's using this code/library?

If you use this code in your project, please drop me a message.

Updated Wiki: Home

thuang — Thu, 26 Feb 2009 08:52:53 GMT

Project Description

Features

Script combining. Scripts declared with MvcScriptManager will be dynamically combined into a single script file request when the page is rendered.
Render localized resources for stand-alone script files. Localized strings will be appended to the script if specified.
Support script crunching in release mode. Crunching can be enabled/disabled for each script.
Support configurable HTTP compression and expiration setting when outputing scripts.
Script content caching with file dependency. Script file content is cached so that rendering combined script file will be much more performant. Cache dependency is linked to the physical file therefore any script update in the file system will be reflected in the cache instantly.
Support rendering scripts in debug/release mode based on the running environment.
Resolving different paths for stand-alone script files.
Support multiple MvcScriptManager's on a single page (or master page).

What MvcScriptManager Won't Offer

Below are the things MvcScriptManager doesn't (and probably won't) offer in case you are used to using the ScriptManager and assume these features are included:

Support for ASP.NET Ajax extensibility model. In my opinion, with ASP.NET MVC Framework and jQuery, writing ajax script/extender controls is no longer necessary.
Support for embedded script files. We should avoid embedding script files in assembly anyway because updates of script will require a rebuild of the project which is not ideal.
Provide access to web methods from script by registering web services. This is overhead and you can totally avoid it by either using jQuery’s AJAX utilities or Sys.Net.WebServiceProxy class available in ASP.NET AJAX client library.
Support UpdatePanel and partial-page Rendering.

How to Use MvcScriptManager

Please see the attached Readme.pdf.

Who's using this code/library?

If you use this code in your project, please drop me a message.

Updated Wiki: Home

thuang — Fri, 20 Feb 2009 01:02:26 GMT

Project Description

Features

Script combining. Scripts declared with MvcScriptManager will be dynamically combined into a single script file request when the page is rendered.
Render localized resources for stand-alone script files. Localized strings will be appended to the script if specified.
Support script crunching in release mode. Crunching can be enabled/disabled for each script.
Support configurable HTTP compression and expiration setting when outputing scripts.
Script content caching with file dependency. Script file content is cached so that rendering combined script file will be much more performant. Cache dependency is linked to the physical file therefore any script update in the file system will be reflected in the cache instantly.
Support rendering scripts in debug/release mode based on the running environment.
Resolving different paths for stand-alone script files.
Support multiple MvcScriptManager's on a single page (or master page).

What MvcScriptManager Won't Offer

Below are the things MvcScriptManager doesn't (and probably won't) offer in case you are used to using the ScriptManager and assume these features are included:

Support for ASP.NET Ajax extensibility model. In my opinion, with ASP.NET MVC Framework and jQuery, writing ajax script/extender controls is no longer necessary.
Support for embedded script files. We should avoid embedding script files in assembly anyway because updates of script will require a rebuild of the project which is not ideal.
Provide access to web methods from script by registering web services. This is overhead and you can totally avoid it by either using jQuery’s AJAX utilities or Sys.Net.WebServiceProxy class available in ASP.NET AJAX client library.
Support UpdatePanel and partial-page Rendering.

How to Use MvcScriptManager

Please see the attached Readme.pdf.

Who's using this code/library?

If you use this code in your project, please drop me a message so we can include it in this list!

Updated Wiki: Home

thuang — Sat, 14 Feb 2009 02:41:28 GMT

Project Description

Features

Script combining. Scripts declared with MvcScriptManager will be dynamically combined into a single script file request when the page is rendered.
Render localized resources for stand-alone script files. Localized strings will be appended to the script if specified.
Support configurable HTTP compression and expiration setting when outputing scripts.
Script content caching with file dependency. Script file content is cached so that rendering combined script file will be much more performant. Cache dependency is linked to the physical file therefore any script update in the file system will be reflected in the cache instantly.
Support rendering scripts in debug/release mode based on the running environment.
Resolving different paths for stand-alone script files.
Support multiple MvcScriptManager's on a single page (or master page).

What MvcScriptManager Won't Offer

Below are the things MvcScriptManager doesn't (and probably won't) offer in case you are used to using the ScriptManager and assume these features are included:

Support for ASP.NET Ajax extensibility model. In my opinion, with ASP.NET MVC Framework and jQuery, writing ajax script/extender controls is no longer necessary.
Support for embedded script files. We should avoid embedding script files in assembly anyway because updates of script will require a rebuild of the project which is not ideal.
Provide access to web methods from script by registering web services. This is overhead and you can totally avoid it by either using jQuery’s AJAX utilities or Sys.Net.WebServiceProxy class available in ASP.NET AJAX client library.
Support UpdatePanel and partial-page Rendering.

How to Use MvcScriptManager

Please see the attached Readme.pdf.

Who's using this code/library?

If you use this code in your project, please drop us a message so we can include it in this list!

Updated Wiki: Home

thuang — Sat, 14 Feb 2009 02:37:57 GMT

Project Description

Features

Script combining. Scripts declared with MvcScriptManager will be dynamically combined into a single script file request when the page is rendered.
Render localized resources for stand-alone script files. Localized strings will be appended to the script if specified.
Support configurable HTTP compression and expiration setting when outputing scripts.
Script content caching with file dependency. Script file content is cached so that rendering combined script file will be much more performant. Cache dependency is linked to the physical file therefore any script update in the file system will be reflected in the cache instantly.
Support rendering scripts in debug/release mode based on the running environment.
Resolving different paths for stand-alone script files.
Support multiple MvcScriptManager's on a single page (or master page).

What MvcScriptManager Won't Offer

Below are the things MvcScriptManager doesn't (and probably won't) offer in case you are used to using the ScriptManager and assume these features are included:

Support for ASP.NET Ajax extensibility model. In my opinion, with ASP.NET MVC Framework and jQuery, writing ajax script/extender controls is no longer necessary.
Support for embedded script files. We should avoid embedding script files in assembly anyway because updates of script will require a rebuild of the project which is not ideal.
Provide access to web methods from script by registering web services. This is overhead and you can totally avoid it by either using jQuery’s AJAX utilities or Sys.Net.WebServiceProxy class available in ASP.NET AJAX client library.
Support UpdatePanel and partial-page Rendering.

How to Use MvcScriptManager

Please see the attached Readme.pdf.

Who's using this code/library?
If you use this code in your project, please drop us a message so we can include it in this list!

Updated Wiki: Home

thuang — Tue, 10 Feb 2009 04:03:22 GMT

Project Description

Features

Script combining. Scripts declared with MvcScriptManager will be dynamically combined into a single script file request when the page is rendered.
Render localized resources for stand-alone script files. Localized strings will be appended to the script if specified.
Support configurable HTTP compression and expiration setting when outputing scripts.
Script content caching with file dependency. Script file content is cached so that rendering combined script file will be much more performant. Cache dependency is linked to the physical file therefore any script update in the file system will be reflected in the cache instantly.
Support rendering scripts in debug/release mode based on the running environment.
Resolving different paths for stand-alone script files.
Support multiple MvcScriptManager's on a single page (or master page).

What MvcScriptManager Won't Offer

Below are the things MvcScriptManager doesn't (and probably won't) offer in case you are used to using the ScriptManager and assume these features are included:

Support for ASP.NET Ajax extensibility model. In my opinion, with ASP.NET MVC Framework and jQuery, writing ajax script/extender controls is no longer necessary.
Support for embedded script files. We should avoid embedding script files in assembly anyway because updates of script will require a rebuild of the project which is not ideal.
Provide access to web methods from script by registering web services. This is overhead and you can totally avoid it by either using jQuery’s AJAX utilities or Sys.Net.WebServiceProxy class available in ASP.NET AJAX client library.
Support UpdatePanel and partial-page Rendering.

How to Use MvcScriptManager

Please see the attached Readme.pdf.

Updated Wiki: Home

thuang — Tue, 10 Feb 2009 03:58:03 GMT

Project Description

Features

Script combining. Scripts declared with MvcScriptManager will be dynamically combined into a single script file request when the page is rendered.
Render localized resources for stand-alone script files. Localized strings will be appended to the script if specified.
Support configurable HTTP compression and expiration setting when outputing scripts.
Script content caching with file dependency. Script file content is cached so that rendering combined script file will be much more performant. Cache dependency is linked to the physical file therefore any script update in the file system will be reflected in the cache instantly.
Support rendering scripts in debug/release mode based on the running environment.
Resolving different paths for stand-alone script files.
Support multiple MvcScriptManager's on a single page (or master page).

What MvcScriptManager Won't Offer

Below are the things MvcScriptManager doesn't (and probably won't) offer in case you are used to using the ScriptManager and assume these features are included:

Support for ASP.NET Ajax extensibility model. In my opinion, with ASP.NET MVC Framework and jQuery, writing ajax script/extender controls is no longer necessary.
Support for embedded script files. We should avoid embedding script files in assembly anyway because updates of script will require a rebuild of the project which is not ideal.
Provide access to web methods from script by registering web services. This is overhead and you can totally avoid it by either using jQuery’s AJAX utilities or Sys.Net.WebServiceProxy class available in ASP.NET AJAX client library.
Support UpdatePanel and partial-page Rendering.

How to Use MvcScriptManager

Please see the attached Readme.pdf.

Updated Wiki: Home

thuang — Fri, 23 Jan 2009 07:37:23 GMT

Project Description

Features

Script combining. Scripts declared with MvcScriptManager will be dynamically combined into a single script file request when the page is rendered.
Render localized resources for stand-alone script files. Localized strings will be appended to the script if specified.
Support configurable script output compression setting.
Script content caching with file dependency. Script file content is cached so that rendering combined script file will be much more performant. Cache dependency is linked to the physical file therefore any script update in the file system will be reflected in the cache instantly.
Resolving different paths for stand-alone script files.

What MvcScriptManager Won't Offer

Below are the things MvcScriptManager doesn't (and probably won't) offer in case you are used to using the ScriptManager and assume these features are included:

Support for ASP.NET Ajax extensibility model. In my opinion, with ASP.NET MVC Framework and jQuery, writing ajax script/extender controls is no longer necessary.
Support for embedded script files. We should avoid embedding script files in assembly anyway because updates of script will require a rebuild which is not ideal.
Provide access to web methods from script by registering web services.
Support UpdatePanel and partial-page Rendering.

How to Use MvcScriptManager

Please see the attached Readme.pdf.

Updated Wiki: Home

thuang — Tue, 20 Jan 2009 06:12:18 GMT

Project Description

Features

Script combining. Scripts declared with MvcScriptManager will be dynamically combined into a single script file request when the page is rendered.
Render localized resources for stand-alone script files.
Support configurable script output compression setting and browser caching control setting.
Resolving different paths for stand-alone script files.

What MvcScriptManager Won't Offer

Below are the things MvcScriptManager doesn't (and probably won't) offer in case you are used to using the ScriptManager and assume these features are included:

Support for ASP.NET Ajax extensibility model. In my opinion, with ASP.NET MVC Framework and jQuery, writing ajax script/extender controls is no longer necessary.
Support for embedded script files. We should avoid embedding script files in assembly anyway because updates of script will require a rebuild which is not ideal.
Provide access to web methods from script by registering web services.
Support UpdatePanel and partial-page Rendering.

How to Use MvcScriptManager

Please see the attached Readme.pdf.