I performed a "typical" install to my local instance of SQL2008 and when I looked at the web.config I found the entry for the SQL Express was updated.  All works as expected, but this is "different" and will be confusing to some.

As you can see from below the SQL 2005/2008 Express entry is updated in both locations.  Aslo note that Data Source has been updated for all entries, not just the Express entry.  hmmm?

<connectionStrings>
    <!-- Connection String for SQL Server 2005/2008 Express -->
    <add name="SiteSqlServer" connectionString="Data Source=(local);Initial Catalog=DNNV550beta;User ID=DNNUser;Password=DNNPassword" providerName="System.Data.SqlClient" />
    <!-- Connection String for SQL Server 2005/2008
    <add name="SiteSqlServer" connectionString="Server=(local);Database=DotNetNuke;uid=;pwd=;" providerName="System.Data.SqlClient" />
    -->
  </connectionStrings>
  <appSettings>
    <!-- Connection String for SQL Server 2005/2008 Express - kept for backwards compatability - legacy modules   -->
    <add key="SiteSqlServer" value="Data Source=(local);Initial Catalog=DNNV550beta;User ID=DNNUser;Password=DNNPassword" />
    <!-- Connection String for SQL Server 2005/2008 - kept for backwards compatability - legacy modules
    <add key="SiteSqlServer" value="Server=(local);Database=DotNetNuke;uid=;pwd=;"/>
    -->

I will post this in Gemini .
Paul. 
 
Update - Issue 13055 in Gemini.

Sevastian,

Yes I do agree -- the issue is really a DNN rockie may be caught off guard with this.  Previously, the appropriate entry in Web config was updated.   So, update one consistent entry with examples of other possible connections strings, or return to the previous mode of updating the appropriate entry. 

I unchanged this could lead to several support calls and/or emails.

Also, I wanted to help with beta testing and every little bit helps ... don't you think?

Paul.