Areas - Good or Bad?
I notice you have not opted for Areas in your Enterprise solution, but instead to split each layer into projects and in each project have a folder for each 'would be' Area. I think this makes a lot of sense and leads to a cleaner solution.
Which makes me question the usage of Areas in an Enterprise site. I guess it makes sense if you want to totally isolate a module so you could perhaps import it into other websites, otherwise taking the separation approach in the book you would only be left with a controller in each area. Also I don't like the way Areas add an extra top level to your RESTfull URL, although I believe the area can be omitted if your controller names are unique.
Perhaps Areas are useful in medium complexity sites or where modules need to be copied/imported into other websites.
Excellent book, one I keep rereading to get more out of..