Help Cider Name an API, Part I of Many

Brian in Cider | 0 Comments November 9, 2006

Jim and Richard are grapling with the naming of the adorner placement APIs in Cider. Here's a link to Jim's blog. Check it out, and let Jim know your favorite name.

Naming Controls in Cider

Brian in Cider | 22 Comments September 13, 2006

Since the dawn of time (OK, since Visual Basic 1, but that was a long time ago in computer time) designers have been automatically assigning names to controls. Plop a button on a form and it was given a wonderful name like "Button1". But at least it got a name. You had no control over this in Visual Basic. Controls all had to have names, so even if you had a form that contained nothing but lots of static labels your code still had access to Label1 through Label200.

Windows Forms in VS.NET 2005 changed that a bit. We still required names on controls because too many things broke if we didn't name all the controls with unique names. However, we allowed you to flip a bit that would cause the code generator to generate the variable as a local rather than as a member variable. Now all your labels and static images could stay the heck out of your Intellisense drop downs. There was much rejoicing, except by the QA team whose test matrix doubled in size.


The Design Mode Property Redux

Brian in Cider | 6 Comments July 19, 2006

When we were looking at our options for adding a design mode property to WPF, an obvious choice was to add a dependency property to WPF that the designers would use. None of us remotely thought we could get something like that into WPF at this time. WPF ships with Vista, and Vista is down to fixing "level five recall class super double probation bugs". Or something like that. So, Sparkle and Cider knocked our heads together and came up with a late bound way of accessing a dependency property that we would each define in our own applications.


What, No Design Mode Property?

Brian in Cider | 15 Comments July 3, 2006

If you’ve written controls for Windows Forms you may have encountered a property on the control called DesignMode. This property returns false when the control is running in an application and true when the control is running in a designer. I’ve always considered this property to be a necessary evil. On one hand, we did a lot of work in Windows Forms to allow you to separate your design time logic into a separate DLL from your runtime logic, so the property is unnecessary. On the other hand, it just isn’t always practical or possible to separate all design time logic out of your runtime DLL.


New Developer Community Site for .NET 3.0

Brian in News | 0 Comments June 12, 2006

Check out the new developer community site for .NET 3.0: