OK - Hopefully someone can tell me what I'm doing wrong here because I can't imagine I'm the only one that has ever experienced this...

I'm running Windows XP Pro w/SQL Server 2000.  I downloaded DNN v4.0.3 and did the following:

1) I unzipped the project to c:\Inetpub\wwwroot\DNN_ORG.  It created /Website, /Library and the solution file DotNetNuke.sln.

2) I ran Visual Studio 2005 Pro and opened the solution file above.  First, it created a new Virtual Directory in IIS called DotNetNuke_2.  VS then said that the site "DotNetNuke_2" was configured for use with ASP.NET 1.1 but offered to convert it for use with ASP.NET 2.0 which I accepted.

3) VS then churned for a bit and when it was finished, VS showed me 43 Errors and 7 Warnings.

4) I can repeat the behavior by removing the Virtual Directory and the DNN_ORG directory and repeating the step above.

Most all of the errors are about "ClientAPI" as seen below:
Error 4-8 'ClientAPI' is not a member of 'Utilities'. C:\Inetpub\wwwroot\DNN_ORG\Library\Components\Shared\CDefault.vb 80 16 DotNetNuke.Library

Can anyone help me with what I am doing wrong?  I have been working with VS 2003 for a couple of years, but this is my first install of VS2005...

Thank in advance for any help!

Hi,

i ran into the same problems, not sure how i rectified it, but this is my setup:

- i removed the "web" project from the .sln file when VS loaded, so that all i have is the library components in the project.

- make sure that the dotnetnuke.library is the startup/ default project

- build the project, i noticed that i had to build it a couple of times to get ride of the errors, i think some of the library builds are not in order.

i then "open" a "website" for the website portion, - build it, - then publish it to a staging area _precompiledWeb. i then copy/ftp/etc... to my live web site.

if i find remember how I exactly rectified the issue ( i think it was something quiet simple/stupid), I'll post it  for you

HTH

Johnny