APPENDIX B, p.790

StvnSpnz · November 6th, 2015, 03:59 PM

Hi Imar,

I could publish the sample site in a temporary server for testing it. I also had to rename the name of the database.

My question is if changing this name, would I need to modify the <connectionStrings> with the new DB name only or another element else? And, are the parameters (Initial Catalog, ID, etc.) inside of it case sensitive?

Thanks, almost finished. A lot of questions, weren't they?

PS: When is ready I will put the link for you to give me your "last word". Hah.

Imar · November 6th, 2015, 04:50 PM

You may also need to change the data source (the server you're targeting) and maybe also the user name and password if any.

The name of the database is not case sensitive.

Cheers.,

Imar

StvnSpnz · November 6th, 2015, 05:13 PM

The good thing I know is in the <connectionStrings> because I have access to the remote DB through SMSS, here I put the code for you to take a look:

Code:

<connectionStrings>
    <add name="PlanetWroxConnectionString1" connectionString="Data Source=xxx.xxx.xxx;Initial Catalog=dbname;User ID=dbname;password=xxxxxxxx"
    xdt:Transform="SetAttributes" xdt:Locator="Match(name)"/>
    
    <add name="PlanetWroxEntities" connectionString="metadata=res://*/App_Code.PlanetWrox.csdl|res://*/App_Code.PlanetWrox.ssdl|res://*/App_Code.PlanetWrox.msl;provider=System.Data.SqlClient;provider connection string=&quot;data source=xxx.xxx.xxx;Initial Catalog=dbname;Trusted_Connection=True;MultipleActiveResultSets=True;Integrated Security=True;&quot;" xdt:Transform="SetAttributes" xdt:Locator="Match(name)"/>
  </connectionStrings>

I copied it from the web.config transformed.
Do I have to modify the <add name> or the metadata attribute too?

Thanks.

Imar · November 6th, 2015, 05:17 PM

>> Do I have to modify the <add name> or the metadata attribute too?

Not if your EF model is called PlanetWrox. Otherwise you need to update that code to match your EF model.

BTW: you use two different connection types (integrated and SQL authentication) for the same database.

Imar

StvnSpnz · November 6th, 2015, 05:31 PM

Hi,

I found that the hosting folder had both web.config (web.config from local development and the web.host.config from the transformation), I suppose that the host executes the web.config. Therefore never had the right <connectionStrings>.

I published the web project again and it did it right. I can log in, but now I have the "Yellow screen of death" telling me when I click in PhotoAlbum/Gigs:

Keyword not supported: 'id'.
EntityException: The underlying provider failed on ConnectionString.

My connectionStrings again:

Code:

<connectionStrings>
    <add name="PlanetWroxConnectionString1" connectionString="Data Source=xxx.xxx.xxx;Initial Catalog=dbname;User ID=dbname;password=xxxxxx;Integrated Security=False;" providerName="System.Data.SqlClient" />
    
    <add name="PlanetWroxEntities" connectionString="metadata=res://*/App_Code.PlanetWrox.csdl|res://*/App_Code.PlanetWrox.ssdl|res://*/App_Code.PlanetWrox.msl;provider=System.Data.SqlClient;provider connection string=&quot;data source=xxx.xxx.xxx;Initial Catalog=dbname; Integrated Security=False;Id=dbname;Password=xxxxxx; MultipleActiveResultSets=True;&quot;" providerName="System.Data.EntityClient" />
  </connectionStrings>

Thanks.

StvnSpnz · November 7th, 2015, 09:22 AM

I think now my problem is that the EF cannot connect. Should I change

"...metadata=res://*/App_Code.PlanetWrox..."?

See my previous post

StvnSpnz · November 7th, 2015, 10:15 AM

Quote:

Originally Posted by StvnSpnz

Hi,

Keyword not supported: 'id'.
EntityException: The underlying provider failed on ConnectionString.

My connectionStrings again:

Code:

<connectionStrings>
    <add name="PlanetWroxConnectionString1" connectionString="Data Source=xxx.xxx.xxx;Initial Catalog=dbname;User ID=dbname;password=xxxxxx;Integrated Security=False;" providerName="System.Data.SqlClient" />
    
    <add name="PlanetWroxEntities" connectionString="metadata=res://*/App_Code.PlanetWrox.csdl|res://*/App_Code.PlanetWrox.ssdl|res://*/App_Code.PlanetWrox.msl;provider=System.Data.SqlClient;provider connection string=&quot;data source=xxx.xxx.xxx;Initial Catalog=dbname; Integrated Security=False;Id=dbname;Password=xxxxxx; MultipleActiveResultSets=True;&quot;" providerName="System.Data.EntityClient" />
  </connectionStrings>

Thanks.

My mistake.... Id intead User ID, now it worked....

Thanks for your valuable help, again.

Imar · November 7th, 2015, 05:21 PM

That's looking great (and familiar).

>> If want to see the biography text box CSS you told me, go to the NewTest Photo album which is the last one I did.

Yeah, exactly what I thought: a string without spaces which normal users won't enter.

Cheers,

Imar

StvnSpnz · November 7th, 2015, 05:49 PM

You said in the appendix B that Windows Authentication is more secure than SQL Auth. But, is it possible when the web is hosted with third parties?

Thanks again for your help all these days.

PS: Yeah, familiar. It's like an architect learning to build the Eiffel Tower, again.

So the order for the next levels is (books)
Pro ASP
Security, Membership
MVC
AJAX?

Imar · November 7th, 2015, 05:55 PM

>> But, is it possible when the web is hosted with third parties?

It depends on the host. Some do, some don't.

Imar