"Gregory A. Beamer" wrote:
Quote:
> =?Utf-8?B?ZGF2ZQ==?= <epridave@xxxxxx> wrote in
> news:3CD34E7D-106D-4035-8756-46659608E6F8@xxxxxx:
>
> Quote:
> > Obviously I am missing something here, but I'm not sure what to even
> > start searching on.
> >
>
> I am not sure about the runtime issue, but XAML does not currently support
> "visual inheritance", so I am not sure you can solve the design time
> problem easily.
>
> As far as runtime goes, you need to look at the final XAML and you will
> likely be able to get a clue what is going wrong. Not sure how to do in
> WPF; it is a bit easier in XBAP and Silverlight.
>
>
> --
> Gregory A. Beamer
> MVP; MCP: +I, SE, SD, DBA
>
> Twitter: @gbworld
> Blog: http://gregorybeamer.spaces.live.com
>
> *******************************************
> | Think outside the box! |
> *******************************************
> i definately do my best thinking outside the box... unless you consider the
shower a box.
well, it looks like i was on the right track with my first guess. I was
missing a call to InitializeComponent() in each of the sub classes though
which let them build but they wouldn't do anything when it ran. I also had
to take it one step further and create my own common base class for the sub
classes which made the namespaces for the xaml a bit uglier, but it works now
anyway.