Deployment

vbboyd · July 15th, 2013, 02:51 PM

I posted my website onto a remote server this morning and I was told by the hosting provider that you can just copy the whole thing up via ftp and Visual Studio 2012 and that you don't need to set up the SQL Server database that sits under the App_Data folder in your Visual Studio directory that once you post to the remote IIS server that your ASP.NET 4.5 application will automatically just see that .mdf file sitting under the App_data folder (that is referenced in your web.config file) in the file structure of your ASP.NET 4.5 website and that you don't have to do any special configuration. At least that is what their tech support people told me. That Microsoft was really good about that sort of thing.
But I found out that I needed to change the web config to point to the SQL Server database that they was created by me remotely.
Thanks once again:
PS
I took your example out of your book as a blueprint and I used to build and E-Commerce website for a fictional chocolate factory and candy store.

Thanks once again.

RichClutter · July 15th, 2013, 11:06 PM

Good luck to you. I hope you get the job. At least you are trying to improve and better yourself which is a lot more than I can say for the worthless bums on welfare. But I didn't mean to preach. What you are doing is very honorable. Again good luck to you. I just hope the Author guy doesn't get as you say get too "crabby" with you for asking a question. Ha, ha, ha. Only kidding.

-Rich C-

vbboyd · July 16th, 2013, 11:39 PM

Is this the correction connection string that I should add to my remote hosting of the production server to where I have uploaded my application as it is on page 802 of your book?

Code:

<add name="CandyStoreEntities" connectionString="metadata=res://*/App_Code.CandyStore.csdl|res://*/App_Code.CandyStore.ssdl|res://*/App_Code.CandyStore.msl;provider=System.Data.SqlClient;provider connection string=&quot;data source=localhost;Initial Catalog=CandyStore;User ID=****yd;password=****ez;MultipleActiveResultSets=True&quot;" providerName="System.Data.EntityClient"/>

Here is the regular connection string for the remote server that the remote hosting service gave me to use:
<add name="strConn" connectionString="Data Source=localhost;Initial Catalog=DBNAME;Integrated Security=false;User ID=DBUSERNAME;Password=DBPASSWORD" />

The only thing about your entity connection string that I am not understanding is what is this part of the connection string all about?:
provider connection string="
Does that part need to be changed too?

Imar · July 30th, 2013, 02:15 PM

Quote:

The only thing about your entity connection string that I am not understanding is what is this part of the connection string all about?:
provider connection string="

This embedded connection string refers to the SQL Server database you want to use. EF leverages the main connection string facilities. However, it has other needs than regular connection strings. So, part of the connection string is EF specific (all the metadata stuff). It then embeds a SQL Server connection string inside its own connection string. In order for the quotes to be used as literal values, they are encoded to " otherwise that would prematurely close of the connectionString attribute of the outer connection string.

Hope this helps,

Imar

August 6th, 2013, 01:10 AM

the posts here are beneficial one for me as well ..