NuGet Packages are missing

Question

I searched this problem but none of the solutions worked. I have Visual Studio Professional 2015 installed and I am using TFS. My NuGet version is 3.1.6. This problem is happening only in my C# Web API/MVC project.

I am getting the below error:

This project references NuGet package(s) that are missing on this computer. Use NuGet Package Restore to download them. For more information, see http://go.microsoft.com/fwlink/?LinkID=322105. The missing file is ..\packages\Microsoft.Net.Compilers.1.0.0\build\Microsoft.Net.Compilers.props

I do not have .nuget folder in my solutions.
I have a packages folder in the solution and when I delete it, it seems like NuGet does rebuild the dependencies but the project still has the above error.
I tried removing the project from TFS and it didn't fix it.
Along with the above error, all the references in the project have yellow warning signs and say they are missing.
When I checked the NuGet Package Manager for the project, everything that is "missing" has a green tick next to it, including Microsoft.Net.Compilers.
I tried adding a new Web API/MVC project and it faced a similar problem where most references such as Owin were "missing" with the yellow warning sign.

Vadim Kotov · Accepted Answer · 2017-12-14 13:36:09Z

398

I solved my issue by removing this code from .csproj file:

<Target Name="EnsureNuGetPackageBuildImports" BeforeTargets="PrepareForBuild"> <PropertyGroup> <ErrorText>This project references NuGet package(s) that are missing on this computer. Enable NuGet Package Restore to download them. For more information, see http://go.microsoft.com/fwlink/?LinkID=322105. The missing file is {0}.</ErrorText> </PropertyGroup> <Error Condition="!Exists('$(SolutionDir)\.nuget\NuGet.targets')" Text="$([System.String]::Format('$(ErrorText)', '$(SolutionDir)\.nuget\NuGet.targets'))" /> </Target>

edited Dec 14, 2017 at 13:36

Vadim Kotov

8,2848 gold badges51 silver badges63 bronze badges

answered Jan 30, 2016 at 12:24

DKR

5,8162 gold badges22 silver badges21 bronze badges

Sign up to request clarification or add additional context in comments.

14 Comments

Levi Fuller Over a year ago

Accepted answer would not work since I am referencing the project in multiple separate solutions. This was the only fix. Commented it out and it worked like a a charm.

HeyZiko Over a year ago

I could be wrong, but I believe this is "swatting the fly with the hammer". If, for whatever reason, the published location loses any other required nuget package, it will not error, giving you a false positive (i.e. deployment succeeds, but system fails). Not a fan, but I'm not going to downvote it because there are aspects of nuget I'm still not familiar with.

Tom McDonald Over a year ago

Confirmed this issue still exists in VS 2017. I migrated a project from visual studio 2015 to 2017 and got this error message upon first compile in 2017. This fixed the bug.

Nicow Over a year ago

Why delete functionality, risk your project breaking etc by doing this? As @HeyZiko points out this can lead to problems later on. I could just do what the error states "Enable package restore". See my answer somewhere on this page...

CodeHxr Over a year ago

This may be "swatting a fly with a hammer", but in my case, my project had ZERO nuget packages (one other project in the solution did, though, if that makes a difference, but that project compiled fine) and the options to "Enable package restore" were, in fact, checked.

|

Lee Taylor · Accepted Answer · 2021-03-17 14:42:14Z

307

I had the same error (missing exactly the same package) today. I also created a MVC + Web API project.

It happened because I moved the app files (including the .csproj) file to another location. I manually updated the .sln file but all packages dependencies are now (Visual Studio 2015) stored in .csproj file.

Editing the .csproj file and correcting the relative path to the solution folder (which contains the packages folder) solved the problem for me.

edited Mar 17, 2021 at 14:42

Lee Taylor

7,99416 gold badges38 silver badges53 bronze badges

answered Aug 30, 2015 at 11:43

Tiberiu Craciun

3,2811 gold badge15 silver badges12 bronze badges

11 Comments

Justin Wignall Over a year ago

Copying the Microsoft.Net.Compilers... folder from the old packages folder to the new packages location after a move if it is missing may be a final step required.

SpoiledTechie.com Over a year ago

I just removed that ONE package from my computer and it worked.

Andrew Jens Over a year ago

I also got the error when physically moving a project to a different location in the Visual Studio solution. None of the solutions on this page worked, so I made a copy of the project (on the file system) and completely removed all reference to the original project in VS. I then recreated the project and copied the bits and pieces into it (from the copy I made). Laborious, but it worked.

Nirman Over a year ago

I also had the same issue after moving project from one location to another. Fixing path of the packages in the ".csproj" file fixed the issue.

Francisco d'Anconia Over a year ago

@MiłoszWieczorek I tried running the command in Package Manager Console and it did not solve the issue. It reloaded all packages, but the references are still not found.

|

Community · Accepted Answer · 2020-06-20 09:12:55Z

54

BEWARE - this updates packages for the entire solution not just the project.

If you have one more missing nuget package that giving your error while building your solution use following command using Nuget Command Console from Tools > Nuget Package Manager > Package Manager Console. It will reinstall your all current packages.

Update-Package –reinstall

Update:

You can pass specific project name as a parameter.

Update-Package –reinstall -ProjectName SampleApp

edited Jun 20, 2020 at 9:12

CommunityBot

11 silver badge

answered Aug 30, 2015 at 13:04

Shyam Bhagat

7996 silver badges7 bronze badges

8 Comments

Patrick Borkowicz Over a year ago

This worked for me. The error popped up after for me after pushing changes through git on one system and pulling them on another. Maybe my .gitignore is not properly configured for nuget packages.

Rashmi Pandit Over a year ago

Beware ... this updates packages for the entire solution not just the project.

Nick Alexander Over a year ago

This worked for me. NuGet kept complaining about missing packages, but Visual Studio would not auto-resolve. It took a couple minutes to run completely, but this command fixed my problem.

Miłosz Wieczorek Over a year ago

You can add -ProjectName parameter to make it only for specific project, not entire solution.

rollsch Over a year ago

VS2017 crashed half way through this and it broke everything

|

Abdullah · Accepted Answer · 2019-04-09 11:21:10Z

this way solved my error : To open .csproj file for update in Visual Studio 2015+ Solution Explorer:

Right-click project name -> Unload Project

Right-click project name -> Edit .csproj

Remove the following lines :

<Target Name="EnsureNuGetPackageBuildImports" BeforeTargets="PrepareForBuild"> <PropertyGroup> <ErrorText>This project references NuGet package(s) that are missing on this computer. Use NuGet Package Restore to download them. For more information, see http://go.microsoft.com/fwlink/?LinkID=322105. The missing file is {0}.</ErrorText> </PropertyGroup> <Error Condition="!Exists('..\packages\Microsoft.Net.Compilers.1.0.0\build\Microsoft.Net.Compilers.props')" Text="$([System.String]::Format('$(ErrorText)', '..\packages\Microsoft.Net.Compilers.1.0.0\build\Microsoft.Net.Compilers.props'))" /> <Error Condition="!Exists('..\packages\Microsoft.CodeDom.Providers.DotNetCompilerPlatform.1.0.0\build\Microsoft.CodeDom.Providers.DotNetCompilerPlatform.props')" Text="$([System.String]::Format('$(ErrorText)', '..\packages\Microsoft.CodeDom.Providers.DotNetCompilerPlatform.1.0.0\build\Microsoft.CodeDom.Providers.DotNetCompilerPlatform.props'))" /> <Error Condition="!Exists('packages\Microsoft.Net.Compilers.1.0.0\build\Microsoft.Net.Compilers.props')" Text="$([System.String]::Format('$(ErrorText)', 'packages\Microsoft.Net.Compilers.1.0.0\build\Microsoft.Net.Compilers.props'))" /> <Error Condition="!Exists('packages\Microsoft.CodeDom.Providers.DotNetCompilerPlatform.1.0.0\build\Microsoft.CodeDom.Providers.DotNetCompilerPlatform.props')" Text="$([System.String]::Format('$(ErrorText)', 'packages\Microsoft.CodeDom.Providers.DotNetCompilerPlatform.1.0.0\build\Microsoft.CodeDom.Providers.DotNetCompilerPlatform.props'))" /> </Target>

