I had no problems whatsoever with the install process of the site.  It installed just fine and I was able to start building my site with no problems whatsoever.  The problems started when I loaded up the project the first time in Studio. 

I tried to load DotNetNuke.sln to start with.  Many of the projects caused an error "The project location is not fully trusted by the .Net runtime".  Of course, it didn't tell me which project was causing the problem, but it was several (15, maybe...).  As one might expect, I had a plethora of build errors (166, to be exact), and several warnings, all to the effect of   "Warning: The dependency 'DotNetNuke, Version=3.0.12.21332, Culture=neutral' in project 'DotNetNuke' cannot be copied to the run directory because it would overwrite the reference 'DotNetNuke, Version=3.2.2.30184, Culture=neutral'."  I got  probably 10 or so of these referencing various dlls.

I found a post where a user had similar problems and solved them by compiling different projects in a certain order.  I did that as the posts recommended, but to no avail.

Is there any documentation or an easy way to get all of these assemblies to play nice with each other?  What am I missing?

Thanks in advance

Davey

That is one of the things that is confusing me.  I'm not trying to open it from another machine.  However, I suppose that something could be in the project, solution, or config files that are causing the .net framework to believe the files either exist on another machine or need to reference files on another machine.  Any ideas as to where to check to see if this is the case?

I didn't have any other versions of DNN.  This is the first time I have dealt with it at all.  If I remember right, I downloaded the "source" zip for 3.2.2, extracted it to the virtual directory in my web root, and ran the install proc.  Smooth as glass.  I just wish the damn thing would compile.  I have been very impressed with how DNN works so far.  I was able to upload and inport the Blog module with no problems.

Is there somewhere I can maybe get a list of dependancies, or perhaps a list of what projects need to be loaded and compiled in what order?  I'd rather not have to bring all the individual projects into a solution 1 by 1, but if that's the way, then OK, I suppose.

Thanks for the help!

Davey Bolling