Connectionstrings in webconfig STANDARD?

The glorious internet has a vast collection of articles on this topic, some of which were even kind enough to mention that they were written centuries ago.

(asp.net 2.0)
Is this 'the way' to store connection strings?
In this example I have two connection strings, one for my test environment and another for production. Toggling comments will toggle which server I hit.

  <connectionStrings>
    <remove name="SqlServer"/>
    
    <!-- offline; my test environment -->
    <add name="SqlServer" 
         connectionString="Data Source=myComputer\\sqlexpress;Initial Catalog=myproduct-test;Integrated Security=SSPI"
         providerName="System.Data.SqlClient" />
    
    <!-- online; my server aka production -->
    <!--      
    <add name="SqlServer"
           connectionString="Server=myserver.com;Database=mydb;Uid=myuser;Pwd=mypw"
           providerName="System.Data.SqlClient" />
         -->
    
      </connectionStrings>

Code (markup):

The code to access this stored connection string is:

string connectionString = ConfigurationManager.ConnectionStrings["SqlServer"].ConnectionString;

Code (markup):

Am I cutting edge or am I a noob??????

Thanks for readin'

 

I'd also like to add that I have copied my connection strings into the above web.config and previously they were strings in some app_code class. My sql connection will no longer open. Does this have to do with SSPI?

 

That is generally how you should set up connection strings. Usually you don't use SSPI but instead have Integrated Security=True if you are using SQL express on your development machine.