I am trying to understand some best practices with regards to VS2008 and DotNetNuke development and the best method for setting up a complex multi-project solution in Visual Studio 2008 for just two developers.  I want to load up the DNN core into the solution so that I can learn form how things are being done.

In looking at the core DNN solution/project, I see that a separate VB project has been created named "Library". Could someone explain why this was broken out from the DNN web site project. Was this done because DNN decided to use a WSP project for the core instead of a WAP project (to support limited VS Express)?

If I am using VS2008 Standard and WAP projects are my preferred project type, is there any reason not to convert the DotNetNuke WSP, the Library project and Core Module Projects into WAP projects?   If someone has done this already I would love to hear how they set up their solution structure.

I came across the following inconsistencies in the core modules source projects:
Some of the core module projects appear to be built as VB Projects (Blog) and others are WAP projects (Events) .
Some of the code modules appear to have the SQLProvider file broken out into separate projects (creating lots of small projects) and some, including the templates, have it included as part of the module project.
Some of the module projects reference common dlls in the DNN Website bin and others reference the same dlls within the library project.
What is the recommended methodology (location) for referencing common DLLs. For example: Where should my new module reference the DotnetNuke.dll and Microsoft.ApplicationBlocks.dll?

Any recommendation are appreciated.

Les.