Question: In the latest release of ASP.NET MVC 2 they have launched the concept of areas as supported by MS. However to perform this areas concept one has to create multiple separate projects. One project per area. In ASP.NET MVC 1 there were many other ways out there to support areas where you would still be working within the same project. This post is not about [whether areas are important or not](https://stackoverflow.com/questions/462458/asp-net-mvc-areas-are-they-important-to-a-large-application) but what a proper implementation would be. What is your preference for working with areas and why? What do you think of this new multi-project way of performing areas?

Here were the pre 2.0 ways to implement areas:

<http://haacked.com/archive/2008/11/04/areas-in-aspnetmvc.aspx>

<http://blog.codeville.net/2008/11/05/app-areas-in-aspnet-mvc-take-2/>

<http://devlicio.us/blogs/billy_mccafferty/archive/2009/01/22/mvc-quot-areas-quot-as-hierarchical-subfolders-under-views.aspx>

I am about to start working on a very large ASP.NET MVC project (and can't wait to dig into the 2.0 preview) and am wondering if I should use this new areas implementation or what we have already proved to work.

Answer: 
fixed it

```
$pagefixed = str_replace("href=\"/","href=\"http://www.domain.com/","$page");

```

Thanks all
You'll either need to use a regular expression (preg\_replace) or 2 str\_replaces since quotes vary.