Here are my secrets to clean build of DotNetNuke 5.6.0. I am using Windows 7, Visual Studio 2010 and IIS is configured properly. Note that this applies to Community and Professional editions.

 

1. Unzip the source and copy/move it to C:\Projects\dnn560ce
2. Using IIS check the DotNetNuke_Community web application physical path is set to C:\Projects\dnn560ce\website
3. Open DotNetNuke_Community.sln

 

You will get this error:

 

http://localhost/DotNetNuke_Community : error  : Unable to open the Web site 'http://localhost/DotNetNuke_Community'. To access local IIS Web sites, you must run Visual Studio in the context of an administrator account.

 

Pin Visual Studio to the start menu

 

3. Press the windows key and type visual studio
4. Right click on Visual Studio 2010 and select Pin to Start menu.

 

From now on, to open Visual Studio in admin mode just press the windows key (or click start button) and right click on Visual Studio 2010 to run as Administrator.

 

Open Visual Studio  as Admin

 

5. In Recent Projects, click DotNetNuke_Community
6. Right click on http://localhost/DotNetNuke_Community/ and select Set as Startup Project

 

Build Solution

 

7. Press Ctrl+Shift+B (Build Solution)

 

(if you don't get an error the first time, build it again)

 

Error        1        Unable to copy file "bin\DotNetNuke.Services.Syndication.xml" to "..\..\..\Website\bin\DotNetNuke.Services.Syndication.xml". Could not find file 'bin\DotNetNuke.Services.Syndication.xml'.        C:\Projects\dnn560pe.source\Library\Components\Syndication\DotNetNuke.Syndication.csproj        113        5        DotNetNuke.Syndication

 

Workaround

8. In Solution Explorer, expand Solution Items, Support Projects.
9. Right click on DotNetNuke.Syndication, select Properties
10. Select Build Tab
11. Change the XML documentation file from

 

bin\DotNetNuke.Services.Syndication.xml

to

DotNetNuke.Services.Syndication.xml

 

Build Solution

 

12. Press Ctrl+Shift+B (Build Solution)

 

Error        2        The 'Text' property cannot be set declaratively.        C:\Projects\105.DotNetNukePE\DesktopModules\Blog\BlogImport.ascx        31        

 

Workaround

 

13. Double click on the error
14. Change

<asp:DropDownList ID="ddlBlogs" runat="server" Text=" " />

to

<asp:DropDownList ID="ddlBlogs" runat="server" />

 

Error Free Build

 

15. Press Ctrl+Shift+B (Build Solution)

 

Builds errors are one of the most annoying things about open source. Most would expect to load up the project and compile it. If it doesn't work first time, many will simply abandon the effort and very few will actually get it working.

 

I challenge the DotNetNuke team to check the option Treat all warnings as errors for the next release.

(For both DotNetNuke.Library and DotNetNuke.web, right click on the project, select properties, then the compile tab.)

I hope this is of some help to you.

Sebastian,

This is were I get confused between the Community (public) and Professional (private) communities. I have already sent multiple build reports as trouble tickets to the DotNetNuke Support Network with the following response:

A total of 7 Gemini issues has now been logged in our DNN PRO Gemini database using the information you provided.  It will be of great help to our engineering group to read your analysis and comments.  Thank you again.

Q1) As a professional subscriber where would you suggest that I post these reports?
Q2) Do I have access to DNN Pro Gemini to submit, watch and provide input?
Q3) Should I duplicate my reports in "community" Gemini?

I am finding it very difficult with multiple roles and multiple reporting options across multiple systems.