Ok i'm thoroughly confused -- there seems to be some gaping continuity issues, unless I've missed a whole section somewhere?

So chapter 4, models .. got us to build a StoreManagerController, cool .. got that all to work; although I wasted a little time trying to get my SQL connection string to work, only to find I needed it placed in the debug version of Web.config ..

Read on to chapter 5, and the whole layout of the MvcMusicStore has changed, on page 97, it mentions adding a <form> section 'just below the promotion div' ... err? promotion div? At this point my Index view of my homecontroller still is pretty much the basic 'sample' MVC app ... I don't see a div -- the only <div> in Index.cshtml is <div class="content-wrapper">

I scan forward a page or two and see the image show in figure 5-2 ... The ASP.NET MVC MUSIC STORE ... with Genres down the left, and Home, Sture, Cart, Admin across the top .... how on earth did we arrive at that?

Brian.

I've just encountered the same problem...what is going on with that? Did no body proof read this? At what point of the ASP.NET MVC Music Store are we supposed to be at? I have gone back over the previous pages since the last example and nowhere did it tell us to use a different project.

I am having trouble too. So, I posted a new thread with a subject that was a little more clear about my feelings, but here is what it comes down to for me: The explainations seem to make sense but then when I try to follow the blocks of code and create a example, the lack of clear instructions and notes of what to implment/not implement & etc. are just making this book a major source of frustration

I believe that is what it's supposed to look like in the end.

I agree, the book does NOT have very good continuity and it's confusing when the code the author gives is supposed to be just an example or when it's code were are supposed to actually type in.

I've found other issues where models are given that contain other classes that are never implemented in the book.

It's too bad because the book itself touches on great subjects. Also, I guess we need to remember that "Professional" is supposed to mean that you have some experience, but even some pros would probably be lost.

I have yet to find one good MVC book that can actually take someone by the hand that hasn't used MVC before and actually guide them through it cleanly. They all seem to have good and bad points.

What I've done with this book is just to swallow my pride and roll up my sleeves and attempt to make it work. What I can say is, that definitely reinforces the concepts into my head and my more apt to remember it than just blindly typing in code. Usually, that's how you learn, especially in the real world. You run into an issue that stumps you. You fight through it, getting help from either the internet or other people, and eventually you figure it out. I find when that happens, I tend to not forget what I learned from that experience that helps me grow as a developer. It's worked that way for the past 15+ years for me!

I don't know if that was the intent of the author, but I tend to believe it wasn't. However, in the end, it is making me a better MVC programmer in the end.

But, I do agree the continuity is not very good. Not sure how the previous editions were, but I have heard from some that the MVC 2 book was pretty good.

Well you have mentioned great information, I was searching type of information from a very long time, and finally I got it.