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 ForumsClientAPIClientAPIProblems with ClientAPI.AddButtonConfirm - Please help!Problems with ClientAPI.AddButtonConfirm - Please help!
Previous
 
Next
New Post
9/28/2006 9:48 PM
 

I have created a new custom module.  In this module I have copied the standard URLControl.ascx that's included in the DotNetNuke project.  I modified the namespace for the URLControl to match my project.  What I'm needing to do is to modify the URLcontrol so that it displays the file selected if it's an image file.

I can't seem to get it to compile correctly without getting the message "'ClientAPI' is not a member of 'Utilities'".

I've download the latest DotNetNuke.WebControls project, unzipped it, added the WebControls project to the DotNetNuke.sln recompiled everything, deleted the VSWebCache folder, restarted IIS, deleted all the DotNetNuke.WebControls.dll in the entire project, recompiled again, stood on my head, repeated the process, etc.....

Why am I getting this message?  In my code when I type DotNetNuke.UI.Utilities. intelesense shows DNNClientAPI but not ClientAPI.  What the heck am I doing wrong??

Also, I understand the value of splitting out controls/modules into all these projects, but it would be helpful if all the source was avaiable in a single download with a single .sln file that would allow an easy way to recompile everything.

 
New Post
9/29/2006 9:56 AM
 

The ClientAPI and the WebUtilities are two different dlls. The core has a dependency on both, for it uses the controls and it also uses the ClientAPI.  The DNNClientAPI is the DNN specific code that utilizes the ClientAPI.

It seems like you simply need to reference the WebUtility.dll which is distributed with the core, found in the controls\dotnetnuke.webutility folder.

 


 
New Post
9/29/2006 2:42 PM
 

Thanks Jon!  Adding a reference to the DotNetNuke.WebUtility solved the problem.

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsClientAPIClientAPIProblems with ClientAPI.AddButtonConfirm - Please help!Problems with ClientAPI.AddButtonConfirm - Please help!


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