Hotfix Posted for VS 2010 RC Crashing Issue

Brian in Cider, News | 0 Comments February 15, 2010

The VS 2010 RC has a serious bug that causes crashes when editing text.  The VS team has released a patch for it here:  Karl's also posted this on The Cider Blog.

Cider Performance for VS2010

Brian in Cider | 0 Comments January 8, 2010

It’s been a long time since this blog has seen any posts about Cider.  I haven’t been sleeping.  Instead, I’ve been tuning.  For the last six months I’ve been heads down focusing on the performance of Cider in VS 2010 both for WPF and for Silverlight.  ScottGu’s post about creating another public release candidate hopefully has you convinced that we’re very serious about ensuring that the performance of the product meets your expectations.  I thought it would be helpful if I talked about some of the specific things we’ve done in Cider to help with performance.


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.