I'm assuming that your motivation is either:
1) You want to run a fully-customized ASP.NET UI alongside a generic Naked Objects MVC UI, targeted at different user groups, but using the same domain model.
2) You want to use Naked Objects MVC to prototype the domain model, but then deploy with a fully custom UI
Either way, before going further, you should look at another option which is to run the same domain model with the Restful Objects for .NET viewer, and then building your fully-custom UI to interface to the Restful Objects API. This would be my personal
preference - and build the UI as a single page app, which is the emerging architecture.
If, however, you definitely want your custom UI to be an ASP.NET MVC app (i.e. the HTML views are generated on the server) then you can do it. Effectively, you want to use the domain model, but not the Naked Objects framework at all.
Start by reading this thread right through: http://nakedobjects.codeplex.com/discussions/360965
I understand that Jacques now has this working (his motivation is option 1 above, but the principle is the same for option 2).