Hi,
The "deployment" files are already compiled so there is no need to build it in VS, all the C# source code is already compiled into dlls in the /bin folder. These files are meant for production deployment not for use in VS, though its ok to use them there. The problem is that there may be a few extra files in the package that are not really used but VS is trying to compile them. You can safely delete any file it complains about, like /Services/PopToJSON.ashx.
When working with the "source code" package there are project files like mojoPortal.Web.csproj so the project files know that the Web/Services/PopToJSON.ashx is no included in the project even though it does exist on disk. Its an old file for something I want to do in the future and I did some protyping and then excluded it because its not finished yet. It doesn't get used and doesn't need to be compiled. It does not hurt anything either but I will try to clean that out from deployment packages in the future.
To use the source code package, you should read the READMEVisualStudio.txt file included.
The issue about it starting 6 web servers is because there are multiple web applications in the solution as features are split into separate projects. All the files for features get copied up to the main mojoPortal.WEb project ie Web folder by post build events, so the feature projects are not meant to be run directly, the mojoPortal.Web project must always be the startup project, though you can set breakpoints and debug any of the code in any of the projects, but the main web project always has to be the startup project. You can disable those extra web apps from launching a web server as described here http://stackoverflow.com/questions/16363/how-do-you-configure-vs2008-to-only-open-one-webserver-in-a-solution-with-multi#16390
Just click the project node in Solution EXplorer and then click the Properties tab on the right and you will see where to disable it. I have disabled them on my copy but it does not seem to persist those settings in the solution, they are apparently user specific.
No matter which package you use, you create a database in SQLExpress. I recommend configure SQLExpress for Mixed Mode Authentication, ie Windows Users and SQL Users. Create a SQL User and add it to the dbo group for the db. Then set credentials in the connection string in Web.config or user.config as described here:
http://www.mojoportal.com/mssqlsetup.aspx
There is no need to put the db files in the App_Data folder, some projects do that and ship a db with the app but we do not because we support a lot of different dbs not just ms sql.
Hope it helps,
Joe