Question

I’m working on a site where the images and other resources will be located on a separate domain from the main content of the site. We will use something like ‘www.example.com’ for the main site, and then ‘images.example.com’ for all extra resources for styles, etc.

When developing the site I will keep all of these resources on local dev. machines. The challenge here is keeping CSS references consistent between the production server and development environments.

What I was thinking of doing was creating a web.config key that would store the URL of the images server. Then, when switching from development to production I could just change the web.config value and everything would be done.

Is there any way to add a value to a CSS file, dynamically or otherwise, from some place in a config or C# class? Or am I going about this the wrong way?

Also, I’m limited to using .NET 2.0 if that makes a difference.

UPDATE
To expand on this a little more, I know I can use a web.config setting for server controls’ URLs. Those are already generated dynamically. What I’m more interested in is what options I have for modifying (or doing ‘something‘) to static CSS files that will allow me to change URLs for things such as background image resources that would be referenced in CSS. Is there anything I can do besides find/replacing the values using my IDE? Perhaps something that can be done automatically with a deployment script?

Answer 1

Is keeping the CSS file on the image server an option? If that it possible, you could make all the image references relative, and then you just need to update the link to the css file.

<link rel='stylesheet' href='<%= ConfigurationManager.AppSettings('css-server') %>style.css' /> 

If you still want to send or generate a css file dynamically:

css files don’t have to end in css. aspx is fine. You could do this:

<link rel='stylesheet' href='style.aspx' /> 

and then in your style.aspx page:

protected void page_load(){     Response.ContentType = 'text/css';     if (ConfigurationManager.AppSettings('css-server') == 'local') {         Server.Transfer('css/local.css');     } else {         Server.Transfer('css/production.css');     }    } 

If you still want to dynamically generate a css file, I’d use an HttpHandler, set the contenttype to ‘text/css’, then generate the css with Response.Write. If you insist on having the page end in css, you could always register css to go to asp.net in IIS, then on incoming requests in global.asax application_Begin request, if the file ends in .css, use httpcontext.current.rewritepath to your handler.

This will have a net effect of style.css being dynamically generated at runtime.