Right-click project name -> Reload Project

Finally Build your solution.

After fixing manually the paths in csproj I removed the section EnsureNuGetPackageBuildImports and it worked perfectly. thanks
Worked for me. A bit overkill but other options didn't fix the issue.
Those conditions are checking that packages exists in two places. (a bit odd, one is enough). A better alternative to deleting them is to fix the path to point to the actual packages folder. It's relative. Your package folder is likely ..\..\packages or ..\..\..\packages or similar.

Ryan Russon · Accepted Answer · 2015-08-31 02:22:12Z

21

I had this exact frustrating message. What finally worked for me was deleting all files and folders inside /packages and letting VS re-fetch everything the next build.

answered Aug 31, 2015 at 2:22

Ryan Russon

1,0799 silver badges17 bronze badges

3 Comments

Vitor Canova Over a year ago

I did a right click on the Solution and Restore Nuget Packages.

Ziggler Over a year ago

I donot have any Restore Nuget Package when I right click on solution.... I am using VS 2013..

AceMark Over a year ago

also had to make sure that it restores to the right package. check the .csproj using note/Edit *.csproj for the location of the packages folder

Tom Stickel · Accepted Answer · 2015-10-07 00:41:17Z

Tiberiu is correct. I had to edit my .csproj file as the files were moved and caused this issue

 <Import Project="..\..\packages\Microsoft.CodeDom.Providers.DotNetCompilerPlatform.1.0.1\build\Microsoft.CodeDom.Providers.DotNetCompilerPlatform.props" Condition="Exists('..\..\packages\Microsoft.CodeDom.Providers.DotNetCompilerPlatform.1.0.1\build\Microsoft.CodeDom.Providers.DotNetCompilerPlatform.props')" />

I changed at top of the file and at the bottom

<Error Condition="!Exists('..\..\packages\Microsoft.Net.Compilers.1.0.0\build\Microsoft.Net.Compilers.props')" Text="$([System.String]::Format('$(ErrorText)', '..\..\packages\Microsoft.Net.Compilers.1.0.0\build\Microsoft.Net.Compilers.props'))" /> <Error Condition="!Exists('..\..\packages\Microsoft.CodeDom.Providers.DotNetCompilerPlatform.1.0.1\build\Microsoft.CodeDom.Providers.DotNetCompilerPlatform.props')" Text="$([System.String]::Format('$(ErrorText)', '..\..\packages\Microsoft.CodeDom.Providers.DotNetCompilerPlatform.1.0.1\build\Microsoft.CodeDom.Providers.DotNetCompilerPlatform.props'))" />

what did work for me in the end was to edit only the line at the end of the file, but not at the top

Mohsin Awan · Accepted Answer · 2016-11-19 13:55:40Z

I solved this issue by removing the following code from .csproj file

<Target Name="EnsureNuGetPackageBuildImports" BeforeTargets="PrepareForBuild"> <PropertyGroup> <ErrorText>This project references NuGet package(s) that are missing on this computer. Use NuGet Package Restore to download them. For more information, see http://go.microsoft.com/fwlink/?LinkID=322105. The missing file is {0}.</ErrorText> </PropertyGroup> <Error Condition="!Exists('..\..\..\Assemblies\NuGet\SpecFlow.Plus.Excel.1.4.2\build\SpecFlow.Plus.Excel.targets')" Text="$([System.String]::Format('$(ErrorText)', '..\..\..\Assemblies\NuGet\SpecFlow.Plus.Excel.1.4.2\build\SpecFlow.Plus.Excel.targets'))" />

