Migrating from ASP.NET 1.x to ASP.NET 2.0

Re: "The base class includes the field 'WebUserControl1', but its type (common_WebUserControl) is not compatible with the type of control (ASP.common_webusercontrol_ascx)"

vijay_010237866 — Tue, 20 Oct 2009 06:00:14 GMT

In the reference the path of the control given must be ~/Common/User.ascx.

Re: "The base class includes the field 'WebUserControl1', but its type (common_WebUserControl) is not compatible with the type of control (ASP.common_webusercontrol_ascx)"

praddy — Tue, 20 Oct 2009 05:44:58 GMT

thanks for the suggestion but this solution is not applicable in vs 2008.. the usercontrol comes with the codefile tag and not the codebehind tag by default.. if u mention the codebehind it throws a compilation error.. is there any other solution?

Re: "The base class includes the field 'WebUserControl1', but its type (common_WebUserControl) is not compatible with the type of control (ASP.common_webusercontrol_ascx)"

sean717 — Mon, 19 Oct 2009 23:07:20 GMT

Hi, have you tried the possible solution suggested by Maduka?

Here it is:

try to create a new usercontrol in vs.net 2005. It will create as CodeBehind not as CodeFile. I guess CodeBehind is the suitable property in the vs.net 2005.

CodeFile willl work with converted .net projects(vs.net 2003 to vs.net 2005). But when you try to add new web form to converted project and try to use an user control of vs.net 2003 version, this error occurs.

Rgds

Maduka

Re: "The base class includes the field 'WebUserControl1', but its type (common_WebUserControl) is not compatible with the type of control (ASP.common_webusercontrol_ascx)"

praddy — Mon, 19 Oct 2009 14:15:58 GMT

hey i have encountered a similar problem but in .net 3.5. i have tried all the solutions mentioned here for .net 2.0 i.e. vs2005.. my app was developed in vs2003 v1.1 and then converted to vs2008 v3.5. earlier this problem was not there and the website was running w/o any glitch but this problem occurred suddenly a few weeks back.. i've been trying to solve it but in vain. can anyone please suggest what i should do?

Re: "The base class includes the field 'WebUserControl1', but its type (common_WebUserControl) is not compatible with the type of control (ASP.common_webusercontrol_ascx)"

sean717 — Wed, 14 Oct 2009 21:13:42 GMT

Maduka:
Maduka

I had the same problem, after I made change according to what Maduka suggested, eveything works fine now.

Thanks!

Re: "The base class includes the field 'WebUserControl1', but its type (common_WebUserControl) is not compatible with the type of control (ASP.common_webusercontrol_ascx)"

mickeyding — Fri, 09 Oct 2009 04:17:00 GMT

We had a similar issue. Our user controls lived in a directory called "Controls"

In an effort to group related controls some of the user controls were put in subdirectories under the controls directory. We noticed the problem surfaced when a user control in a subdirectory was referring to another usercontrol in the parent directory (eg A SearchList control in the \Controls\SearchItems directory used a ModalDialogue control in the \Controls Directory.

A clone of the ModalDialogue Control was created in the \Controls\SearchItems subdirectory. The new control was given a different name (ModalDialogTest) to be sure to isolate which control was being used. This worked fine. We then hit on the idea of parking the modal dialogue control in its own subdirectory. (out from the parent "\Controls" directory)

A Subdirectory was created "\Controls\Modal". Our ModalDialogue control was created in this subdirectory and it cured the problem. I hope this helps someone out.

Re: "The base class includes the field 'WebUserControl1', but its type (common_WebUserControl) is not compatible with the type of control (ASP.common_webusercontrol_ascx)"

Ajitchahal — Fri, 11 Sep 2009 19:10:10 GMT

Hi,

This problem normally occurs if you keep user controls in diffrent directories or name spaces, moving them to same namespace and physical directry solved this problem for me.

Hope this helps.

Thanks,

Ajit

Re: "The base class includes the field 'WebUserControl1', but its type (common_WebUserControl) is not compatible with the type of control (ASP.common_webusercontrol_ascx)"

pilot1 — Thu, 02 Jul 2009 07:38:35 GMT

See http://support.microsoft.com/kb/919284.

It also could happen because Inherits="xxx" attribute has value of unexisting class.

Re: "The base class includes the field 'WebUserControl1', but its type (common_WebUserControl) is not compatible with the type of control (ASP.common_webusercontrol_ascx)"

dvisaria — Fri, 05 Jun 2009 19:57:28 GMT

It does solve my problem. I wasted 4 hr try to solve problem by deleting temporaroy files. But this does the trick.

Re: "The base class includes the field 'WebUserControl1', but its type (common_WebUserControl) is not compatible with the type of control (ASP.common_webusercontrol_ascx)"

ozkary — Thu, 14 May 2009 22:08:34 GMT

Hello,

This run-time error also shows when the mark-up has some invalid format. For example, if the control has this control directive:

<% Control Language="C#"

when it should be

<%@ Control Language="C#" (NOTE THE @)

Something small that can get overlooked.

I hope it helps

Re: "The base class includes the field 'WebUserControl1', but its type (common_WebUserControl) is not compatible with the type of control (ASP.common_webusercontrol_ascx)"

rajquest — Wed, 18 Feb 2009 22:39:29 GMT

This solution worked for me right away.
Removed the ID tag. Is there a reason why the ID tag would cause this error ?

****** Worked for me *****************

Thanks

Re: "The base class includes the field 'WebUserControl1', but its type (common_WebUserControl) is not compatible with the type of control (ASP.common_webusercontrol_ascx)"

pradman2005 — Mon, 07 Jul 2008 05:45:55 GMT

Hi Net,

Even I experienced the same problem...

but I have not made any changes to the structure of the website, the usercontrol in question was working perfectly from a long time. It was just on saturday that I got this problem. I tried the solution that you have given here ie. transferring the usercontrol to the same folder as the page. But it will require changing the register tag in all the pages that include the said control. Moreover, did u find the reason why this problem occurred in the first place?

Awaiting your reply.

Re: "The base class includes the field 'WebUserControl1', but its type (common_WebUserControl) is not compatible with the type of control (ASP.common_webusercontrol_ascx)"

dmcmulle — Tue, 01 Jul 2008 17:22:29 GMT

"Use fixed naming and single page assemblies" did the trick.

Re: "The base class includes the field 'WebUserControl1', but its type (common_WebUserControl) is not compatible with the type of control (ASP.common_webusercontrol_ascx)"

Badajoz — Tue, 20 Nov 2007 03:52:06 GMT

I just had this issue and turning off the "Allow this precompiled state to be updatable" was not an option. If I do then Reporting Services reports on my website do not work.

Rather, the work around that I used was to check "Use fixed naming and single page assemblies". This corrected the issue. One presumes that that this does not have any detrimental impact - it's just a different way of the compiler organising its dlls...?

Hopefully this gets fixed and new bug replaces it in 2008

Re: "The base class includes the field 'WebUserControl1', but its type (common_WebUserControl) is not compatible with the type of control (ASP.common_webusercontrol_ascx)"

mike8431 — Wed, 05 Sep 2007 01:24:12 GMT

as someone previous mentioned, what seems to fix the problem is to turn off update when you publish.

1) go to the menu item Build -> Publish Web Site

2) turn off the option "Allow this precompiled state to be updatable" (This is on by default)

3) Make sure you deleted your old precompiled website

4) hit okay in the dialog.

Hopefully this gets fixed in 2008.