Root Web Area and Sueetie Project Setup

Please note: This Web Root area setup will change considerably with the next source code update, due mid-to-late May. The root web project is now a Website Project and both members and admin website projects have been integrated into the root Website. Those details will be forthcoming when the next CodePlex source update occurs. Thanks!

Setup Step #1: The Web Root Directory¶

The Web Root directory is a light-weight top tier that serves primarily as a landing page, at least at this early phase of Sueetie evolution. The light-weight landing page approach reduces complications in supporting hierarchical ASPNET applications.

The Web Root directory source code demonstrated at Project Gummy Bear is available both in ZIP format and as version controlled source at the Sueetie CodePlex project area.

Unzip the CodePlex source from the Source Code page.

The Root Web Project is a Web Application Project with the namespace and project name of Sueetie.Web. This is your site's IIS root directory. Below is the Sueetie.Web solution. Notice how /members and /admin are excluded in Sueetie.Web and loaded as separate Website projects. Also notice the inclusion of Sueetie.Wiki.

With the addition of Sueetie.Core, we are sharing a connectionstring across multiple ASPNET application with SueetieConfiguration and a Sueetie.Config file in the Web Root. Be sure to update the Sueetie.Config ConnectionString element for the SueetieSqlDataProvider for your environment. To share a common .config file across multiple ASPNET apps we're using an app.config in each application that uses the Sueetie.Core Data Provider. Please notice the app.config file in Sueetie.Web root and in /members. Update the "rootpath" setting to your site's physical root directory area. As a side note, please remember to add a reference to Sueetie.Core in your applications, or better yet include the Sueetie.Core project in your solution and reference it then.

Web.config modifications¶

Update the SueetieServer connection string. The connection string is used in several different places, you may wish to do a solution-wide search for '(local)'.

An essential component of unifying the various Sueetie applications is a common Machine Key located in the web.config. You may wish to replace the MachineKey element in the ZIP'd web.config with your own. A good generator is available at ASPNET Resources. Whatever generator you use, be certain to include the "decryption="AES"" attribute, as Sueetie ASPNET Membership passwords are encrypted. Remember that the machinekeys in all site web.configs must be identical.

Remember too to update the membersConnectionString and adminConnectionString connection strings in the /members and /admin websites.

Create the Database¶

1. There are currently three SQL Scripts Gummybear_Membership.sql, Gummybear_BlogSetup.sql and Gummybear_UserCore. You can execute them here, but in the order listed. Membership, then BlogSetup, then UserCore.
2. Give database owner permissions to ASPNET/Network Service or to the "Connect As" user in IIS7.
   

A Word on Sueetie Roles¶

Sueetie Roles, of course, play a big role in how a user interacts with the various site applications. In setting up an application for use in Sueetie, the app's default roles are modified to correspond with their roles used across Sueetie. The following roles are used in Sueetie.

Registered - All users assigned to Registered role when they create an account
WikiAdministrator - Has access to all Wiki Administrative functions
MediaAdministrator - Full access to media gallery functions
SueetieAdministrator - This is the highest role, with full access to all functions across the site and only role with access to membership functions
ForumAdministrator - Full access to forums administrative functions
BlogAdministrator - Full access to all blogs. Additional roles can be added to grant blog Edit capabilities.

Sueetie Default Users¶

Two users are created by the gummybear_membership.sql script by default. "admin" and "testguy." Both use "password" as password. Admin is member of all roles which Testguy is member of Registered Group only. The passwords can be changed in the WSAT admin area.

On Successful Site Startup¶

At this point we have a basic site with ASPNET Membership administrative support. When loaded the home page should look exactly like Project Gummy Bear with a "Hello, Guest!" and login links. Upon logging in as "admin" (password-"password"), you will see a "Control Panel" link where you can view the administrative area.

Members and Administrative Areas¶

As noted above, the Members and Administration areas are each Website Project folders and must be configured as such in IIS. A helpful screenshot of the Sueetie Site IIS layout is located here.

Next Up¶

Go to Configuring ScrewTurn Wiki for Sueetie.