The following assemblies names has been changed:
The following assemblies were added for .NET 4.0 support:
The namespaces of the following classes have been changed to allow for shared use in the Silverlight products in future releases:
The following classes and members have been marked obsolete:
NestedPropertyChangedEventArgs – This class derived from PropertyChangedEventArgs and existed to allow a PropertyChangeNotifier/DependencyObjectNotifier derived class to optionally raise its PropertyChanged event when a property of a sub-object had been changed in an effort to chain property change notifications. This class (and the methods that used them - PropertyChangeNotifier.RaisePropertyChangedEvent(string, object, PropertyChangedEventArgs) and DependencyObjectNotifier.RaisePropertyChangedEvent(string, object, PropertyChangedEventArgs)) have been deprecated and will no longer be supported. Any usage of these members will result in a compiler error. Objects interested in receiving change notifications for a nested object could use a Binding where the path uses the multiple property syntax.
In order to use the VisualStateManager in Blend 4 (to be able to see the "States" in the "States Window"), you have to follow these steps:
The controls related templates from the DefaultStyles folder should be hooked up in blend 4. This is required because Blend cannot recreate the Ultimate UI for WPF controls templates – thus it creates some simple (wrong in the majority of cases) templates.
If the control templates are using images, they needs to be copied over to you project as well.
At some point you may notice that you are not able to change some properties (i.e. background of an element). You have to convert it to a local value, using the "Advanced Options" button (a small square on the right side of each property in the Properties window).