Hi Imar,
the download link to sample file is this.

Please check this.

If I understand you correctly, this just works because LINQ to SQL embeds the connection string in the assembly and uses it as a default when no connection string is defined in the config file.

IMO, this is very undesirable as it means you need to redeploy your assemblies whenever the database connection string changes. The alternative to that is to use a connection string in the config file which is exactly what EF does.

Cheers,

Imar

__________________
Imar Spaanjaars
http://Imar.Spaanjaars.Com
Follow me on Twitter

Author of Beginning ASP.NET 4.5 : in C# and VB, Beginning ASP.NET Web Pages with WebMatrix
and Beginning ASP.NET 4 : in C# and VB.
Did this post help you? Click the button below this post to show your appreciation!

Thanks Imar for clarification.

But apart from what EF provides (whether it is functionality), is not it possible with EF what L2S provides?

It is possible Both ObjectContext and DbContext have a constructor that lets you pass in a connection string. That way you can hardcode the connection string so it gets embedded in the assembly:

http://msdn.microsoft.com/en-us/libr...ctcontext.aspx
http://msdn.microsoft.com/en-us/libr...vs.103%29.aspx

But again: I would recommend against this as it means embedding the connection string in the assemblies.

Cheers,

Imar

__________________
Imar Spaanjaars
http://Imar.Spaanjaars.Com
Follow me on Twitter

Author of Beginning ASP.NET 4.5 : in C# and VB, Beginning ASP.NET Web Pages with WebMatrix
and Beginning ASP.NET 4 : in C# and VB.
Did this post help you? Click the button below this post to show your appreciation!

Thanks Imar,
it worked.

Thanks for clearing it out there...really appreciate that..

__________________
REI Coupon