So next question would be if there is a step by step process for getting the code to a debuggable state.

Problem I'm running into is that it was "installed" onto a remote server.  I'd like to change the source code on a development machine and just push the new code out as I need to.  At the moment I've got the solution working in 2008/3.5, however when I try to just run it, I get the install page, and with that an error about rights on the main folder. 

Would it just be better to zip up the server code and deploy that on my development machine?  I would think that the server code won't have most of the code files, just assemblies.  Will I have to run the normal install on my development computer?

The end goal here is to be able to change some of the already in place modules like say Login or Blog.

Fair enough, but personally I would like to add to or change existing modules because I am hoping that will take less time that creating whole new ones ie reinventing the wheel.  If possible, and I'm not sure this is worth the time, I'd like to remove the stored procedure dependancy in some of the base modules/classes and replace with ORM generated code.  (Not a fan of stored procedures)  This may prove annoying and I might ditch the idea, but this is an example of what I am planning to do.

I did end up running the install and just changing the connection properties.  Worked just fine.  Ends up that was really the way to go.

Hi -- Regarding the original question, if I open the vs2008.sln solution in vs2008, I also get the compile errors.  I checked and the system is targeting .NET 2.0, but I still can't compile.  Shouldn't I be able to get the source open and compiled in vs2008, targeting .NET 2.0?