With the .NET 3.5 cycle out of the way and ASP.NET 4.0 on the horizon, it's time to try and figure out a way to incorporate the many new features and techniques that have emerged \ been released into the next editions of ASP.NET books. So then, what would you put in 'Programming ASP.NET 4.0' and what would you NOT put in it? Books are supposed to be for the programming community so here's your chance to have your say.

VB is just as important as C#, and more readable.  Please show all code samples in both VB and C#, and do not relegate the VB code to "the CD" or to a download.  Please do not use "Google search stats" to justify the book being C# only.

Thank you for asking for opinions!

speednet:

VB is just as important as C#, and more readable.  Please show all code samples in both VB and C#, and do not relegate the VB code to "the CD" or to a download.  Please do not use "Google search stats" to justify the book being C# only.

Thank you for asking for opinions!

 I totally agree. I'm a VB programmer and I find it annoying when I buy a book and its only in C# with VB being an addition on a CD or whatever..

My problem with learning and using asp.net has been one of deciding on the correct models to use. I would love to see a complete dotnet site with all of the normal components of a typical business site (registration/login, blog, skins and masterpage, support forums, e-commerce, etc) and then have the code for that site explained. The site should be comprehensive so that it contains examples of as many of the dotnet components as possible and it explains why the components are used in place of alternatives. The site could be like one of the starter kits now available, except it should be written using the latest dotnet features. Is it best to use MVC? Where do you make the best usage of AJAX? Dynamic Data? etc... Take the reader through the site-building process step-by-step, starting with "Do I use Visual Web Developer or do I need Visual Studio?" and continuing on with site design and page-by-page development.

As asp.net has grown, the number of alternatives available for building a site and performing specific functions within the site has grown to a point where I no longer feel like I know if I'm choosing the correct (or best) method/component/whatever. There are lots of books explaining pieces of the dotnet framework, but I haven't found anything that puts it all together.

 If you're still stuck in the past with Visual Basic, why would you want to read a book called Programming in ASP.NET 4.0, you people aren't capable of learning new things; otherwise you would have moved to C# by now.

reach4thelasers:

 If you're still stuck in the past with Visual Basic, why would you want to read a book called Programming in ASP.NET 4.0, you people aren't capable of learning new things; otherwise you would have moved to C# by now.

I've never seen ignorance expressed quite this way before.

reach4thelasers:

 If you're still stuck in the past with Visual Basic, why would you want to read a book called Programming in ASP.NET 4.0, you people aren't capable of learning new things; otherwise you would have moved to C# by now.

Aren't capabable of learning new things?  What's new in C# that's not in VB.NET, and vice versa?

C# was my first .NET language, but recently I've been doing a project in VB.  It's been really easy transitioning back and forth, it's just a difference in syntax.

I find your fanaticism over a particular language rather odd.  It's like arguing over which font produces better code.

OK, and time. I'll try my darnedest to get VB code into the book as well as C#. Who knows, there might even be some IronRuby or IronPython in there if there is time. Anything else?

 >OK, and time. I'll try my darnedest to get VB code into the book as well as C#.

Excellent! (I am bi-lingual VB.NET / C#, but I recognise that there are far more VB.NET developers around)