performance - asp.net website optimization for static resources- development vs production deployment - serving static resources from subdomain -


I see a website optimizing and especially looking for CSS sprites and a subdomain ( static .mysite.com ). Reference:

We are using Cassini (which comes with Visual Studio) for development and does not support subdomain. My stable resource folder includes www.mysite.com/Contents/Static/.. It works for both Cassini and IIS7.

If I give these static properties to static.mysite.com , without changing much in my codebase (references to js / css / images), what is the most optimal way to do this? Will happen?

My concern is the fact that Cassini does not support subdomains, I think I need 2 code bases? Or should I convert my references to static properties in code base from mysite.com/contents/static to static.mysite.com ? How do you guys know about it?

PS: On one side note, it would be nice if you can tell me the good esp net performance in tuning articles (though Google helps in search)

A question about this kind of development environment and developer workflow is created.

Cassini is fine your god-env so long as you do system / user-acceptance testing against the target webserver used in the production environment.

If you want to stick to Cassini, then I would like to use a webserver, such as LPTPP, to complete static content during a different development. Once you are serving the right document route, you can forget a lot about it.

Alternatively, if you are open to running IIS, you can easily move Cassini.

For reference to static content in your code, the general approach is to create a full URL for each static resource using a variable from your master page (or config). I do not recommend any string replacement at build / deploy time.


Comments

Popular posts from this blog

sql - dynamically varied number of conditions in the 'where' statement using LINQ -

asp.net mvc - Dynamically Generated Ajax.BeginForm -

Debug on symbian -