... after getting the whole thing running, went thru the installation process ... nice and shine ... however, opened the site several times (as well as a rebuild in between).

So, heading for the next step .... during installing of languages packs I read on the Dutch User Group site of DotNetNuke users a question: "How to speed up the load time of DNN and Custom Private Assemblies." This question draw my attention because I also noticed the terribly long time of loading the home webpage hitting ttp://localhost/<site>/home.aspx
 
The answer was: This is something that is often forgotten about. Select the project, navigate to “Configuration Properties“ and select the “Optimizations“ node. The default value is &H11000000 (285,212,672). If you neglect to change this value, your component will conflict with every other in-process component compiled using the default. Staying well away from this address is recommended. I figured out that this is the case for project: DotNetNuke.Library.VS2008 (for the other project: DotNetNuke.Web.VS2008 the default value was &H00400000).

In relation to this information I read as well suggestion on page: Advanced Compiler Settings Dialog Box - Visual Basic (http://msdn.microsoft.com/en-us/libra...). So, I went into both projects properties pages > Compile tab > [Advanced Compile Options ...] there I checked Enable optimizations ... it's true, you may critisize me on not checking well what 'enabling optimizations' really meant, but for time consuming reasons ... I recompiled the solution ... FAIL because of ...

Now what??

It surprises me that this error pops out at the moment the /">http://localhost/<site>/ is just started to (re)build. Again that nasty error: "Could not get dependencies for project reference 'DotNetNuke.Library.VS2008'Validating Web Site"  .... ???

I had the whole thing flying ???

It surprised me as well that at this time, each time I tried to rebuild, it takes a while because it is rebuilding all folders /<site>/bladiebla
(note: the other week when I tried it for the first time, to me this happenend only the very first time if I remember well, although I did at that time a rebuild several times)

.. it turned out that during rebuilding all those folders three errors popping out which I each building stops as soon it reaches the error
1) on BlogImport.ascx
 line 31 <asp:DropDownList ID="ddlBlogs" runat="server" Text=" " /> the property Text can not be set declarative
 so I had to comment this line out to be able to continue a rebuild
2) it turned out I had to comment out line 73 and 74 on the same page (BlogImport.ascx)
<asp:LinkButton ID="cmdImport" .... OnClick="cmdImport_Click" Style="height: 19px" Text="Import" />&nbsp;
<asp:LinkButton ID="cmdCancel"  CommandButton" BorderStyle="None" CausesValidation="False" Text="Cancel" />&nbsp;
telling me both could not be reached because of they both are private
then at last
3) I had to exclude AddressEdit.ascx because for what ever reason it could not be added anymore

So, it maybe superfluous but before every (re)build I did do a clean of the solution because I noticed that by several occasions some typical other error pops up saying some dll's for instance (Taxonomy.dll) are in use by another process. 

Only after closing reopening VS2008, resetting IIS and ... sure .. restarting my machine, I was able to rebuild, however only with the two comment-out lines just mentioned on BlogImport.ascx and an excluded AddressEdit.ascx

To me, I am rather lost ... I do have the feeling there is some chicken - egg problem >> the website can not be rebuild because it can not reach the project reference 'DotNetNuke.Library.VS2008' to validate it, while it seems that the 'DotNetNuke.Library.VS2008' is depending on a proper build including the website

So ... are you aware of any solution regarding this into the newest DotNetNuke release which is mentioned to be published somewhere this week because of the bug in ASP.NET??

KWHJ