I’ve been asked to document on my Sueetie Development Visual Studio and IIS configuration to demonstrate how to support debugging across multiple applications. Below is this morning’s addition to the Sueetie Wiki, Working with Sueetie in Visual Studio. It also covers IIS7 configuration. I work with Sueetie on a standalone Windows 2008 Server, so your environment may require a different configuration.
The Environment Overview
Sueetie Development that supports this site, Project Gummy Bear and the source code library on CodePlex is done on Windows 2008 Server and IIS7. The Server is member of a a home office Windows Workgroup and not a domain.
IIS Configuration of Sueetie Development Site
Sueetie contains all root-oriented paths (/style, /wiki, etc.), so it’s essential that we are using a discrete url which supports both a root point of origin and a non-localhost, Visual Studio web site. The url of the development site is
The IIS site bindings to support http://sueetie is shown below.
Website root project setup in Visual Studio
With IIS configured to support http://sueetie we can setup the root project startup accordingly.
…and press F5 and walk through the code.
Working with other Sueetie Application projects in Visual Studio
Sueetie contains multiple Visual Studio, one project per application. Each project (YetAnotherForum.NET, BlogEngine.NET, etc) will contain the root /Web website project with other Sueetie Framework class library projects like Sueetie.Core. The trick to enabling F5 debugging and urls like http://sueetie/blog for full site utility while debugging is to set the root Website project as the startup project.
We’ll want to make sure the root website startup property in Sueetie projects is the same as shown above, with the base URL being http://sueetie.
Now when we press F5 we can walk through the complete source as shown here with BlogEngine.NET.