View Single Post
Old October 6th, 2015, 03:14 AM
Imar's Avatar
Imar Imar is offline
Wrox Author
Points: 70,322, Level: 100
Points: 70,322, Level: 100 Points: 70,322, Level: 100 Points: 70,322, Level: 100
Activity: 0%
Activity: 0% Activity: 0% Activity: 0%
Join Date: Jun 2003
Location: Utrecht, Netherlands.
Posts: 17,089
Thanks: 80
Thanked 1,576 Times in 1,552 Posts

Does that mean that there is EF code on the server, probably in the .NET Framework, that does something with the EF code in my ASP app before it's sent to the browser?
It depends. For older versions, up to 4.0, EF was part of the framework.

For newer versions, you can deploy EF in your own bin folder so you don't depend on the EF version on the server. In this case I was referring to the F version in your Bin folder on the server as you said you built the model direclty on the server which could have meant it was using an older or newer version of EF.

Hard to answer the other questions as you're still not providing enough information such as the actual compilation error you're getting.

As I'm thinking about this... does the Build > Publish Website do some actual processing so that simply using ftp to transfer files won't work with EF even though it works with SQL connects?
No, it shouldn't affect how EF works. Depending on how you deploy, your files may be precompiled but EF should just continue to work.


Imar Spaanjaars
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!
The Following User Says Thank You to Imar For This Useful Post:
Grodnik (October 7th, 2015)