Visual Studio 2017 Metadata file EntityFramework.dll could not be foundMetadata file '.dll' could not be foundMetadata file '.dll' could not be foundThe type or namespace name could not be foundWriting to output window of Visual StudioVisual Studio “Could not copy” … during buildEntityFramework.dll missing?Entity framework Not Found after updating to Visual Studio 2013 update 4MSBuild CopyFilesMarkedCopyLocal Entity Framework IssueCould not load file or assembly “System.Net.Http, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a”Roslyn Issue - Metadata file System.Runtime.dll could not be foundMySQL with Visual Studio 2017

May a hotel provide accommodation for fewer people than booked?

Patio gate not at right angle to the house

Prepare a user to perform an action before proceeding to the next step

Given mean and SD, can we approximate the underlying distribution?

How did Biff return to 2015 from 1955 without a lightning strike?

Problem with Alignment of Tabular Data Using siunitx

Derivative is just speed of change?

Can machine learning learn a function like finding maximum from a list?

How to innovate in OR

Word for giving preference to the oldest child

How char is processed in math mode?

Should students have access to past exams or an exam bank?

Is it possible to tell if a child will turn into a Hag?

Why would an invisible personal shield be necessary?

Applications of pure mathematics in operations research

What are the cons of stateless password generators?

Academic progression in Germany, what happens after a postdoc? What is the next step?

How to prevent a single-element caster from being useless against immune foes?

Balancing Humanoid fantasy races: Elves

Do cabinets and speaker enclosures add the additional harmonic contents?

Database Cache Memory in Performance Monitor drops down significantly after DBCC CheckDB

What is the full text of the song about the failed battle of Kiska?

"Valet parking " or "parking valet"

What force enables us to walk? Friction or normal reaction?



Visual Studio 2017 Metadata file EntityFramework.dll could not be found


Metadata file '.dll' could not be foundMetadata file '.dll' could not be foundThe type or namespace name could not be foundWriting to output window of Visual StudioVisual Studio “Could not copy” … during buildEntityFramework.dll missing?Entity framework Not Found after updating to Visual Studio 2013 update 4MSBuild CopyFilesMarkedCopyLocal Entity Framework IssueCould not load file or assembly “System.Net.Http, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a”Roslyn Issue - Metadata file System.Runtime.dll could not be foundMySQL with Visual Studio 2017






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;








0















I am working on a C# program that utilizes EntityFramework, I've cloned the program from git repo, but now it is having that dreadful Metadata file 'EntityFramework.dll' could not be found error. I have searched and tried countless suggestions for this kind of problem, but none worked. I've already checked that the reference to EntityFramework.dll in the .csproj files are correct and it is definitely there under the packagesEntityFramework.6.2.0libnet45 folder. So I am not sure what else to try.










