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 ...Compilation errorCompilation error
Previous
 
Next
New Post
10/6/2006 6:12 AM
 
I figured it out, it's all installed and i'm loving it its exactly what i have been looking for. thank you all for your help.

Is there any more skins available for dounload or do i have to create my own?
 
New Post
10/6/2006 9:46 AM
 

congratulations.

there are plenty of skins, some you can pay for(www.snowcovered.com) many are free.

its not hard to make your own(documentation available :D).  Nina, is generous and has offered some free skins.

careful about trying other peoples stuff unless they have some integrity.

You can search the forums or this site has a link to Ninas site.


DotNetNuke Search Engine
ASP.Net Search Engine
Email me to add your favorite sites to the search List.
 
New Post
11/20/2007 8:46 AM
 
The error is caused by the "web-project" not being able to find the DotNetNuke Class Library (DotNetNuke.dll). 

There are two common causes for not being able to find the assembly.

1. In Visual Studio 2003 (for Visual Basic but not C#), the project file contained a number of commonly used Imports statements - ie Imports Statements that were used by all .vb files in the project.  As .NET 2 websites do not have a project file, these default Imports statements have been moved to the web.config file.

eg
       
           
               
               

Thus if release.config has not been copied/renamed to web.config, the compiler will not be able to find the "Config" class, as the project does not have an Imports statement referencing the correct namespace..

2. If working with the Source release - the assemblies need to be built, before the site can be run..  (This is normal behaviour for source releases, (for instance Linux, Apache etc), although it is quite surprising how many people expect the source package to work out of the box).

EDIT** As this behaviour (no binaries in the /bin) is different from 3.x, we will probably release an updated package with the binaries included.
 
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Compilation errorCompilation error


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