Dave Burke : Freelance .NET Web Developer specializing in Online Communities

Doing the Community Server SDK with DaveB

I received an email last night asking how to setup the Community Server 2.1 SDK and realized I never stepped this off.  Dave Stokes wrote the grand-daddy of all Community Server SDK setup documents, of course, which you'll find in his Downloads library.  If you want the Unabridged New Oxford English Dictionary version of the SDK setup process, go see DaveS, otherwise, I think there's a place in the Community Server world for my Funk & Wagnall's version as well.

What I wanted to cover was how to setup a web project on its own http://site, not converting the /sdk/source/web directory to a virtual IIS application directory as is most often described. 

So we've downloaded the Community Server 2.1 SDK from the cs.org Downloads Current Releases area.

  1. Setup the IIS site for ASP.NET 2.0.  May want to add a temporary default.htm just to ensure everything is working.  Be sure to get your ASP.NET 2.0 and Application Pool settings correct.
  2. Copy the /source/web contents to your new IIS site root folder.  Our site is called "CSLOVE" and its root folder is d:/inetpub/cslove.
  3. Open up /source/Community Server ASPNET20.sln in VS2005.  Remove the Web project. 
  4. Add the Web project in d:/inetpub/cslove to the Solution.  Screenshot 1.  Screenshot 2.
  5. Make the CommunityServerWeb20 project you just added the startup project and its default.aspx the start page.
  6. Open the web project's References folder where you'll see several broken links.  Add the broken linked library files from /source/lib/Framework2 and from /source/lib.  No more broken links.
  7. Create a SQL database.  (We're calling ours "cslove.")  Add a user that you'll be using in the web.config Connection Strings.  We'll use "cs_dude."  Make sure he's an owner of the database.
  8. Open MSQuery (or SQL2005 manager.)  We're going to execute CS_2.1_CreateFullDatabase.sql and cs_ASPNET2_Membership_Schema_Update.sql.
  9. The final thing we'll do in MSQuery is execute the SQL "Create Community" stored procedure.  More information is in /SQLScripts/HOW_TO_SETUP_DATABASE.txt.  Mine looked like this.  exec dbo.cs_system_CreateCommunity 'cslove', 'dev', 'daveburke@dbvt.com', 'admin', 'admin', 0, 1
  10. Copy the /source/ASP.NET2_config files to your website root directory.
  11. Update the two Connection Strings in your website's web.config.  (c:\inetpub\cslove\web.config.)
  12. Rebuild your web project in VS2005.
  13. Load your beautiful new Community Server site.

Comments (7) | Post RSS RSS comment feed

Posted on 12/5/2006 8:57:51 AM by Dave Burke
Categories: Community Server
Tags: No tags for this post

Related posts

Comments

12/5/2006 10:08:09 AM Permalink

I dont know how you got a 100 pages down to that, but it is all there.  As always great to read your posts.

Dave

Dave Stokes |

12/5/2006 10:20:11 AM Permalink

Wow, no one could give me a greater compliment, Dave!  You're still the SDK Document Master.  Thanks for your comment and for confirming I didn't miss anything.

daveburke |

12/5/2006 10:38:00 AM Permalink

Thanks for posting the answer to my question Dave.

Jonathan |

12/5/2006 11:01:59 AM Permalink

Hope it helps, Jonathan.  Thanks for asking and making me realize I didn't have a compendium to Dave Stokes' work.  Now we do!

daveburke |

12/6/2006 7:45:47 AM Permalink

Testing a comment with the CS 2.1 SP2...

daveburke |

3/28/2007 11:20:56 AM Permalink

Dave,

Followed your instructions to a tee.  However, a couple of questions.

I'm installing the web portion of cs on my development web server(win 2003).  the rest of the sdk is local to my pc.

I looks from the docs that your expecting to use the local iis installation in XP to do the debugging.

How can i debug the project using my windows 2003 box's IIS?

daveburke |

3/28/2007 11:28:02 AM Permalink

Mike, right?  Actually, the SDK is on a win2003 box, but XP for the SDK and debugging is fine, too.  Bugs would be rooted out on the box with the SDK, primarily by stepping through the code, etc.  Setting CustomErrors to OFF on the Web Developer Server to display the runtime will provide enough information to go back to the SDK box and work it out.  Like any other development - production scenario, i suppose.  Hope that helps!  Thanks for visiting.

daveburke |

Comments are closed

This site was built with the Sueetie .NET Online Community Framework. Learn more about Sueetie at Sueetie.com.