The mojoPortalWebPartsAtlas project has a dependency on Atlas and I cannot legally distribute the Atlas dll.
See the README.VisualStudio2005.txt at the root of the solution.
and read http://www.mojoportal.com/usingmypage.aspx
I probably should remove this project from the Solution (not from the file system) and make users who wish to use Atlas add the project to the Solution. I will do that soon. In any case if you are running on Windows my guess is you will want to use the Atlas enabled mojoWebPartManager from the mojoPortalWebPartsAtlas project instead of the non-Atlas enabled mojoWebPartManager in the mojoPortalWebParts project that is currently referenced from the mojoPortal.Web project.
The advantage of the Atlas enabled version is that the WebPart drag and drop works in Firefox and maybe Safari using that one while the non-Atlas one only has drag and drop in IE.
My basic strategy in having 2 versions of mojoWebPartManager is to make it possible to use this Atlas feature without having a dependency on Atlas. This is to keep mojoPortal a pure open source project and to avoid additional hurdles in getting the 2.x branch of mojoPortal working on Mono. So Windows users who want to use this feature can enable it but by default it is not enabled and I will probably exclude it from the Solution in svn to avoid this build error. Users who wish to use it can add it to the solution, install the Atlas dll, uncomment a few things in the web.config and have the Atlas enabled version up and running fairly easily.
The document and link above should help you get things setup, I imagine you will want to use it. Let me know if you have any questions after reading that.
The other compiler warnings are mostly coming from subordinate projects rather than mojoPortal, there may be a few mojo warnings but none of these are anything of serious concern and can be ignored for the most part.