When specifying SQL instance name at install time, web.config file doesn't reflect the instance name

[nfields03]

I was installing this today on one of our servers after successfully working with it in the lab, and noticed I was getting a SQL connection error after installation even though the database was created and I could get into SSMS with the same login. After a bit of tinkering I noticed that if you specify a SQL instance name in the install screen, it doesn't necessarily update the web.config file during the install process (mine showed "localhost" as the datasource in the connection strings section of the Web.Config file, but once I edited it to be "localhost\falconorch" to match the instance name, I did an IISRESET and the site came up. It goes to the other suggestion for some validation during the installation script, but hopefully this helps anyone else who runs into the same issue.

[mr-burnse]

Thanks for pointing this out. Definitely a bug that will be addressed.