Hi Matthias, thanks for thinking with me.
I use the same replacement string for both installs. So i replace the original webconfog part:
<connectionStrings>
<!-- Connection String for SQL Server 2005/2008 Express -->
<add name="SiteSqlServer" connectionString="Data Source=.\SQLExpress;Integrated Security=True;User Instance=True;AttachDBFilename=|DataDirectory|Database.mdf;" 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=.\SQLExpress;Integrated Security=True;User Instance=True;AttachDBFilename=|DataDirectory|Database.mdf;"/>
<!-- Connection String for SQL Server 2005/2008 - kept for backwards compatability - legacy modules
<add key="SiteSqlServer" value="Server=(local);Database=DotNetNuke;uid=;pwd=;"/>
-->
with:
<connectionStrings>
<add name="SiteSqlServer" connectionString="Server=o8yqlqpti4.database.windows.net;Database=DotNetNuke;uid=itproadm;pwd=**password**!;" providerName="System.Data.SqlClient" />
</connectionStrings>
<appSettings>
<!-- Connection String for SQL Server 2005/2008 - kept for backwards compatability - legacy modules-->
<add key="SiteSqlServer" value="Server=o8yqlqpti4.database.windows.net;Database=DotNetNuke;uid=itpradm;pwd=**password**;"/>
This works since version 1 or so ;) (i have used dotnetnuke since version 1, but stopped at version 4... to return now. since there are more asp.net /ms-sql providers for a more reasonable price it finally is affordable to run a asp.net site with ms-sql)
I will be testing the install in a few days, i need to purchase an additional web+sql package first. But first I have to create some working sites. I'll keep this up to date with my findings regarding the 6.02.02 install version.