Professional Asp.net 3.5 in C# and VB
Programmer to Programmer edition.

Written in part by Scott Hanselman

----

Intro.


I'm not fond of asp.net.
In part because the first sample in the book has SQL inside HTML. Holy shit.

...why don't they put a "OnPostBack" event besides OnLoad? Are we always going to put if(IsPostBack) inside only OnLoad, on all pages for special logic of getting a result?

Jeez, why isn't the code highlighted?
No screenshots of the resulting html pages?

Chapter 1.

Jeez, why would you ever want to have a strongly typed PreviousPage, where PreviousPage can be null, and has PreviousPage.IsCrossPagePostBack property?
What if I have lots of different previous pages that lead to one final page?
What does it mean if IsCrossPagePostBack is false? Will PreviousPage exist in that case?
Why would you redirect twice via a PostBackUrl AND a Response.Redirect?
Why are pagenames and IDs in strings? To deliberatelly destroy rename refactorings?

The custom BuildProviders are weird... Like, the end result is some compiled C# code, classes. So you can make these classes dynamic from some sourcefiles other than c# code. Weird.


Chapter 2.

CSS in VS - cool.
ASP.Net Server Controls:
- Web Server Controls
- HTML Server Controls
- User Controls (not controls at all)
- Cusom Controls - cool.


"Register" Javascript script methods are a joke. And awful, cruel joke. JS inside the code behind? No. JS needs IDs of elements. They used server control IDs as text - and it worked. What about Constom Controls or User Controls? Probably Fail.

Client-Side callbacks are a hack, but none the less kinda cool. Not extendable (string in, string out).

Chapter 3.