share|improve this question






























    0















    I am working on a C# program that utilizes EntityFramework, I've cloned the program from git repo, but now it is having that dreadful Metadata file 'EntityFramework.dll' could not be found error. I have searched and tried countless suggestions for this kind of problem, but none worked. I've already checked that the reference to EntityFramework.dll in the .csproj files are correct and it is definitely there under the packagesEntityFramework.6.2.0libnet45 folder. So I am not sure what else to try.










    share|improve this question


























      0












      0








      0








      I am working on a C# program that utilizes EntityFramework, I've cloned the program from git repo, but now it is having that dreadful Metadata file 'EntityFramework.dll' could not be found error. I have searched and tried countless suggestions for this kind of problem, but none worked. I've already checked that the reference to EntityFramework.dll in the .csproj files are correct and it is definitely there under the packagesEntityFramework.6.2.0libnet45 folder. So I am not sure what else to try.










      share|improve this question














      I am working on a C# program that utilizes EntityFramework, I've cloned the program from git repo, but now it is having that dreadful Metadata file 'EntityFramework.dll' could not be found error. I have searched and tried countless suggestions for this kind of problem, but none worked. I've already checked that the reference to EntityFramework.dll in the .csproj files are correct and it is definitely there under the packagesEntityFramework.6.2.0libnet45 folder. So I am not sure what else to try.







      c# entity-framework






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Mar 26 at 20:29









      For CommentFor Comment

      2374 silver badges13 bronze badges




      2374 silver badges13 bronze badges

























          4 Answers
          4






          active

          oldest

          votes


















          0














          please have a look on the bin folder ,sometimes the dlls do not exist there .






          share|improve this answer

























          • well, the error is preventing the compilation to finish, so of course the DLL is not going to be in the bin folder, plus, the issue is why the compilation is not finding that DLL in the first place.

            – For Comment
            Mar 26 at 20:44











          • have you tried to run Visual Studio as administrator , remove obj folder , Rebuild the entire solution ?

            – Mahmoud-Abdelslam
            Mar 26 at 21:10



















          0














          This typically happens when teams check in files that should not be checked in (such as the .suo file) or have "optimized" their builds to exclude rarely changed projects. (unticking projects in the configuration manager.)



          Another common cause for missing references is when devs reference a dependency from a /bin folder instead of the packages folder, but it sounds like you've confirmed that isn't the case.



          Other questions such as Metadata file '.dll' could not be found list a number of things to check, so your problem will surely be one of these. Try building each project individually, working from projects that have no project dependencies upwards to the main application project(s). Ensure they're running the same .Net versions, check the solution NuGet packages for dependencies with "multiple versions" and consolidate these so that the solution is using a single version of each dependency. (generally good for cleaning up) Also look at .config files for version re-directs that sometimes get zombified in source control.






          share|improve this answer

























          • Yes, these are really good suggestions.

            – For Comment
            Mar 26 at 22:24


















          0














          Ok, I've resolved this problem. Here is what happened. Apparently, when cloning into local directory, one of the folder on the path has a space in its name (like My DSS), and this nuget issue seems to indicate the inability of nuget to find package with space in path. So, once I changed that folder's name to MyDSS, it compiled successfully.






          share|improve this answer
































            0














            In Visual Studio, on top, click on Build -> Configuration Manager. Make sure that the build checkbox next to your project is checked. In case it already is, uncheck it and then make it checked again. Clean your Solution and Build it again after this.






            share|improve this answer





























              Your Answer






              StackExchange.ifUsing("editor", function ()
              StackExchange.using("externalEditor", function ()
              StackExchange.using("snippets", function ()
              StackExchange.snippets.init();
              );
              );
              , "code-snippets");

              StackExchange.ready(function()
              var channelOptions =
              tags: "".split(" "),
              id: "1"
              ;
              initTagRenderer("".split(" "), "".split(" "), channelOptions);

              StackExchange.using("externalEditor", function()
              // Have to fire editor after snippets, if snippets enabled
              if (StackExchange.settings.snippets.snippetsEnabled)
              StackExchange.using("snippets", function()
              createEditor();
              );

              else
              createEditor();

              );

              function createEditor()
              StackExchange.prepareEditor(
              heartbeatType: 'answer',
              autoActivateHeartbeat: false,
              convertImagesToLinks: true,
              noModals: true,
              showLowRepImageUploadWarning: true,
              reputationToPostImages: 10,
              bindNavPrevention: true,
              postfix: "",
              imageUploader:
              brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
              contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
              allowUrls: true
              ,
              onDemand: true,
              discardSelector: ".discard-answer"
              ,immediatelyShowMarkdownHelp:true
              );



              );













              draft saved

              draft discarded


















              StackExchange.ready(
              function ()
              StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55365727%2fvisual-studio-2017-metadata-file-entityframework-dll-could-not-be-found%23new-answer', 'question_page');

              );

              Post as a guest















              Required, but never shown

























              4 Answers
              4






              active

              oldest

              votes








              4 Answers
              4






              active

              oldest

              votes









              active

              oldest

              votes






              active

              oldest

              votes









              0














              please have a look on the bin folder ,sometimes the dlls do not exist there .






              share|improve this answer

























              • well, the error is preventing the compilation to finish, so of course the DLL is not going to be in the bin folder, plus, the issue is why the compilation is not finding that DLL in the first place.

                – For Comment
                Mar 26 at 20:44











              • have you tried to run Visual Studio as administrator , remove obj folder , Rebuild the entire solution ?

                – Mahmoud-Abdelslam
                Mar 26 at 21:10
















              0














              please have a look on the bin folder ,sometimes the dlls do not exist there .






              share|improve this answer

























              • well, the error is preventing the compilation to finish, so of course the DLL is not going to be in the bin folder, plus, the issue is why the compilation is not finding that DLL in the first place.

                – For Comment
                Mar 26 at 20:44











              • have you tried to run Visual Studio as administrator , remove obj folder , Rebuild the entire solution ?

                – Mahmoud-Abdelslam
                Mar 26 at 21:10














              0












              0








              0







              please have a look on the bin folder ,sometimes the dlls do not exist there .






              share|improve this answer













              please have a look on the bin folder ,sometimes the dlls do not exist there .







              share|improve this answer












              share|improve this answer



              share|improve this answer










              answered Mar 26 at 20:33









              Mahmoud-AbdelslamMahmoud-Abdelslam

              1591 silver badge7 bronze badges




              1591 silver badge7 bronze badges















              • well, the error is preventing the compilation to finish, so of course the DLL is not going to be in the bin folder, plus, the issue is why the compilation is not finding that DLL in the first place.

                – For Comment
                Mar 26 at 20:44











              • have you tried to run Visual Studio as administrator , remove obj folder , Rebuild the entire solution ?

                – Mahmoud-Abdelslam
                Mar 26 at 21:10


















              • well, the error is preventing the compilation to finish, so of course the DLL is not going to be in the bin folder, plus, the issue is why the compilation is not finding that DLL in the first place.

                – For Comment
                Mar 26 at 20:44











              • have you tried to run Visual Studio as administrator , remove obj folder , Rebuild the entire solution ?

                – Mahmoud-Abdelslam
                Mar 26 at 21:10

















              well, the error is preventing the compilation to finish, so of course the DLL is not going to be in the bin folder, plus, the issue is why the compilation is not finding that DLL in the first place.

              – For Comment
              Mar 26 at 20:44





              well, the error is preventing the compilation to finish, so of course the DLL is not going to be in the bin folder, plus, the issue is why the compilation is not finding that DLL in the first place.

              – For Comment
              Mar 26 at 20:44













              have you tried to run Visual Studio as administrator , remove obj folder , Rebuild the entire solution ?

              – Mahmoud-Abdelslam
              Mar 26 at 21:10






              have you tried to run Visual Studio as administrator , remove obj folder , Rebuild the entire solution ?

              – Mahmoud-Abdelslam
              Mar 26 at 21:10














              0














              This typically happens when teams check in files that should not be checked in (such as the .suo file) or have "optimized" their builds to exclude rarely changed projects. (unticking projects in the configuration manager.)



              Another common cause for missing references is when devs reference a dependency from a /bin folder instead of the packages folder, but it sounds like you've confirmed that isn't the case.



              Other questions such as Metadata file '.dll' could not be found list a number of things to check, so your problem will surely be one of these. Try building each project individually, working from projects that have no project dependencies upwards to the main application project(s). Ensure they're running the same .Net versions, check the solution NuGet packages for dependencies with "multiple versions" and consolidate these so that the solution is using a single version of each dependency. (generally good for cleaning up) Also look at .config files for version re-directs that sometimes get zombified in source control.






              share|improve this answer

























              • Yes, these are really good suggestions.

                – For Comment
                Mar 26 at 22:24















              0














              This typically happens when teams check in files that should not be checked in (such as the .suo file) or have "optimized" their builds to exclude rarely changed projects. (unticking projects in the configuration manager.)



              Another common cause for missing references is when devs reference a dependency from a /bin folder instead of the packages folder, but it sounds like you've confirmed that isn't the case.



              Other questions such as Metadata file '.dll' could not be found list a number of things to check, so your problem will surely be one of these. Try building each project individually, working from projects that have no project dependencies upwards to the main application project(s). Ensure they're running the same .Net versions, check the solution NuGet packages for dependencies with "multiple versions" and consolidate these so that the solution is using a single version of each dependency. (generally good for cleaning up) Also look at .config files for version re-directs that sometimes get zombified in source control.






              share|improve this answer

























              • Yes, these are really good suggestions.

                – For Comment
                Mar 26 at 22:24













              0












              0








              0







              This typically happens when teams check in files that should not be checked in (such as the .suo file) or have "optimized" their builds to exclude rarely changed projects. (unticking projects in the configuration manager.)



              Another common cause for missing references is when devs reference a dependency from a /bin folder instead of the packages folder, but it sounds like you've confirmed that isn't the case.



              Other questions such as Metadata file '.dll' could not be found list a number of things to check, so your problem will surely be one of these. Try building each project individually, working from projects that have no project dependencies upwards to the main application project(s). Ensure they're running the same .Net versions, check the solution NuGet packages for dependencies with "multiple versions" and consolidate these so that the solution is using a single version of each dependency. (generally good for cleaning up) Also look at .config files for version re-directs that sometimes get zombified in source control.






              share|improve this answer













              This typically happens when teams check in files that should not be checked in (such as the .suo file) or have "optimized" their builds to exclude rarely changed projects. (unticking projects in the configuration manager.)



              Another common cause for missing references is when devs reference a dependency from a /bin folder instead of the packages folder, but it sounds like you've confirmed that isn't the case.



              Other questions such as Metadata file '.dll' could not be found list a number of things to check, so your problem will surely be one of these. Try building each project individually, working from projects that have no project dependencies upwards to the main application project(s). Ensure they're running the same .Net versions, check the solution NuGet packages for dependencies with "multiple versions" and consolidate these so that the solution is using a single version of each dependency. (generally good for cleaning up) Also look at .config files for version re-directs that sometimes get zombified in source control.







              share|improve this answer












              share|improve this answer



              share|improve this answer










              answered Mar 26 at 22:09









              Steve PySteve Py

              8,0451 gold badge12 silver badges22 bronze badges




              8,0451 gold badge12 silver badges22 bronze badges















              • Yes, these are really good suggestions.

                – For Comment
                Mar 26 at 22:24

















              • Yes, these are really good suggestions.

                – For Comment
                Mar 26 at 22:24
















              Yes, these are really good suggestions.

              – For Comment
              Mar 26 at 22:24





              Yes, these are really good suggestions.

              – For Comment
              Mar 26 at 22:24











              0














              Ok, I've resolved this problem. Here is what happened. Apparently, when cloning into local directory, one of the folder on the path has a space in its name (like My DSS), and this nuget issue seems to indicate the inability of nuget to find package with space in path. So, once I changed that folder's name to MyDSS, it compiled successfully.






              share|improve this answer





























                0














                Ok, I've resolved this problem. Here is what happened. Apparently, when cloning into local directory, one of the folder on the path has a space in its name (like My DSS), and this nuget issue seems to indicate the inability of nuget to find package with space in path. So, once I changed that folder's name to MyDSS, it compiled successfully.






                share|improve this answer



























                  0












                  0








                  0







                  Ok, I've resolved this problem. Here is what happened. Apparently, when cloning into local directory, one of the folder on the path has a space in its name (like My DSS), and this nuget issue seems to indicate the inability of nuget to find package with space in path. So, once I changed that folder's name to MyDSS, it compiled successfully.






                  share|improve this answer













                  Ok, I've resolved this problem. Here is what happened. Apparently, when cloning into local directory, one of the folder on the path has a space in its name (like My DSS), and this nuget issue seems to indicate the inability of nuget to find package with space in path. So, once I changed that folder's name to MyDSS, it compiled successfully.







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered Mar 26 at 22:21









                  For CommentFor Comment

                  2374 silver badges13 bronze badges




                  2374 silver badges13 bronze badges
























                      0














                      In Visual Studio, on top, click on Build -> Configuration Manager. Make sure that the build checkbox next to your project is checked. In case it already is, uncheck it and then make it checked again. Clean your Solution and Build it again after this.






                      share|improve this answer































                        0














                        In Visual Studio, on top, click on Build -> Configuration Manager. Make sure that the build checkbox next to your project is checked. In case it already is, uncheck it and then make it checked again. Clean your Solution and Build it again after this.






                        share|improve this answer





























                          0












                          0








                          0







                          In Visual Studio, on top, click on Build -> Configuration Manager. Make sure that the build checkbox next to your project is checked. In case it already is, uncheck it and then make it checked again. Clean your Solution and Build it again after this.






                          share|improve this answer















                          In Visual Studio, on top, click on Build -> Configuration Manager. Make sure that the build checkbox next to your project is checked. In case it already is, uncheck it and then make it checked again. Clean your Solution and Build it again after this.







                          share|improve this answer














                          share|improve this answer



                          share|improve this answer








                          edited Mar 27 at 9:19









                          E_net4

                          14.1k7 gold badges41 silver badges79 bronze badges




                          14.1k7 gold badges41 silver badges79 bronze badges










                          answered Mar 26 at 21:05









                          Hassnain AliHassnain Ali

                          737 bronze badges




                          737 bronze badges






























                              draft saved

                              draft discarded
















































                              Thanks for contributing an answer to Stack Overflow!


                              • Please be sure to answer the question. Provide details and share your research!

                              But avoid


                              • Asking for help, clarification, or responding to other answers.

                              • Making statements based on opinion; back them up with references or personal experience.

                              To learn more, see our tips on writing great answers.




                              draft saved


                              draft discarded














                              StackExchange.ready(
                              function ()
                              StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55365727%2fvisual-studio-2017-metadata-file-entityframework-dll-could-not-be-found%23new-answer', 'question_page');

                              );

                              Post as a guest















                              Required, but never shown





















































                              Required, but never shown














                              Required, but never shown












                              Required, but never shown







                              Required, but never shown

































                              Required, but never shown














                              Required, but never shown












                              Required, but never shown







                              Required, but never shown







                              Popular posts from this blog

                              SQL error code 1064 with creating Laravel foreign keysForeign key constraints: When to use ON UPDATE and ON DELETEDropping column with foreign key Laravel error: General error: 1025 Error on renameLaravel SQL Can't create tableLaravel Migration foreign key errorLaravel php artisan migrate:refresh giving a syntax errorSQLSTATE[42S01]: Base table or view already exists or Base table or view already exists: 1050 Tableerror in migrating laravel file to xampp serverSyntax error or access violation: 1064:syntax to use near 'unsigned not null, modelName varchar(191) not null, title varchar(191) not nLaravel cannot create new table field in mysqlLaravel 5.7:Last migration creates table but is not registered in the migration table

                              용인 삼성생명 블루밍스 목차 통계 역대 감독 선수단 응원단 경기장 같이 보기 외부 링크 둘러보기 메뉴samsungblueminx.comeh선수 명단용인 삼성생명 블루밍스용인 삼성생명 블루밍스ehsamsungblueminx.comeheheheh

                              155 수학 과학 기타 둘러보기 메뉴eh추가해eh문서를 완성해