Need deployment cheatsheet AND no Connection string for aspnetdb?

Notso · April 23rd, 2013, 10:37 PM

Hello,
I am trying to figure out how to deploy my site to production.

They talk about connection strings and changing it for production. However, my web config connection strings look like this

Code:

  <connectionStrings>
      <add name="JamestownDatabaseEntities" connectionString="metadata=res://*/App_Code.Model.csdl|res://*/App_Code.Model.ssdl|res://*/App_Code.Model.msl;provider=System.Data.SqlClient;provider connection string=&quot;data source=.\SQLEXPRESS;attachdbfilename=|DataDirectory|\JamestownDatabase.mdf;integrated security=True;user instance=True;multipleactiveresultsets=True;App=EntityFramework&quot;" providerName="System.Data.EntityClient" />
  </connectionStrings>

It has just the one connection string, but my aspnetdb works fine even though there is no connection string for it. What do I do to get my aspnetdb working in prod? Do I need to add a connection string for it in my web.config?

Ok. I found the http://www.asp.net/web-forms/tutoria...ing-options-cs pages. So, I guess I will just look through that stuff for now. So, I deleted the novel I had in here. However, if someone can help me with the above question about aspnetdb connection string, that'd be great.

Imar · April 24th, 2013, 02:44 AM

Hi there,

Good to see you figured out most of this ;-) You may also find this interesting: http://msdn.microsoft.com/en-us/libr.../hh420322.aspx

For the connection string, check out Chapter 19 and Appendix B of my book as they deal with deployment. In particular page 725 (recreating the database) and further and Page 771 - Configuring Application Services) explain how this works. In short: .NET has a default connection string called LocalSqlServer that is used. You can override that connection string to point to your own database or you can reconfigure the various providers to point to your connection string (page 771 and further).

Hope this helps,

Imar