System.Windows.Data Warning: 40 with FallbackValue - only on some machines

[Brian Noyes]

Got one that is driving me a little bonkers that I'm hoping one of you geniuses has solved before or can maybe guess at a cause....

We have a view that is reused across two view models. There are some controls in the view bound to properties that exist on one of the view models, but not on the others and the field gets hidden through a converter depending on which view model it is bound to.

We originally naturally had binding errors being dumped in the output window when the view was rendered with the view model that is missing the properties because even though the control is hidden, its binding is still trying to resolve against the non-existent property. FallbackValue to the rescue... we thought. Added FallbackValue to those bindings and the problem went away... on the developers machine who put it there along with several others, but several different machines are still seeing System.Windows.Data Warning: 40 for those properties even with the FallbackValue in place.

Same code base, verified (Get Latest) on all machines, some see the binding warnings, some do not. No one seeing or not seeing them recalls configuring anything special with their environment.

Any ideas what could cause this?

Thanks

Brian

--
-----------------------------------------
Brian Noyes
Chief Architect, IDesign Inc
Microsoft Regional Director / MVP
http://www.idesign.net
+1 703-447-3712
-----------------------------------------

[Brian Noyes]

Never mind - found it. Tools > Options > Debugging > Output Window > WPF > Data Binding. The ones showing it were set to Warning, the ones not set to Error. Not sure how they were different since no one ever set those explicitly. Any ideas there?

[Karl Shifflett]

Brian,

I wrote about this here:  http://karlshifflett.wordpress.com/2010/06/24/visual-studio-2010-wpf-trace-settings-default-is-incorrect/

Best,

Karl

[Brian Noyes]

Right, but my rumination after figuring out where the setting was was to wonder what else might set that since none of us set it explicitly but we had a mix of two settings. Two of the developers are on a company provided laptop with a standard build, but had a different setting from each other.

Is this one of those "If you select VB profile, you can't handle the truth!" :) kind of things where it is set differently based on the selected profile?

[karl shifflett]

Brian,

This could have been corrected by a VS SP or update.  I remember writing up a bug against this.

Not sure if this is profile related. 

Karl