Ask a questionAsk a question
 

AnswerUserControl Inheritance

  • Wednesday, March 26, 2008 11:36 AMVijay.Greypad Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Hi,

    I have two UserControls
    1.UserControl1
    2.UserControl2

    how to inherit Usercontrol1 in UserControl2.

    Please give me some idea about this.

    Regards,
    Vijay

Answers

  • Friday, March 28, 2008 2:30 AMMarco Zhou Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    In current version of WPF, you cannot subclass from XAML generated classes, you need to do it in code instead something like the following should work:

    Code Snippet

    public class Parent : UserControl
    {
    }

    <src:Parent x:Class="Test.Child"
                     xmlns:src="clr-namespace:Test"
                     xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
                     xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"/>


    Hope this helps

All Replies

  • Wednesday, March 26, 2008 4:16 PMDenis Vuyka Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    public class UserControl2 : UserControl1

    {

    }

     

    I think this question is more related to the basics of object oriented programming and you should really refer to the appropriate forums or you simply didn't cover your issue within the question.

     

  • Thursday, March 27, 2008 4:18 AMVijay.Greypad Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Hi Desnis Vuyka,

    You are correct.In CS file you will do like this.

    public class UserControl2 : UserControl1

    {

    }

    But what about in Xaml.I did like this

    In UserControl1.Xaml
    <UserControl x:Class="MDIWindows.Parent"
        xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
        xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
        Height="300" Width="300">

    </UserControl>

    In UserControl2.Xaml
    <srcUserControl1 x:Class="MDIWindows.Child"
        xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
        xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml" xmlnsTongue Tiedrc="clr-namespace:MDIWindows"
        Height="300" Width="300">
     
    </src:UserControl1>

    Here i am getting error.
    Please me about this.


    Regards.


  • Friday, March 28, 2008 2:30 AMMarco Zhou Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    In current version of WPF, you cannot subclass from XAML generated classes, you need to do it in code instead something like the following should work:

    Code Snippet

    public class Parent : UserControl
    {
    }

    <src:Parent x:Class="Test.Child"
                     xmlns:src="clr-namespace:Test"
                     xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
                     xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"/>


    Hope this helps
  • Monday, May 12, 2008 8:56 AMbootis Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Dear all,

    I have a question about all this: how to develop my controls for the moment ?

    As inheritance with XAML generated classes does not work, i don't know whether I should
    programmatically declare all my "generic" controls in the base class, or abandon this idea of common controls and duplicate XAML declarations...

    Actually the question could be: should I design my controls as if a future WPF release would support XAML base-classes, and wait for this next release with a temporary solution ?

    What is your opinion about this ?
  • Tuesday, May 13, 2008 7:18 AMbootis Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    No answer... Is my question stupid? (don't hesitate...), and if yes: why?
  • Tuesday, May 13, 2008 11:38 AMRob RelyeaModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    3.5sp1 is the next release (just went to Beta).  It hasn't yet fixed this problem.

    I'm unsure if the release after that will support it.

     

    I recommend you plan to proceed without it for anywhere from 1 - 3 years...I can't promise when we will address...

     

    Thanks, Rob

    Rob Relyea | Program Manager, WPF & Xaml Language Team
    robrelyea.com | /blog | /wpf | /xaml

  • Tuesday, May 13, 2008 11:54 AMbootis Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Thanks much for your answer.
    The most important is that you planned to fix the problem someday...
  • Tuesday, June 17, 2008 3:03 PMBrownie PointsMVP, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Just curious what are you trying to do in this case? Do you want the child control to have the exact same look as its parent but have different functionality? Or do you want to add additional controls to the child that weren't on the parent?

  • Thursday, July 02, 2009 2:13 PMdayanandavt Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Go to ____.
  • Tuesday, July 07, 2009 1:47 PMrgregoryTSC Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    I have done what you did in UserControl2.Xaml with some success.   You need to add a namespace where your UserControl1 is defined.  See below

    <src:UserControl1 x:Class="MDIWindows.Child"
        xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
        xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml" xmlnsTongue Tiedrc="clr-namespace:MDIWindows"
        xmlns:srs="myNamespace"
        Height="300" Width="300">
     
    </src:UserControl1>

    This approach will compile and execute, but will not display correctly in the Visual Studio Designer.  I believe this is a bug.
    Your Solution Build will succeed, even though you will get an error when you try to update the Designer window.

  • Saturday, September 12, 2009 10:28 AMSvetoslav Savov Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals