none
Can I bin deploy EF 4.1? RRS feed

  • Question

  • Or does it need to be isntalled on every machine that runs the asp.net application that uses it?

    Thanks!


    Tuesday, July 26, 2011 1:55 PM

Answers

  • Actually, I finally got around to trying it and it \bin deploys just fine and does not need to be installed on the server.
    • Marked as answer by CodeSlinger Friday, July 29, 2011 10:03 PM
    Friday, July 29, 2011 10:02 PM

All replies

  • EF 4.1 needs to be install on all systems that run the ASP.Net applications that use EF 4.1 functionality.

     

     


    Fernando (MCSD)

    If a post answers your question, please click "Mark As Answer" on that post and "Mark as Helpful".
    Tuesday, July 26, 2011 1:59 PM
  • On 7/26/2011 9:55 AM, CodeSlinger wrote:
    > Or does it need to be isntalled on every machine that runs the asp.net
    > application that uses it?
    >
    > Thanks!
    >
    >
     
    EF is part of the .NET Framework so you have to install the .NET
    Framework on any machine that is going to access a database using EF.
     
    • Marked as answer by CodeSlinger Friday, July 29, 2011 10:03 PM
    • Unmarked as answer by CodeSlinger Friday, July 29, 2011 10:03 PM
    Tuesday, July 26, 2011 5:23 PM
  • Actually EF 4.1 is NOT part of the .NET 4.0 framework though of course that would have to be there as well since an ASP.NET app...

    Tuesday, July 26, 2011 5:38 PM
  • On 7/26/2011 1:38 PM, CodeSlinger wrote:
    > Actually EF 4.1 is NOT part of the .NET 4.0 framework though of course
    > that would have to be there as well since an ASP.NET app...
    >
     
    What is your point? You are not coming around it. So your point is kind
    of moot.
     
    Tuesday, July 26, 2011 5:53 PM
  • My point is that the EntityFramework.dll for EF 4.1 in NOT part of .NET 4.0 and so has to either be "bin" installed or all of EF 4.1 has to be installed. If I had no point it could not have been moot :)
    Tuesday, July 26, 2011 6:08 PM
  • On 7/26/2011 2:08 PM, CodeSlinger wrote:
    > My point is that the EntityFramework.dll for EF 4.1 in NOT part of .NET
    > 4.0 and so has to either be "bin" installed or all of EF 4.1 has to be
    > installed. If I had no point it could not have been moot :)
     
    You can play Mickey Mouse with it if you want. I would have just
    installed the .NET Framework and be done with it instead of trying to
    jump through hoops over it.
     
    Tuesday, July 26, 2011 6:18 PM
  • Darn Old, there is something you are not understanding here...

    "the EntityFramework.dll for EF 4.1 is NOT part of .NET 4.0!!!"

    Tuesday, July 26, 2011 7:31 PM
  • On 7/26/2011 3:31 PM, CodeSlinger wrote:
    > Darn Old, there is something you are not understanding here...
    >
    > "the EntityFramework.dll for EF 4.1 is NOT part of .NET 4.0!!!"
    >
     
    You are boring me with this.
     
    Tuesday, July 26, 2011 7:36 PM
  • What is your problem beside totally not knowing what you are talking about? Do you not understand English? Get lost and pls quit posting...
    Tuesday, July 26, 2011 7:48 PM
  • On 7/26/2011 3:48 PM, CodeSlinger wrote:
    > What is your problem beside totally not knowing what you are talking
    > about? Do you not understand English? Get lost and pls quit posting...
     
    I want to know who do you think you are that you can tell anyone what he
    or she should be doing. You are of no interest to me. Why don't you flip
    the script and tell yourself to stop posting. Get a life and stop
    thinking that you can tell anyone what to do.
     
    Tuesday, July 26, 2011 7:56 PM
  • On 7/26/2011 3:48 PM, CodeSlinger wrote:
     
    <snipped>
     
    And with a nym like CodeSlinger you have told me all I need to know
    about some as arrogant as you are.
     
    Tuesday, July 26, 2011 8:01 PM
  • f off...
    • Marked as answer by CodeSlinger Wednesday, July 27, 2011 1:48 AM
    • Unmarked as answer by CodeSlinger Friday, July 29, 2011 10:01 PM
    Tuesday, July 26, 2011 8:24 PM
  • On 7/26/2011 4:24 PM, CodeSlinger wrote:
    > f off...
     
    Yeah yeah I thought so Pampers.
     
    Tuesday, July 26, 2011 8:31 PM
  • Actually, I finally got around to trying it and it \bin deploys just fine and does not need to be installed on the server.
    • Marked as answer by CodeSlinger Friday, July 29, 2011 10:03 PM
    Friday, July 29, 2011 10:02 PM
  • You can play Mickey Mouse with it if you want. I would have just
    installed the .NET Framework and be done with it instead of trying to
    jump through hoops over it.
     

    CodeSlinger is right - EF 4.1 is NOT part (built-in) of .NET Framework 4.0 (only EF 4.0 is), so it either has to be installed using the provider installer from http://www.microsoft.com/download/en/details.aspx?id=26825 or all necessary assemblies have to be bin-deployed (or placed on GAC) ...
    Wednesday, August 10, 2011 7:32 AM
  • On 7/26/2011 2:08 PM, CodeSlinger wrote:
    > My point is that the EntityFramework.dll for EF 4.1 in NOT part of .NET
    > 4.0 and so has to either be "bin" installed or all of EF 4.1 has to be
    > installed. If I had no point it could not have been moot :)
     
    You can play Mickey Mouse with it if you want. I would have just
    installed the .NET Framework and be done with it instead of trying to
    jump through hoops over it.
     
    Because if you install the .NET Framework you only get EF 4.0, not 4.1.  Therefore, if you are using 4.1 features on your dev box and are referencing 4.1 DLLs, then your application will not work when you deploy to a server that only has EF 4.0.  This much is obvious to everyone here, but you.  Your responses are rude and contributed nothing, and detracted from the ultimate outcome.  You really owe CodeSlinger an apology IMO.
    Friday, February 17, 2012 9:52 PM