But why where these wrong in the first place? Bug in Visual Studio?

Karthik · Accepted Answer · 2020-04-13 04:35:34Z

I solved the same issue with the following steps

Removed package <package id="Microsoft.CodeDom.Providers.DotNetCompilerPlatform" version="2.0.1" targetFramework="net46" /> from package.config file.
Edit the .csproj project file and removed the below settings. <Target Name="EnsureNuGetPackageBuildImports" BeforeTargets="PrepareForBuild"> <PropertyGroup> <ErrorText>This project references NuGet package(s) that are missing on this computer. Use NuGet Package Restore to download them. For more information, see http://go.microsoft.com/fwlink/?LinkID=322105. The missing file is {0}.</ErrorText> </PropertyGroup> <Error Condition="!Exists('..\packages\Microsoft.CodeDom.Providers.DotNetCompilerPlatform.2.0.1\build\net46\Microsoft.CodeDom.Providers.DotNetCompilerPlatform.props')" Text="$([System.String]::Format('$(ErrorText)', '..\packages\Microsoft.CodeDom.Providers.DotNetCompilerPlatform.2.0.1\build\net46\Microsoft.CodeDom.Providers.DotNetCompilerPlatform.props'))" /> </Target>
1. Go to package manager console and run the command Update-Package –reinstall

Point # 2 and 3 were given by other users and I appreciate those users. Point # 1, removing the Microsoft.CodeDom.Providers.DotNetCompilerPlatform from package.config file is more important. Also, after running the command mentioned in point #3, the issue resolved. All unwanted packages removed and required package reference updated.

Hope this helps someone.

innoSPG · Accepted Answer · 2016-04-27 16:59:36Z

A combination of the 2 answers worked for me. First I modified the .csproj file to remove the reference to 1.0.0 version

< Target Name="EnsureNuGetPackageBuildImports" BeforeTargets="PrepareForBuild" > ----Error--- < /Target>

and then did

Update-Package -Reinstall

from the and it worked.

Brian Vander Plaats · Accepted Answer · 2017-03-27 11:49:28Z

To expand on a few of the answers here, yes you could remove the following block from your .csproj file:

<Target Name="EnsureNuGetPackageBuildImports" BeforeTargets="PrepareForBuild">

and this fixes the issue, however in my case, I noticed that I had additional references to the .NET.Compilers and .CodeDom.Providers with different versions:

