public drop designer gives readonly property error

Apr 23, 2008 at 3:18 AM
You have probably found this but for other people using the prism drop

The designer dies because the types dont match and the designer is too stupid to work out the interfaces is for that type

In RegionManager

change


public static void SetRegionManagerServiceScope(DependencyObject containerElement, IRegionManagerService regionManager)
{
containerElement.SetValue(RegionManagerServiceScopeProperty, regionManager);
}

to

public static void SetRegionManagerServiceScope(DependencyObject containerElement, RegionManagerService regionManager)
{
containerElement.SetValue(RegionManagerServiceScopeProperty, regionManager);
}


and its happy.

With regard to the project talk about throwing the baby out with the Bath water.. just kididng i think the simplicity is well warranted due to WPF's features. Any time you get wrid of half the user code for the same result its got to be a good thing.

I still recomment using eventbroker.. and some command samples .

Regards,

Ben