I know stuff!
In web development and programming, I often come across useful tidbits that solve a problem for me. I often have those problems again and can't remember that tidbit. Now I will. Maybe you can benefit too.
The Problem
Being the security experts that they are, Microsoft is attempting to save you from yourself by providing some built in request validation in .NET. What this means is that if you have a form that has user input fields and someone types in something evil like HTML 3.0 code into it, you'll get an exciting error message telling you this isn't allowed. The idea here is of course to try and keep people from doing things like cross site scripting (XSS) on your poorly designed web site.
Read Full Article...
Here's a great little article from Smashing Magazine on some very nice options for Data Grids. Some are more attractive than others, but all seem to offer some great time saving functionality.
Read Full Article...
With many web forms, it's nice to be able to fill out some quick info and hit Enter to submit the form. With .NET where the whole page is a form this can become troublesome when there's multiple submit options on the page. Take this site for instance. When I enter my login info and hit enter I don't want to search the site, so I might want to specify my Login button as the default. In .NET 2.0, along comes the defaultbutton form attribute. Just specify which button you want to be the default (eg. defaultbutton="btnLogin") and you're good to go.
Read Full Article...
The other day I started having a strange problem with a DetailsView control inside of an AJAX Tab Panel. When the control would load, the paging links looked normal, but when I'd click on one they would all become disabled. In actuality, they were only being disabled in appearance since the paging function is associated with an onclick event rather than the actual href of the link. So why would these all become disabled?
Read Full Article...