# 75 - Introdction to S#arp Architecture

I am currently watching this and the autor mentions that your controllers should be in a seperate assembly. I don't understand this thinking and would love some more explaination on this reasoning.

Joe,

There's some debate about that actually. Check out the discussion thread on it here: http://groups.google.com/group/sharp-architecture/browse_thread/thread/16c953466e2689b2/983ac8af9dfb7a72?hl=en&lnk=gst&q=controllers+assembly#983ac8af9dfb7a72

I did exactly the same, just with a customer table.

Select's work, but creating new or updating existing always leads to this error:

System.IndexOutOfRangeException: Invalid index 4 for this SqlParameterCollection with Count=4.

Does anybody knows what I'm doing wrong?

I found it, searching for ~5h? well, it was a stupid copy/paste error:

Map(x => x.Firstname, "cFirstname");
Map(x => x.Lastname, "cFirstname");

(first and lastname map to same column ...)

thanks for the dimecasts, they are excellent!

Thanks for the dimecast.  I've been playing around with the architecture for a bit now and i have to say that it is still definately in its infancy.  The lack of strong examples (northwind w/CRUD is a joke) and limited community support kills any immediate benefits. I would be very interested to see a dimecast on implementing search capability since this is one of the major missing examples at this time. 

Wes,

I think that's an issue with nomenclature. It's not so much an architecture as it is a starting point for MVC apps with some useful base classes. Almost any question that asks, "How can you do this in Sharp Architecture?" can be generalized to "How can I do this in MVC?" I just started an MVC project that doesn't require a database. I used the Sharp project template to create my starting structure, then ripped out all the data access classes and the CRUD project. The benefit is that the projects are all there with references set up and I can still use the testing helpers. Made it a lot easier than starting from scratch with a single MVC web application project.

Kyle,

I agree and believe that i overstated the limitations of Sharp Architecture.  After reviewing numerous tutorials on Asp.net i came to the realization that like you said the Sharp Project is a starting point.  I was expecting it to be more like Codeigniter which i'm very familiar with.  Nevertheless, i'm quickly beginning to love the Sharp Project. 

Still having problems implementing search functionality, mostly related to my lack of knowledge in regards to asp.net mvc.  Just can't seem to put a search into place that utilizes pagination using nhibernate. Thanks again for the dimecasts.

I have to admit i liked wat i just saw.

NHibernate, MvcContrib and the default creation of all the projects like Controllers, Core. I suppose i have to S#arp Architecture with MVC from now on.

Where can we view the other videocasts  s#arp with webservices?