Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsFCKeditorFCKeditor'controls_labelcontrol_ascx' is ambiguous in the namespace 'ASP'
Previous
 
Next
New Post
4/4/2006 8:57 AM
 

Hello I tried out the video tutorial. As i finished it and tried to recompile dnn i got this error:

ror 11 'controls_labelcontrol_ascx' is ambiguous in the namespace 'ASP'. c:\inetpub\wwwroot\DotNetNuke4\admin\Files\filemanager.ascx 547 12 http://localhost/DotNetNuke4/

When trying to edit a text i get an error in the brower:

Unhandled error loading module.
DotNetNuke.Services.Exceptions.ModuleLoadException: c:\inetpub\wwwroot\DotNetNuke4\DesktopModules\HTML\EditHtml.ascx(10): error BC30560: 'controls_labelcontrol_ascx' is ambiguous in the namespace 'ASP'. ---> System.Web.HttpCompileException: c:\inetpub\wwwroot\DotNetNuke4\DesktopModules\HTML\EditHtml.ascx(10): error BC30560: 'controls_labelcontrol_ascx' is ambiguous in the namespace 'ASP'. at System.Web.Compilation.BuildManager.CompileWebFile(VirtualPath virtualPath) at System.Web.Compilation.BuildManager.GetVPathBuildResultInternal(VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.Compilation.BuildManager.GetVPathBuildResultWithNoAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.UI.TemplateControl.LoadControl(VirtualPath virtualPath) at System.Web.UI.TemplateControl.LoadControl(String virtualPath) at DotNetNuke.UI.Skins.Skin.InjectModule(Control objPane, ModuleInfo objModule, PortalSettings PortalSettings) --- End of inner exception stack trace ---

Any ideas what went wrong?

I am using DNN 4 and VWD

Best

Rick

 
New Post
4/4/2006 6:54 PM
 

Installation of this provider does not require compilation. What video are you talking about?


Locopon
Free modules: E-commerce, Complete localization (Portal, page, module settings, skins, etc.), Secure Login, and more
http://dnn.tiendaboliviana.com
 
New Post
9/27/2006 2:08 AM
 

Hey, even though this reply is some 5+ months after the post, I thought I would make a reply, since I've got what appears to be the cause (& solution) - especially since my Google search of "controls_labelcontrol_ascx" is not defined only got this single forum posting!


Whenever you have a generalized @Regsiter directive (to get a "suite" of DNN controls) at the start of an .ascx page alongside a specific @Register directive targeting a single control, there might be a "collision" if the specific @Register's control is also named in the generalized @Register's suite.

For example, I had the following on my page:

<%@ Register TagPrefix="dnn" Assembly="DotNetNuke" Namespace="DotNetNuke.UI.WebControls" %>

<%@ Register TagPrefix="dnn" TagName="Label" Src="~/controls/labelcontrol.ascx" %>

I was trying to use the dnn:Label control, but it is definable through either @Register, so the compiler couldn't know which one I wanted.

My solution was to delete the generalized directive (the first one) in favor of the more specific directives that target a source. An alternative might be to have the first @Register use a different tag prefix (if it turns out you can't just drop the "suite" of webcontrols in DNN for your particular page).


I hope that helps anyone else who Googles their DNN errors.

 
New Post
6/23/2008 9:32 AM
 

I experienced the same error out of nowhere this morning with the Announcements Module.  I tried your suggestion to some extent, but I couldn't get it to work for me.  I changed all of the TagPrefix and TagName directive attributes in the page skin and in the Announcments module to be unique, but the problem persisted.  So, after that, I decided to simply open up the controls/labelcontrol.ascx and change its class name since DNN said it was ambiguous.  To reiterate, here's what I did to fix my instance of the problem (although I'm concerned it's not the best way):

I opened controls/labelcontrol.ascx.

I added ClassName="DNNLabelControl" to the @Control directive.

Here's the resulting directive:

<%@Control Language="VB" AutoEventWireup="false" Inherits="DotNetNuke.UI.UserControls.LabelControl" targetSchema="http://schemas.microsoft.com/intellisense/ie5" ClassName="DNNLabelControl"%>

I don't know what the proper fix is, but I'm guessing that the ASP.Net assembly cache is mistakenly ending up with two copies of the control in the cache.  That's probably not exactly it, but it may be something like that.  ????

 
New Post
6/23/2008 10:02 AM
 

Actually, I found yet another fix for my instance of the problem - and I think the following is the right way to fix my instance at least:

Delete all of the stuff out of the "Temporary ASP.NET Files" directory in the Windows / Microsoft.Net / Framework / [version] directory.

I didn't do this originally because I didn't see two files that had "labelcontrol" in the name.  I had figured that if their were two copies of the class, there would be two different compiled files for it, but I guess not.

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsFCKeditorFCKeditor'controls_labelcontrol_ascx' is ambiguous in the namespace 'ASP'


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out