How to separate model, view and controller in an ASP.NET MVC app into different assemblies

At the moment I am trying to get into the ASP.NET MVC framework.
For most of my test applications I used a single assembly/project. This worked fine for some smaller applications. Then I wondered how I could place my model, controller and view classes into separate assemblies? In really big web-applications it is not very realistic to put everything into a single assembly/project.

Could not load file or assembly ‘Oracle.DataAccess’ or one of its dependencies. An attempt was made to load a program with an incorrect format

I have installed a Web app on IIS 7.0 Windows Server 2008 R2 64bit.
I am referring an oracle.DataAccess.dll;
When I try to access the application I get the following message:
“Could not load file or assembly ‘Oracle.DataAccess’ or one of its dependencies. An attempt was made to load a program with an incorrect format.”
Can anybody help me, please?

C# – How to change HTML elements attributes

My master page contains a list as shown here. What I’d like to do though, is add the “class=active” attribute to the list li thats currently active but I have no idea how to do this. I know that the code goes in the aspx page’s page_load event, but no idea how to access the li I need to add the attribute. Please enlighten me. Many thanks.

Best practices for integrating ASP.NET Identity – do they exist?

I’m using ASP.NET Identity with a new website and there don’t seem to be many (any?) examples of how to do this in a decoupled manner. I do not want my domain model’s DomainUser class to have to inherit from Microsoft.AspNet.Identity.EntityFramework.User, so I’ve created a class that looks like this: