Over my head

I've just started re-developing ListenToManchester.

I seem to do this every 6 months. It goes something like this...

A new technology comes along.

I get excited.

I begin redeveloping the site with this new technology (ie Ruby on Rails, s#arp).

I discover that the flavour of the month isnt quite as good as I expected and that my productivity isnt quite what I was promised (I usually want to have it completed in a few days).

Most recently I looked at S#arp which is a framework based on nHibernate (yay), Spring.NET (yayer) and the new MVC preview from Microsoft.

I love MVC.
I love nHibernate.
I love Spring.NET.

I dont like s#arp based upon what I've seen of the "best practice" NorthwindMVC project shipped with the project.

The NorthwindMVC.Core project contains the business logic of the application.

It also contains nHibernate mapping files.

Why would they do this??

I dont want my business tier to have any dependency upon the implementation of my data access tier!!!

Ideally I'd have a seperate project that defines interfaces i.e. ISupplierDAO (lets call it NorthwindMVC.Shared).

Using spring I'd inject an implementation of this interface into my business tier.

I dont want to care about the details of the DAO implementation in my Business layer!

This way my business and data tiers only depend upon NorthwindMVC.Shared!!

Is this really how the devs of this platform want us to use it?

Of course, I'm probably being a bit whiney. This is probably just an implementation detail.

Thoughts??

Having said all this, this framework is leaps and bounds better than what ListenTo is currently running off CSLA.NET (shudders).