CODEWITHSUNDEEP
asp.netvisual-studio-2012user-controlsdotnetnuke
Luis LL
Luis LL

Reputation: 2993

@ Registration doesn't resolve controls for "DotNetNuke.Web.UI.WebControls"

Probably this something very simple, but I can't find what I'm doing wrong.
I want to use DNNTreeView in DNN 7.0.6 dev site. This instruction page almost get me there. The code behind resolves the controls, but the .ascx doesn't and gives me the following warning

Warning 102 Element ‘DnnTreeView’ is not a known element. This can occur if there is a compilation error in the Web site, or the web.config file is missing

the page looks like:

<%@ Control Language="C#" AutoEventWireup="true" CodeBehind="View.ascx.cs" Inherits="MySpace.Modules.MyModule.View" %>
<%@ Register TagPrefix="dnn" Namespace="DotNetNuke.Web.UI.WebControls" Assembly="DotNetNuke.Web" %>


<dnn:DnnTreeView runat="server" ID="tvMain">
</dnn:DnnTreeView>

I'm using @ChrisHammond 's templates for the solution.
I have following dll references:

Can you smart guys find what I'm missing?

Upvotes: 1

Views: 1805

Answers (2)

Cliff Richardson
Cliff Richardson

Reputation: 21

I've found a possible solution for the "not a known element" warning. I was pulling my heart out looking for it, but I have one that works for me. All you need to do is add a bin folder to your module and put these dll's in the bin folder: DotNetNuke.dll, DotNetNuke.Web.dll, DotNetNuke.WebControls.dll, Telerik.Web.UI.dll. It doesn't matter if they are in the site bin folder, they need to be in the project bin folder, too.

I have a full explanation here

Upvotes: 2

Chris Hammond
Chris Hammond

Reputation: 8943

If it is just a warning, I wouldn't worry about it, that is fairly common with DNN module development using the WAP approach. If it works in DNN, then just let it go :D

You might check to make sure that you don't have a virtual directory/application on the DESKTOPMODULES folder in IIS, or on the module's folder itself.

Upvotes: 1

Related Questions