I don’t know how to solve the error you’re referring to, but I can tell you that Silverlight works with Firefox 3.5.8. So maybe you can upgrade to the latest Firefox?

I hope this helps!

Andy

I’m glad to hear you’re interested in pair programming. In March, I’m going to try to put together an after-work pair programming session at the Sogeti office, so look for an email from me in the few couple weeks. Also, BitSlingers meets the 1st Monday of every month at Panera bread on Mason Montgomery Rd, and that’s an opportunity to pair program with some smart people (see cinnug.org).

Unfortunately I can’t post the bad code, because it belongs to a solution I built for a client. I can describe what the bad code examples were though, and hopefully that will help:

- The first example was to demonstrate the concept of DRY (don’t repeat yourself). The example wasn’t all that great, but the moral of the story was that you shouldn’t copy and paste code from one area of an application to another because less code is better. Also, shared sections of user interface code (ASPX markup, XAML, etc.) should be put into user controls to prevent duplication of UI code.
- The next example was a gigantic Page_Load event from a web page in an ASP.Net application that I developed. The Page_Load event was about 200 lines long which in itself is bad, but in addition to the length being bad, it also violates the “Single Responsibility Principle” (see the link to the UncleBob site in the slide deck). A class or method should only have one reason to exist, and that particular Page_Load was doing a ton of different things which makes it brittle and hard to maintain.

Thanks,
Andy

I’ll have to remember the warning about the next maintainer.

Can you post the “bad” .NET code, since I won’t be able to attend your live presentation?

Good posting.

Thanks,
Randy Stegbauer