<Error Condition="!Exists('..\packages\Microsoft.Net.Compilers.1.0.0 <Error Condition="!Exists('..\packages\Microsoft.CodeDom.Providers.DotNetCompilerPlatform.1.0.0\ <Error Condition="!Exists('..\packages\Microsoft.Net.Compilers.2.0.1 <Error Condition="!Exists('..\packages\Microsoft.CodeDom.Providers.DotNetCompilerPlatform.1.0.3\

When my packages.config only referenced the following:

<package id="Microsoft.Net.Compilers" version="2.0.1" <package id="Microsoft.CodeDom.Providers.DotNetCompilerPlatform" version="1.0.3"

Removing the 1.0.0 items from the .csproj file fixed the issue.

This also applies when there is a rogue error condition referring to 3.5.0 when it has been updated to 3.7.0.

JWP · Accepted Answer · 2016-09-29 13:05:46Z

For me, the problem was that when I copied the solution to a new folder and opened it, it was missing the Nuget folder as shown below. I copied this folder over and everything worked. Note: This same folder was in our source control but not in this solutions project, it was up one directory.

Caspar Kleijne · Accepted Answer · 2019-08-08 09:14:49Z

6

Just enable NuGet Package Restore. Right click your solution > choose 'Enable NuGet Package Restore'.

This will create the .nuget folder with NuGet.Config file and fixed my problem.

edited Aug 8, 2019 at 9:14

Caspar Kleijne

21.9k13 gold badges74 silver badges102 bronze badges

answered May 9, 2017 at 11:09

Nicow

4454 silver badges7 bronze badges

2 Comments

Jain Prince Over a year ago

Thanks!! I too faced similar situation, and 'Enable NuGet Package Restore' worked.

Dalibor Over a year ago

It didn't wok for me, it says "All packages are already installed and there is nothing to restore."

MAK · Accepted Answer · 2016-01-24 18:36:38Z

I am using VS2012 and facing the same error. I removed the following Target tag from the .csproj file and it started compiling without any error.

<Target Name="EnsureNuGetPackageBuildImports" BeforeTargets="PrepareForBuild"> -- Error messages within Target Tag </Target>

Peter Ennis · Accepted Answer · 2015-09-21 01:27:50Z

The error message is completely correct. I tried all the tricks and none worked. The project (simple MVC Web App test) moved from Windows 8.1 VS 2015 Community to my new test box on Windows 10. All the latest updates to VS 2015 applied. I could not even install any newer version of the compilers package.

Loop: <LOOP>This seems to be a Ground Hog Day phenomena.</LOOP> GoTo Loop

I finally just copied Microsoft.Net.Compilers.1.0.0 from the old project into the new one and it worked. I could then start to update other packages to newer version. Looks like a nuget project upgrade process bug to me.

NOTE: The original project was created in VS 2015 and does not have any legacy nuget methodologies.

madannes · Accepted Answer · 2016-09-06 16:11:34Z

For anyone who stumbles here with the issue I had (some but not all packages being restored on a build server), the final piece of the puzzle for me was adding a NuGet.config in the root of my solution, sibling to the .SLN file as David Ebbo explained here: http://blog.davidebbo.com/2014/01/the-right-way-to-restore-nuget-packages.html.

From Ebbo's blog post, the file contents for me are simply

<?xml version="1.0" encoding="utf-8"?> <configuration> <packageSources> <add key="nuget.org" value="https://www.nuget.org/api/v2/" /> </packageSources> </configuration>

UPDATE:

The NuGet API URL has changed for v3 (current as of Sept 2016). From https://www.nuget.org/

<add key="nuget.org" value="https://api.nuget.org/v3/index.json" />

Community · Accepted Answer · 2020-06-20 09:12:55Z

Solution that works in my case - Visual Studio 2015 Enterprice, project .NET 4.6.1

Upgrade to Update 3
Install Web developer tools

kayleeFrye_onDeck · Accepted Answer · 2018-02-06 21:48:21Z

For DevOps/build engineers, you can probably fix this running nuget restore against the affected SLN, or project if you lack a SLN. I have to do this for our CI/CD builds for all our UWP projects.

Make sure nuget is installed on the build slave either in Visual Studio or standalone. If it's the latter, make sure it's in PATH and skip step 2.
Either open the VS Dev CMD console, or load it via an already open one, which you can do with the instructions below:
VS2015 call "%VS140COMNTOOLS%VsDevCmd.bat"
or
VS2017 call "%ProgramFiles(x86)%\Microsoft Visual Studio\2017\Enterprise\Common7\Tools\VsDevCmd.bat"
call nuget restore MyStuff.SLN or call nuget restore MyStuff.csproj if there's no SLN.

Ian Hale · Accepted Answer · 2018-03-12 20:18:55Z

For me, the packages were there under the correct path, but the build folders inside the package folder were not. I simply removed all the packages that it said were missing and rebuilt the solution and it successfully created the build folders and the .props files. So the error messages were correct in informing me that something was a miss.

Neil Thompson · Accepted Answer · 2018-08-07 12:27:28Z

I had this issue as a failed build in Azure, when deployed from Git.

Turns out my .gitignore was excluding the build folder from ..\packages\Microsoft.CodeDom.Providers.DotNetCompilerPlatform.2.0.0\build\net46\Microsoft.CodeDom.Providers.DotNetCompilerPlatform.props.

Once the build folder was (force) committed to Git, the issue was solved.

bsod_ · Accepted Answer · 2018-08-23 12:18:42Z

For me my gitignore file was ignoring my packages folder. The following gitignore line was causing the issue -

**/packages/*

Removed and it restored my packages folder. Hope this helps someone else.

Juan Carlos Puerto · Accepted Answer · 2019-04-24 10:51:24Z

The folder in my solution was named ".NET Project". By renaming it to "NET Project" everything worked fine. So the dot at the beginning was a bad idea.

Michal · Accepted Answer · 2019-06-27 08:14:48Z

In my case there was missing <RestorePackages>true</RestorePackages> in *.csproj file. It was not necessary to delete snippets of code I see in previous answers.

paul-2011 · Accepted Answer · 2019-08-28 19:03:24Z

A different user name is the common cause for this, Nuget downloads everything into: "C:\Users\USER_NAME\source\repos" and if you had the project previously setup on a different user name the .csproj file may still contain that old user name there, simply open it and do a search replace for "C:\Users\_OLD_USER_NAME\source\repos" to "C:\Users\NEW_USER_NAME\source\repos".

Jeff Dege · Accepted Answer · 2019-10-28 20:34:26Z

There seem to be multiple causes for this.

For mine, it was that the .csproj file contained references to two different versions of Microsoft.Bcl.Build.targets:

<Import Project="..\packages\Microsoft.Bcl.Build.1.0.14\tools\Microsoft.Bcl.Build.targets" Condition="Exists('..\packages\Microsoft.Bcl.Build.1.0.14\tools\Microsoft.Bcl.Build.targets')" /> <Target Name="EnsureBclBuildImported" BeforeTargets="BeforeBuild" Condition="'$(BclBuildImported)' == ''"> <Error Condition="!Exists('..\packages\Microsoft.Bcl.Build.1.0.14\tools\Microsoft.Bcl.Build.targets')" Text="This project references NuGet package(s) that are missing on this computer. Enable NuGet Package Restore to download them. For more information, see http://go.microsoft.com/fwlink/?LinkID=317567." HelpKeyword="BCLBUILD2001" /> <Error Condition="Exists('..\packages\Microsoft.Bcl.Build.1.0.14\tools\Microsoft.Bcl.Build.targets')" Text="The build restored NuGet packages. Build the project again to include these packages in the build. For more information, see http://go.microsoft.com/fwlink/?LinkID=317568." HelpKeyword="BCLBUILD2002" /> </Target> <Import Project="..\packages\Microsoft.Bcl.Build.1.0.21\build\Microsoft.Bcl.Build.targets" Condition="Exists('..\packages\Microsoft.Bcl.Build.1.0.21\build\Microsoft.Bcl.Build.targets')" /> <Target Name="EnsureNuGetPackageBuildImports" BeforeTargets="PrepareForBuild"> <PropertyGroup> <ErrorText>This project references NuGet package(s) that are missing on this computer. Use NuGet Package Restore to download them. For more information, see http://go.microsoft.com/fwlink/?LinkID=322105. The missing file is {0}.</ErrorText> </PropertyGroup> <Error Condition="!Exists('..\packages\Microsoft.Bcl.Build.1.0.21\build\Microsoft.Bcl.Build.targets')" Text="$([System.String]::Format('$(ErrorText)', '..\packages\Microsoft.Bcl.Build.1.0.21\build\Microsoft.Bcl.Build.targets'))" /> </Target>

I removed the old reference, and it solved the problem.

testing · Accepted Answer · 2020-01-17 10:05:20Z

You also get this error if you use package.config together with this build command

MSBuild.exe /t:Restore MySln.sln

In this case either switch to nuget restore command or use PackageReference.

Nick Rubino · Accepted Answer · 2016-08-27 18:10:11Z

I couldn't find any solutions to this so I added a copy of the nuget.exe and a powershell script to the root directory of the solution called prebuild.ps1 with the following content.

$nugetexe = 'nuget.exe' $args = 'restore SOLUTION_NAME_HERE.sln' Start-Process $nugetexe -ArgumentList $args

I called this powershell script in my build in the Pre-Build script path

user1429899 · Accepted Answer · 2016-10-11 14:41:36Z

Mine worked when I copied packages folder along with solution file and project folder. I just did not copy packages folder from previous place.

Parama Dharmika · Accepted Answer · 2016-12-06 16:07:46Z

You can also use the suggested error message as a hint. Here's how, find the Manage Packages for Solution, and click on the resolve missing nuget package.

That's it

Anurag Sharma · Accepted Answer · 2017-06-02 19:09:59Z

Comment the Compiler Option in WebConfig:

<!--<system.codedom> <compilers> <compiler language="c#;cs;csharp" extension=".cs" type="Microsoft.CodeDom.Providers.DotNetCompilerPlatform.CSharpCodeProvider, Microsoft.CodeDom.Providers.DotNetCompilerPlatform, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" warningLevel="4" compilerOptions="/langversion:6 /nowarn:1659;1699;1701" /> <compiler language="vb;vbs;visualbasic;vbscript" extension=".vb" type="Microsoft.CodeDom.Providers.DotNetCompilerPlatform.VBCodeProvider, Microsoft.CodeDom.Providers.DotNetCompilerPlatform, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" warningLevel="4" compilerOptions="/langversion:14 /nowarn:41008 /define:_MYTYPE=\&quot;Web\&quot; /optionInfer+" /> </compilers> </system.codedom>-->

Update the Latest Version of Packages in Package Config File

 <package id="Microsoft.CodeDom.Providers.DotNetCompilerPlatform" version="1.0.4" targetFramework="net452" />

Rebuild if all ok, no need to proceed, else Right-click the project, click 'unload project' Right-click the project again and edit .csproj file

Validate the path of Codedom, it was not having net45 in previous paths, add that manually, save, load, rebuild. It should work.

<Import Project="..\packages\Microsoft.CodeDom.Providers.DotNetCompilerPlatform.1.0.4\build\net45\Microsoft.CodeDom.Providers.DotNetCompilerPlatform.props" Condition="Exists('..\packages\Microsoft.CodeDom.Providers.DotNetCompilerPlatform.1.0.4\build\net45\Microsoft.CodeDom.Providers.DotNetCompilerPlatform.props')" />

Saravanan · Accepted Answer · 2017-10-05 20:02:52Z

As many suggested removing the <Target> tag may make it compile-able. Yet, beware of the fact that it has a side effect when you do it for test projects.

I got error related to MSTest.TestAdapter nuget package while compiling. Resolved that issue by removing <Target> tag. Though it made build successful, test methods became non discover-able. Test explorer won't list down the test methods in that project and Run Test or Debug Test won't work as well.

I encountered this while using Visual Studio 2017 and .Net framework 4.7, it can very well happen in other versions

I've exactly that problem using VS2017, .Net4.7 and a unit testing project. That project is added to multiple solutions. The automatic restore works but to the wrong place. Replace with $(SolutionDir) work but update failes. I asked that here. Do you have any solution found?

Collectives™ on Stack Overflow

NuGet Packages are missing

37 Answers 37

14 Comments

11 Comments

BEWARE - this updates packages for the entire solution not just the project.

8 Comments

3 Comments

3 Comments

1 Comment

1 Comment

Comments

Comments

1 Comment

Comments

2 Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

1 Comment

Linked

Hot Network Questions

Collectives™ on Stack Overflow

37 Answers 37

14 Comments

11 Comments

BEWARE - this updates packages for the entire solution not just the project.

8 Comments

3 Comments

3 Comments

1 Comment

1 Comment

Comments

Comments

1 Comment

Comments

2 Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

1 Comment

Linked

Related