SqlDataSource.CancelSelectOnNullParameter
-
Curious feature of ASP.NET 2.0 that could be useful, but this evening I just found frustrating. The default state of this parameter on the
SqlDataSource
control istrue
which means I spent about an hour and a half trying to figure out why mySqlDataSource.Selecting
event was firing, but theSqlDataSource.Selected
event wasn't and why myRepeater
control wasn't getting populated. Personally, I think the default state of theCancelSelectOnNullParameter
should befalse
because that way, if there is a null parameter an exception is thrown and the developer has a clue as to what is happening. Whereas when it is set totrue
nothing happens and people will spend time banging heads off desks* in frustration trying to figure out what is going wrong. Just thought I'd let you all know - If you ever have the same problem. However, that said, ASP.NET 2.0 will rock your socks off!! I'm learning all the new controls and so far I've saved somewhere in the region of 80 hours of development time over doing the same job in ASP.NET 1.1. And that's with me doing the job on the learing curve at the same time! * This is dangerous because it can cause the retinas to detach.
"If a man empties his purse into his head, no man can take it away from him, for an investment in knowledge pays the best interest." -- Joseph E. O'Donnell Not getting the response you want from a question asked in an online forum: How to Ask Questions the Smart Way!
-
Curious feature of ASP.NET 2.0 that could be useful, but this evening I just found frustrating. The default state of this parameter on the
SqlDataSource
control istrue
which means I spent about an hour and a half trying to figure out why mySqlDataSource.Selecting
event was firing, but theSqlDataSource.Selected
event wasn't and why myRepeater
control wasn't getting populated. Personally, I think the default state of theCancelSelectOnNullParameter
should befalse
because that way, if there is a null parameter an exception is thrown and the developer has a clue as to what is happening. Whereas when it is set totrue
nothing happens and people will spend time banging heads off desks* in frustration trying to figure out what is going wrong. Just thought I'd let you all know - If you ever have the same problem. However, that said, ASP.NET 2.0 will rock your socks off!! I'm learning all the new controls and so far I've saved somewhere in the region of 80 hours of development time over doing the same job in ASP.NET 1.1. And that's with me doing the job on the learing curve at the same time! * This is dangerous because it can cause the retinas to detach.
"If a man empties his purse into his head, no man can take it away from him, for an investment in knowledge pays the best interest." -- Joseph E. O'Donnell Not getting the response you want from a question asked in an online forum: How to Ask Questions the Smart Way!
I have to second that! I've been playing around with Membership and Profiles - it makes authentication etc so much easier and much faster. The login/logout, CreateNewUser, ChangePassword, etc controls are just amazing - it handles everything basicly automatically!!! The only thing that has given me a headache so far was the SiteMapPath and the Menu. After a while I wasn't sure whether it was a bug or if I was just not setting the correct properties. :-D