...and once it is finally found, documentation does not make sense. How for example is this software installed on a local Vista IIS7 development machine?

Hi Clinton,

You will probably need to run the Sitefinity installation executable as "Administrator".  Just right-click on the downloaded EXE and click "Run as administrator".

Once installed, there are a couple other changes you will need to make to IIS on Vista.  You can find information in the Sitefinity documentation:

http://www.sitefinity.com/documents/InstallationGuide_3_5.pdf

See chapter 6 in this manual.  If you still have problems, feel free to post in the Sitefinity forums:

http://www.sitefinity.com/support/forums/forums.aspx

Gabe Sumner

Hello Gabe and thanks for responding.

I've scoured the documentation and one point that stands out is this:

The Sitefinity installer tries to create its virtual folders in the default IIS site, "Default Web Site". If that site is stopped or does not exist, the installation will fail in creating the virtual directories.

Since the biggest mistake that has been made is burying the doc in the executable I have to conclude the failed install is due to the fact that I already use the Default Website for my primary application development and don't want anything messing with my preferred configuration. I'm just glad to see the install did not leave any litter behind.

Currently, installing and configuring Sitefinity on the dev machine is convoluted and the use of the Default Website is unneccessary.
 
I mean the best thing about Vista is IIS 7 and support for multiple websites using the hosts file. 

The  docs also imply a person would have to ask the hosting provider to configure their application server to support SiteFinity but that's another matter for another discussion as I'm sure you'd agree the success of SiteFinity is going to begin and end on the developer's machine.

I'm supportive of Telerik and while I don't remember his name I talked briefly with the founder way back in the day several years ago --but-- I can't cope with this poorly thought out install and configuration.

Personally speaking, the doc should be broken out of the executable and the entire installation and configuration procedure should walk the developer through the use of the hosts file.