Preferred way to use config settings in asp.net mvc master page

My Problem: I have an MVC3 application where all views use a common master page. The master page has many links to other (internal) sites. I need to be able to change the domain of these links depending on the deployment environment (e.g. staging.blah.com, www.blah.com, dev.blah.com etc). This domain is stored in the web.config.

There are numerous ways of doing this, but I am looking for some sort of consensus as to the preferred method. Here are some options but I am open to any suggestions:

(1) reference appsettings from master page directly. This is the simplest and most common approach but I am not particularly keen on reading the web.config and concatenate the url throughout the master page code. In fact, I am not sure that I like the idea of the view accessing the web.config at all.

(2) stick the appsetting value in viewdata/viewbag using a custom action filter which reads the config. concatenate in the page as before.

(3) as (2), but inject appsetting value in via contructor injection rather than reading it within the filter.

(4) create a base class for all my strongly typed viewmodels and populate with the appsetting using a custom action filter.

(5) create an htmlhelper that takes in the path and internally reads the appsetting and concatenates.

(6) create a custom view base class, inject in appsetting value and make available as property or function that takes in path and concat开发者_Go百科enates.

Just to add that typically when the master page requires data, I like to use Html.Action, but this is not possible in the case of these URLs that are used throughout the master page.

Thoughts?

(5) create an htmlhelper that takes in the path and internally reads the appsetting and concatenates.

I would go with this one. Your custom HTML helper could look something like this:

<%= Html.ExternalActionLink(
    "link text", 
    new { path = "/foo/bar.php" }
    new { param1 = "value1", param2 = "value2" }
) %>

and could emit the following HTML:

<a href="http://dev.blah.com/foo/bar.php?param1=value1&param2=value2">link text</a>

What I have done in the past is use viewdata/viewbag in my master page and populate its values in my base controller. The base controller in turn called another class to do the work of reading the values from the web.config.

This way the view is pretty clean (e.g. it does not contain code to read appsettings) and I don't need to create a base view model that matches all my views that use the master.

This approach has the disadvantage that uses a viewdata/viewbag but I decided that was OK in my case and extremely easy to implement.