So here’s an interesting point. When we have a problem when using beta code do we just naturally assume it’s a problem with the beta? I had some questions to ask the team so Alex asked me to report a bug with the BulletedList control, where the BulletStyle attribute didn’t seem to be working. He’s checked the code several times and wondered why the attribute wasn’t being acted on server side, but being passed to straight through to the client.
He’s off to a conference so I looked at the code, and spent half an hour or so trying to work out the exact situation where it wasn’t working, so I could provide a good code sample along with the bug. It’s only then that I spotted he’d mis-spelled the attribute as BulletSyle – missing the t from the Style. We’d both read what we’d wanted to read, rather than what was there, and both decided it was “that damn beta code”.
Of course IntelliSense would have picked it up if we’d been using VS (only had the framework on that machine at the time), but it’s interesting the way we both assumed something else was wrong; our perception being that beta software was more likely to be wrong than our code, which two of us had checked. We expect beta code to be flakey, hence the assumption. Of course we all know assumptions are bad, but it’s amazing how easily you fall into the trap.
Now I’ve publicly embarrased myself, it’s time to try and do some coding that actually works.