Using MergedDictionaries in generic.xaml in Silverlight 3

Question

In WPF it was possible to organise the XAML for multiple user controls by keeping the markup in separate XAML files in the themes folder and then using MergedDictionaries to import them into generic.xaml:

<ResourceDictionary>
    <ResourceDictionary.MergedDictionaries>
        <ResourceDictionary Source="MyFirstControl.xaml" />
        <ResourceDictionary Source="MySecondControl.xaml" />
    </ResourceDictionary.MergedDictionaries>
</ResourceDictionary>

With the availability of the Silverlight 3 beta introducing merged dictionary support, it seemed like it might be possible to do the same with Silverlight user controls. But despite trying all combinations of build action on the merged dictionary files and the corresponding syntax for the source reference in generic.xaml, I can't seem to get it working.

Has anyone else tried? Does anyone know if it is possible and if so what I am doing wrong?

---

OK - so after numerous test projects, getting working samples in WPF and moving the XAML and C# code over to Silverlight 3 and it still failing, I did a full uninstall and reinstall of ALL the Silverlight 2 bits AND ALL the Silverlight 3 beta bits and finally got things working.

I can only assume that I somehow ended up with a faulty install of the beta - I don't know but it seemed like I was still running in the Silverlight 2 runtime despite apparently having the version 3 runtime installed.

Thanks Jared for taking a look at things and checking with the SL3 team...and thanks to Amy Dullard and Shawn Wildermuth for producing the instructions and batch files for running Silverlight 2 & 3 on the same machine.

Answer 1

I just tried the following in a user control and it worked:

<UserControl.Resources>
    <ResourceDictionary>
        <ResourceDictionary.MergedDictionaries>
            <ResourceDictionary Source="ResourcesA.xaml" />
            <ResourceDictionary Source="ResourcesB.xaml" />
        </ResourceDictionary.MergedDictionaries>
    </ResourceDictionary>
</UserControl.Resources>
<StackPanel>
    <Rectangle Width="100" Height="100" Fill="{StaticResource ResAColor}" />
    <Rectangle Width="100" Height="100" Fill="{StaticResource ResBColor}" />
</StackPanel>

But you specifically mention generic.xaml. What sort of problem are you having?

-- EDIT

Based on the additional comments, I talked with the SL3 team and got the following answer:

Works for me, using generic.xaml compiled as a Resource, and using the full resource syntax. There is a bug on not being able to use relative URIs for the Source in generic.xaml (31783) but the non-relative form should work just fine

<ResourceDictionary Source='/SilverlightClassLibrary1;component/CustomControl.xaml'/>

in generic.xaml, and modify the build actions for both generic.xaml and CustomControl.xaml to be Resource. Let me know if there’s still trouble—if you get a repro, I can take a look at it.

Does that help?

Answer 2

If MySecondControl.xaml uses a resource from MyFirstControl.xaml the order you add them to generic.xaml's ResourceDictionary won't matter. You'll need to redundantly include MyFirstControl.xaml in MySecondControl.xaml. MySecondControl.xaml should contain:

<ResourceDictionary.MergedDictionaries>
    <ResourceDictionary Source='/MyControls;component/Themes/MyFirstControl.xaml'/>
</ResourceDictionary.MergedDictionaries>
<!-- ... Contents of MySecondControl.xaml -->

Answer 3

I just worked through this issue. ResourceDictionaries do support MergedDictionaries, but for custom templated controls using Generic.xaml, Generic.xaml does not support MergedDictionaries. So there are two choices: (1) you either pile all your templates into Generic.xaml; or (2) you create YourOwnDictionary.xaml, merged all of your separate dictionaries into YourOwnDictionary.xaml, and reference YourOwnDictionary.xaml from usercontrols and pages. This appears to be a feature/bug from earlier Silverlight versions not supporting merged dictionaries.