Views in Design view/Design time (controls not showing up)

Topics: Prism v2 - WPF 4
Jul 30, 2010 at 10:59 AM


I'm a prism newbie, I can't find any answer here but I managed to couple everything together, but was wandering:

I have views (user control) witch I use as such:


<ItemsControl Grid.Row="0" Name="MenuRegion" cal:RegionManager.RegionName="MenuRegion" />

And the corrisponding module:

_regionManager.RegisterViewWithRegion("MenuRegion", typeof(Views.PlannerMenu));


So my question is when in design time my Shell.xaml design view is empty, is there a way to get the designer to work with prism like normal usercontrols ?

Plesase if I'm ask me if this explanation isn't clear.

Any light on this matter will be highly appreciated :)


Jul 30, 2010 at 10:02 PM

When you use Regions in Prism, the region contents and layout are determined dynamically at runtime. In the designer, there is no way for the designer to determine the runtime contents of the regions.  You should be able to see the top level layout of the regions within the shell, and see each view's layout in the designer for the individual xaml files, but you will not be able to see the whole, integrated application without running it.

I hope that helps, even if it was not the answer you wanted,

Michael Puleio

Aug 4, 2010 at 9:21 AM


Yes it helps, even when it is not the answer I wanted :)


Aug 4, 2010 at 11:04 AM

This a part where Prism (and Blend) could progress since it forces us to make a tradeoff between Architectural Concerns (modularity) and good UX Design ( I mean integrating a UX team where all the people have not a developer background) . 

The designer needs to see the real interface at design time to tune the UI easily (the devil is always in the details) . That's what Blend was made for after all :) .  If the developer has made a lot of modules (worst case scenario,  one per view... :) ) the designer's work begins to look like hell or close to it... And he returns to work with Illustrator or Powerpoint letting the developpers implement the view as they can (that's basically what we were doing before WPF or Silverlight and the Developer/Designer Workflow :) ...).

I'm still waiting some guidance concerning Blendability and View Composition. Views are often nested in composite applications and Designers needs to work on "the big picture".  For the moment  I'm giving to the UX team a mock application statically referencing modules. I use custom behaviors to inject  mock Resource Views in the Regions Content Property at DesignTime. But this is not really satisfactory.    

Any ideas welcome.