ok, assuming that you mean asp.net mvc, we have to differencate between server side and client side. server side, the entity framework takes care of that, see http://stackoverflow.com/questions/19342908/entity-framework-many-to-many-mapping
client side - by the way, I am no asp programmer - this seems more like a wcf related question (using a rest service for crud operations). And, yes, it may be a bit tricky, because e.g. a json rest service needs to stick to a certain schema to accomplish that, and, further more the orm/ odm used must be aware to that schema to assemble/ reassemble the json data accordingly and needs to implement some query and routing logic (depening on where the final joins are executed, and/or how the query is passed through the layer). in the best case an atomic query is natively executed on the database and only the requested fields are returned to the client in a paginated manner. maybe the jaydata framework can help you. I think it is able to consume a variety of services (among these are wcf related stuff). so if there is no build in solution in pure wcf, consuming an odata service thith jaydata client side may be your best bet, see http://jaydata.org
Quote:In CRUD applications, you have to deal with complex data types and one-to-one, one-to-many and even many-to-many associations. Without a proper framework and no database programming experience, this can be a hard work and a pain while you want to create the application of your dreams.