Comments on: ASP.NET MVC tip – Don’t use the Content or Scripts directories for view specific files

By: Derek Morrison

Derek Morrison — Fri, 05 Jun 2009 14:47:54 +0000

This sounds like a good idea, but when I tried to do it, I couldn’t seem to access the JavaScript files stored alongside aspx pages in the Views folder. I’m trying to diagnose it now, but I’m thinking it’s because routing is blocking a direct request for the .js file inside the views folder. Any ideas, anyone?

By: zihotki

zihotki — Fri, 20 Mar 2009 01:06:17 +0000

*typo*
..make calls to DB in views too

By: zihotki

zihotki — Fri, 20 Mar 2009 01:05:05 +0000

This is some kind of Separation of Concerns. I prefer to store scripts in scripts folder, css and images in contents folder and c# code – in some other folders. But you can mix all of them – place views with controller and other related files in the same folder. And even you can easily use codebehind files and make calls to DB too.

By: Scott

Scott — Tue, 17 Mar 2009 20:55:59 +0000

Glyn: There’s nothing preventing you from concatenating your CSS and JS files either in a post-build step or server-side using a handler. In that case, it doesn’t really matter where the files are physically.

By: Glyn Darkin

Glyn Darkin — Tue, 17 Mar 2009 20:17:08 +0000

To increase performance you should be bundling your scripts and css into as few files as possible. This is to reduce calls from the client to the server and speed up page load time. Therefore splitting your files up is not the greatest idea.

By: Patrick Veverka

Patrick Veverka — Tue, 17 Mar 2009 16:53:03 +0000

Hopefully this makes it through

While I think that’s an excellent idea for organization, I think that the Javascript Auto Include plugin for Rails does it up a little more elegantly. It creates a directory structure for you to place your JS files organized by view.

If only there were something similar for MVC

I put some explanatory code in my response: http://bit.ly/pR5Na