Hi Imar,
At the beginning of your books you note: "You must use the Web Site Project model if you want to follow along with this book". At various times I wondered if this was the right choice as many examples found outside of this book, for solving problems not specifically covered by the book, use Web Applications and MVC. Several times I wandered into MVC and each time decided it was overkill for a relatively simple, non-team, non-enterprise type of web site. And, I really didn't want to spend the time to learn the MVC technology.
The latest issue arose with my decision to develop a mini version of my site using jQuery Mobile. This technology seemed pretty easy to learn and I felt I could reuse much of the code I developed by following your book. You kindly went beyond the scope of your book to suggest using MS Web Api to reuse my EF-linq code for DB access. This was a very good suggestion but I soon discovered that most of the Web Api examples floating around on the internet used MVC (and, of course C#). Eventually (but painfully), I found enough info to create a first version of my mobile app.
In the end, the code needed to employ the Web Api in a simple web site turned out to also be extremely simple. No Web Application or MVC needed - once again a Web Site Project works just fine.
This last experience confirms again that sticking with a Web Site Project is the right strategy for an web site like mine - I wish I could say the same for sticking with
VB vs C #.
I assume the new book will continue with the Web Site Project approach?