I've got a number of books, but all seem to get you to do things in a slightly different way. (Apress Pro ASP.NET MVC, Sams ASP.NET MVC, and a Manning book)
I've got to grips with the view, controller side of things, as I pretty much did that in PHP anyway, but it seems to be the model side of things where these books seem to go in their own direction.
I have one book telling me to use the entity framework wizard to create everything from an existing database. Then another book saying to create a model, put all the linq to sql stuff into it(I liked this), then use an IoC (castle windsor) to manage the connection between the model and the database, which involves creating a solution with multiple project within it, (model, UI, and interface).
It's actually getting a little confusing.
I was enjoying reading the Apress Pro ASP.NET MVC book, until it got to the point where it started talking about IoC, and wanted me to do something with castle windsor. At the minute, I don't particularly want to be relying on 3rd party stuff until I know the limitation of what .NET can provide.
Any help would be greatly appreciated.
View Complete Post