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

HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...DNN v 3.2.2 - Clean Source installation do NOT compile at DNNTree referencesDNN v 3.2.2 - Clean Source installation do NOT compile at DNNTree references
Previous
 
Next
New Post
1/3/2006 1:09 PM
 

Did a clean version 3.2.2 install and after the "normal re-referencing" of the missing DotNetNuke.WebUtility and CountryListBox all through the project, we still get 10 compile errors like:

C:\websites\DotNetNuke\admin\Files\FileManager.ascx.vb(103): Reference required to assembly 'DotNetNuke.WebUtility' containing the implemented interface 'DotNetNuke.UI.Utilities.IClientAPICallbackEventHandler'. Add one to your project.

 

As an example, we receive these error at statements like:

Protected WithEvents DNNTree As DotNetNuke.UI.WebControls.DnnTree

 

We have noticed that this may be a common error for clean installs, we would appreciate if anyone please could shed som light ?

 

Best Regards, Swan B.

 
New Post
1/3/2006 7:19 PM
 
This is also somthing that I am running into on my system as well.

Raud.
 
New Post
1/4/2006 3:45 AM
 
Depending on which solution you use this is usual problem.
What I usually do when starting a new development:
- change virtual path in dotnetnuke.vbproj.webinfo (if needed)
- change virtual path in all solutions under solutions folder (if needed)
- open solution DotNetNuke.All and do a full recompile. This should work without any problem.

Once this is done you can then use other solutions (for example DotNetNuke.Core) and all references will be found. This is because some solutions use file references and expect some dlls to be present in some folders. But these dlls are not created until you do a full compilation.

Vicenç Masanas
Banyoles, Girona - Spain

Disgrafic.com    PSD to DNN
 
New Post
1/4/2006 4:17 AM
 
Dear all,
 
did a new DNN 3.2.2 clean install last night and same thing happened.
 
This time I changed approach slightly. 
 
I first did an initial build of the CountryListBox project.
 
I then, set the Copy Local equal true for each of a missing reference and built the respective project, one at a time(DotNetNuke.WebUtility and CountryListBox references).
 
After all missing references was fixed, I did a new rebuild of the DotNetNuke project.....
and voila it compile successfully. (I have no idea why this approach is working..., and not the regular rereferencing)
 
Please also see related discussion:
 
New Post
1/4/2006 10:28 AM
 
Thanks SwanB,

I created a new clean install as well, and by building the two projects CountryListBox and the DotNetNukeWebUtility first (right click on project name in the soluition explorer, and the click build). allowed me to close and reopen the DotNetNuke.sln without an errors and build it succesfully.

Raud




 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...DNN v 3.2.2 - Clean Source installation do NOT compile at DNNTree referencesDNN v 3.2.2 - Clean Source installation do NOT compile at DNNTree references


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