Derive from UserControl

Question

5.00/5 (2 votes)

See more:

Hi again!

I created a usercontrol with a view virtual methods so I could derive from them and use the standard behaviour where needed.
Now XAML tells me
"Error 1 Partial declarations of 'xxx.View.UserControl1' must not specify different base classes ...\View\UserControl1.xaml.cs 20 26"

Isn't it possible to do it this way? I do use interfaces but wanted to have a predifined behaviour which can be overwritten where needed.

Help would be appreciated!
Thank you in advance

Posted 22-Oct-08 11:35am

ezazazel

Add a Solution

2 solutions

Solution 2

Hello,

The solution is quite easy in fact.

When u derive from usercontrol, you have to do it in the code behind and in the XAML you have to change the tag by the one of your derived class. SO the solution is :
1) Declare the XML namespace of your controls (in the old UserControl tag)
2) Change the "UserControl" tag to the YourXMLNameSpace:YourDerivedControl one

That's all

Posted 10-Apr-10 0:10am

jmix90

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

Pete O'Hanlon · Accepted Answer · 2008-10-22T11:43:00

Oh dear - you've hit a fairly common problem here, and it's to do with the way WPF generates a backing class to actually map your controls in (it's called xxxx.g.cs where xxx is your class). You need to do a bit of work to get round this, and here's[^] a link to an entry you might find useful.