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 ForumsClientAPIClientAPIClientAPIClientAPI
Previous
 
Next
New Post
1/31/2006 3:44 AM
 

I have renamed the file ClientAPI to DNNClientAPI in the components/shared directory, and I still get errors compiling in VS 2003.

'ClientAPI' is ambiguous in the in the namespace 'DotNetNuke.UI.Utilities'

I get the same errors with 'DataCache', 'ClientAPIPostBackControl', 'ClientAPIPostBackEventArgs', 'Globals'

Tell me what to do to get rid of theses messages.

 
New Post
1/31/2006 8:59 AM
 

Renaming a file will have no affect on a compile error.  I am not sure what you are trying to do, just compile the same source that is included in the distribution or make custom changes to the core and re-compile.

This type of error generally comes when you decide to import a new namespace.  Another thing to check is wheter your reference paths are pointing to the correct dlls.


 
New Post
2/10/2006 10:46 AM
 

hello

I have downloaded the dotnetnuke 3.2.2 source.and when i compile the source i get more than 100 error saying the client api is not a member of utilities.i thought maybe i am missing something.what should i do?

please help me

somayeh karami

 
New Post
2/10/2006 10:56 AM
 

Make sure your reference path for the project that is having problems is pointing to the right location.  Probably the easiest way to fix this is by expanding the project references and remove the reference to the WebUtility project, then re-add it.  The correct location of the dll is

controls\DotNetNuke.WebUtility\bin\DotNetNuke.WebUtility.dll

You should also validate that teh WebControls is using the right path

controls\DotNetNuke.WebControls\Bin\DotNetNuke.WebControls.dll

 


 
New Post
2/11/2006 6:08 AM
 

hello

thank you .the refrence was worng.i changed the  path and now there is no compilation error.but what should i do to run the project?i made the virtual directory(dotnetnuke)but it still say the project is not configured to be debug.what should the virtual directory be named?(i named it "DotNetNuke" and i gave it write and excute permisions).

and can you give any refrence about the skining technology?i want to run this project to get the idea of it's skining solution.

thanks again

somayek karami

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsClientAPIClientAPIClientAPIClientAPI


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