Database driven asp.net MVC application

I have a CRUD application written in Classic ASP (not .net) which transfers (routes) page requests to relevant servers using a loadbalancer DLL.

It works like this:

1. Someone requests for www.mywebsite.com/products

2. There is an index.asp under folder products that redirect开发者_如何转开发s the request to either:

   http://www1.mywebsite.com/products
   

   or

   http://www2.mywebsite.com/products
   

   based on a loadbalancer logic.

Another scenario:

1. Someone requests for www.mywebsite.com/products/details

2. There is a index.asp under the sub folder details within the products folder that redirects the request to either:

   http://www1.mywebsite.com/products/details
   

   or

   http://www2.mywebsite.com/products/details
   

   based on loadbalancer logic

The main issue with application is whenever I include a new page, I need to create a folder and index.asp page to redirect the page.

We have a CMS database which contains the details of all pages. So I want to create an MVC application to replace the existing Classic ASP application.

But I didn't find any database driven MVC applications and I'm bit confused by routing. Do I need to create a separate route for each main folder I have or should I create a generic route for all pages.

Any help would be appreciated.

You don't have to migrate to ASP.NET MVC just for the URL rewriting.

IIS 7 does have an integrated URL rewrite module and ASP.NET 4 includes routing as well.

• IIS URL Rewriting and ASP.NET Routing
• URL Rewriting in ASP.NET

Anyhow, if you search e.g. on Codeplex for ASP.NET MVC projects, you'll find a lot of them which are database driven.

You don't need to create individual routes for each seperate item. Think about the concept of querystrings (?id=15&day=monday). URL rewriting is pretty much the same.

Update

I've overseen that your talking about classic ASP.

The build in URL rewrite module in IIS 7 works also fine with classic ASP. If you are having an older IIS version you need a 3rd party ISAPI rewrite module.

Anyhow, switch it to ASP.NET MVC ;)

MVC would lend itself very well to sorting your routing problem. So would ASP.NET 4.

However, the problem you have is that you don't know enough to ask a precise question. Hence your confusion with routing in MVC.

I would therefore suggest reading the nerddinners tutorial. You can get a PDF download for free. To go a step further, read Stephen Sandersons book on MVC 2 (or MVC3 in a couple of months).

If you follow the nerddinners tutorial and Stephen Sanderson's tutorial, that will give you a better idea of how it works.

In short, this is how MVC works:

In MVC, you forget about files and folders.

Instead, you have Controllers and actions. The routes map the requests to the right controller and action.

The code in the actions then decide which View to stuff full of data (from a database or wherever, it doesn't matter). The Views are just templates that are told what to do and what data to display.

The Controllers ask the Model for the data that they want.

Ie, the data access is all done in the Model, neatly separated from the User Interface.

M: Model V: Views C: Controller

The above is probably meaningless to you. It is a VERY different mindset to ASP classic.

If you are coming from old ASP, you will have a long hike, but it can be done. I came from Access. Anyway, read the books, follow the tutorial and see if it is for you.

When you are ready, we will still be here to help with more precise questions.

Asp.net MVC routing in your migrated application

Based on requests you've shown here you can sort everything up with just default route:

{controller}/{action}/{id}

In your case you'd have a ProductsController with all the actions you need.

Load balancing application

But having an Asp.net MVC application is just one part. This application will run on both load balanced servers. All redirecting should be done before they hit the MVC application.

If you intend to continue using the same loadbalancer DLL you could create a different Asp.net MVC application with only one route definition:

{*path}

and a single controller and action that does it all:

public Load: Controller
{
    public ActionResult Balance(path)
    {
        // decide for web server and attach path to subdomain
    }
}

This should do the trick just fine as long as the overhead of this action is very small. Otherwise your load balancing logic will become the bottleneck of your application since all requests go through this load balancer (it does that now as well so bare in mind this is no different now; never mind the authentication process on different subdomains you may be using).

Load balancing alternative

You should consider using the web farm balancing capabilities on the IIS 7 that will run your application on several web servers (because that's what your load balancing does in the first place). Search the web for web farm information. You can start with this:

http://www.iis.net/download/webfarmframework