Assets file obj\project.assets.json doesn't have a target - VS2017

Question

Using Visual Studio 2017, AspNetCore 1.1.2

All of a sudden I am getting following error when I am trying to publish (Release build) any project in the solution:

Assets file 'C:\example\obj\project.assets.json' doesn't have a target for '.NETFramework,Version=v4.5.2/win7-x86'. Ensure that restore has run and that you have included 'net452' in the TargetFrameworks for your project. You may also need to include 'win7-x86' in your project's RuntimeIdentifiers.

Have checked in the project.assets.json files, I have:

"targets": {
  ".NETFramework,Version=v4.5.2": {

and

"runtimes": {
  "win7-x86": {
    "#import": []
  }

In the *.csproj files I have:

  <PropertyGroup>
      <TargetFramework>net452</TargetFramework>
  </PropertyGroup>

  <PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Debug|AnyCPU'">
      <PlatformTarget>x86</PlatformTarget>
  </PropertyGroup>

Have made no changes to config in the projects. Only thing is that I have updated VS2017 to latest version today, 15.6.3. Could this cause issue?

Please clarify: .NET Framework and .NET Core are two different things. It doesn't appear that you're using .NET Core at all here. — McGuireV10, Mar 20 '18 at 19:18
Just in case someone finds this after running into the same problem as me: one of the issues you can run into is a mismatch between .NET Standard and .NET Core when you're doing multi-targeting. You can't have a library target .NET Standard and then use `dotnet build -f netcoreapp2.1` despite the code being technically compatible. You either need to use `-f netstandard2.0` and add that to your assets file as a target, or switch to targeting .NET Core 2.1. — Polynomial, Nov 28 '18 at 17:14
https://developercommunity.visualstudio.com/t/error-NETSDK1005:-Assets-file-projecta/1248649?preview=true — kayleeFrye_onDeck, Feb 03 '23 at 01:07

score 158 · Accepted Answer · edited Jul 05 '21 at 22:36

According to the Microsoft blog (which, bizarrely, my account doesn't have permissions to post in), this isn't a bug, and is entirely caused by ReSharper. If you disable this, the problem goes away.

Errr, one problem: I'm getting this error, and I don't have ReSharper.

After a lot of hunting around, I found the reason I was getting the error on my .NET Core project which had been upgraded from 1.0 to 2.1.

When running my project in Debug or Release mode, everything worked fine, but when I tried to publish to Azure, I got that error:

Assets file '(mikesproject)\obj\project.assets.json' doesn't have a target for '.NETCoreApp,Version=v2.0'. Ensure that restore has run and that you have included 'netcoreapp2.0' in the TargetFrameworks for your project.

Although I had updated the version of .NET Core to 2.1 in Project\Properties and upgraded the various nuget packages, there was one place which hadn't picked up this change... the Publish Profile file.

I needed to go into the Properties\PublishProfiles folder in my solution, open up the .pubxml file relating to the way I was publishing to Azure, and change this setting from netcoreapp2.0 to netcoreapp2.1:

<Project ToolsVersion="4.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
  <PropertyGroup>
    . . . 
    <TargetFramework>netcoreapp2.0</TargetFramework>
    . . . 
  </PropertyGroup>
</Project>

Ridiculous, hey?

I do wish Microsoft error messages gave some clue as to the source of problems like this.

Removed and created a new Publish Profile and then it worked! — Westerlund.io, Jun 17 '19 at 10:37
I'm running into the same thing now. I have a simple class library project targeting both net47 and net6.0. Resharper disabled and no .pubxml file. I'm at a loss on why this is happening. (BTW, running "dotnet build" in "development powershell" works and creates a good project.assets.json file. =/ — MarcWeintraub, Sep 19 '22 at 14:07

score 128 · Answer 2 · answered Nov 03 '18 at 19:22

128

Restarting Visual Studio solved the error for me.

answered Nov 03 '18 at 19:22

Ferro

1,863
2
14
20

4

Updated an open solution from github which included new framework targets, this answer fixed the problem when nothing else did. – Adrian Seeley Mar 26 '19 at 18:46
3

This solved my issue in VS 16.8.2 with netcoreapp3.1;netstandard2.0 – Josh Graham Mar 29 '21 at 22:42
I upgraded a handful of .NET standard 2.0 libraries in a solution to 2.1, everything was normal at first until I did some stashing and changed branches; then I was met with this when trying to run tests. Restarting VS cleared the issue... – Urk Aug 30 '22 at 17:32
124 upvotes, including mine. Really. Just restarting it. – aleee Mar 29 '23 at 20:26
Still applicable in VS2022 and .NET 7.0. – Roman Starkov Apr 25 '23 at 19:29

Paul · Answer 3 · 2019-05-10T12:34:56.717

54

Right click on the project file, and click unload. Then right click on the project and reload.

edited May 10 '19 at 12:34

answered Mar 05 '19 at 18:37

Paul

2,330
2
19
18

8

This worked for me after I also "Rebuilt" the offending project – mystackoverflow1212 Sep 12 '19 at 15:19
this worked in VS2022 – cikatomo Jan 17 '23 at 04:07

score 40 · Answer 4 · answered Dec 13 '19 at 12:17

40

Had this error in similar situation. This has helped me: Link

This is my property group in *.csproj file of my .net core 3.0 project:

<PropertyGroup>
    <OutputType>Exe</OutputType>
    <TargetFrameworks>netcoreapp3.0</TargetFrameworks>
    <RuntimeIdentifier>win-x64</RuntimeIdentifier>  <----- SOLVES IT. Mandatory Line
</PropertyGroup>

answered Dec 13 '19 at 12:17

CodingYourLife

7,172
5
55
69

1

Hint: If you face new/other issues by this change (especially when working with EF Core), just use the plural form instead: ``. – Martin Schneider Nov 10 '22 at 12:15

k4st0r42 · Answer 5 · 2020-11-24T10:55:39.517

28

Migrating from nuget 5.4 to nuget 5.8 solve the problem on my devops build server

edited Nov 24 '20 at 10:55

answered Nov 12 '20 at 09:20

k4st0r42

1,174
1
15
29

kayleeFrye_onDeck's answer is the better answer here, because it gives a pointer to an article that explains _why_ the upgrade is the thing to do. – JdeBP Nov 06 '21 at 03:46
How to migrate nuget version? – ManirajSS Jun 08 '22 at 05:51
How did you find out it's required. What would be the root cause @k4str042 – Shashank Sood Jan 09 '23 at 11:22

score 13 · Answer 6 · answered Jan 22 '20 at 22:12

13

Delete the publish profile you created and create a new one. The wizard will put in the correct targetframe work for you and publish again. It should solve the problem.

answered Jan 22 '20 at 22:12

Eyad

201
1
3
5

This is absolutely the "best" answer for most circumstances. – paulsm4 Oct 09 '22 at 18:34

score 5 · Answer 7 · answered Feb 09 '21 at 10:54

5

If your build script starts with a dotnet restore and ends with a dotnet publish --no-restore, you must make sure that they both include the same --runtime parameter.

answered Feb 09 '21 at 10:54

9Rune5

373
1
4
16

This was actually my problem on GitHub Actions – cmxl Dec 09 '22 at 19:03

Jamshaid K. · Answer 8 · 2023-08-14T20:39:16.783

5

For me it was the happening because I had migrated my project from .net5.0 to .net6.0 and the problem was caused when I was publishing the project while debugging worked fine.

Checking the publishing profile showed that it had a configuration for .net5.0 in it:

Changing the existing .net core version with the desired one resolved the issue:

Or you can directly change it by going into the publishing profile `.pubxml` file under `Properties > PublishingProfiles` directory.

edited Aug 14 '23 at 20:39

answered Jun 02 '22 at 08:43

Jamshaid K.

3,555
1
27
42

Same for me. Upvoting. – James Harcourt Sep 27 '22 at 10:27
This happened for me after upgrading from .NET 6 to 7. I restarted Visual Studio per a popular answer, but I bet I didn't need to. I saw the dropdown saying "6" the next time I went to Publish. Changed it to 7 and success. – StackOverflowUser Nov 25 '22 at 09:43

score 4 · Answer 9 · answered Dec 12 '19 at 11:42

4

Restarting Visual Studio or unloading/reloading the project didn't work for me, but deleting the "obj" folder and then rebuilding seems to have fixed the issue.

answered Dec 12 '19 at 11:42

Dion V.

2,090
2
14
24

score 4 · Answer 10 · answered Mar 12 '21 at 09:03

I got this error when upgrading a web project from netcoreapp3.1 to net5.0.

One of the answers here pointed me in the right direction:

The publish profile still had netcoreapp3.1 as target framework. Edited the publish profile and changed target framework to net5.0 and it worked.

(Visual Studio 16.8)

score 3 · Answer 11 · answered Aug 20 '19 at 15:37

For me the problem ended up being that one of my NuGet feeds was down, so a package was not getting updated properly. It wasn't until I ran a NuGet package restore directly on the solution that I saw any error messages related to my NuGet feed being down.

score 3 · Answer 12 · answered Dec 04 '20 at 15:59

You should try all the other solutions here first. Failing that you can try what eventually unblocked me when none of these did. I ran into this problem when porting a Jenkins build to an Azure DevOps pipeline on a pool of agents. It took about 60 builds before I tried every other possibility. I found out that needed to do two things:

Ensure the tooling was consistent for this specific project
Use a nuget restore friendly with the version of MSBuild used after finding out that mattered yet I couldn't use the proposed workaround for just updated nuget tooling.

The versions I needed to use are likely different than yours.

1:

call choco install windows-adk-all --version=10.0.15063.0 --force

call choco install windows-sdk-10.1 --version=10.1.15063.468 --force

2:

call MSBuild -t:restore Solution.sln

call MSBuild Solution.sln /t:rebuild;pack /p:Configuration=Release /p:Platform="Any CPU"

Sadly, the hyperlink here is the explanation that all of the other "upgrade XYZ" answers lacked. — JdeBP, Nov 06 '21 at 03:45

score 2 · Answer 13 · answered Nov 11 '20 at 10:18

2

To me, the error was caused because of an existing global.json file in the solution level folder, pointing to a different .NET version. Removing that file (or changing its SDK version) resolved the problem

answered Nov 11 '20 at 10:18

Shimmy Weitzhandler

101,809
122
424
632

We added a file 'global.json' and specified version as { "sdk": { "version": "2.1.509", "rollForward": "latestFeature" } } – Vsh Feb 16 '21 at 05:24

score 2 · Answer 14 · answered Nov 26 '20 at 11:36

2

Upgrading NuGet version from 5.5.1 to 5.8.0 fixed the issue.

answered Nov 26 '20 at 11:36

ak_01

61
1
3

How did you find out it's required. What would be the root cause @ak_01 – Shashank Sood Jan 09 '23 at 11:19

score 2 · Answer 15 · edited Jan 30 '21 at 14:30

I had similar issue, when I installed a new sdk version.

Exception was:

Severity Code Description Project File Line Suppression State Error NETSDK1005
Assets file '.. \RazorPages\obj\project.assets.json' doesn't have a target for 
'netcoreapp3.1'. Ensure that restore has run and that you have included 'netcoreapp3.1' 
in the TargetFrameworks for your project. RazorPages 
C:\Program Files\dotnet\sdk\5.0.102\Sdks\Microsoft.NET.Sdk
\targets\Microsoft.PackageDependencyResolution.targets    241

Solution was to select again the target version of the project.

right click on solution
Properties\Application Tab
Change Target framework version to something different and change it back.

The error happened to me because I mistakenly compiled the solution in an old VS version, which restored odd dependencies. This answer solved the problem to me. — Cesar, Mar 20 '21 at 15:08

score 2 · Answer 16 · answered Sep 21 '22 at 07:47

2

Running dotnet restore --packages .nuget in the project directory fixed the issues for me.

answered Sep 21 '22 at 07:47

steven01804

335
2
13

score 1 · Answer 17 · answered Oct 20 '20 at 17:34

A colleague ran into this after upgrading an application from dotnet core 1.1 to dotnet core 2.1. He properly updated all the targetFramework references within the various csproj files, and had no issues on his local development machine. However, we run Azure DevOps Server and build agents on-premises, so the build agent was reporting this error after a pull request build was executed.

The dotnet clean task was throwing an error because of the new targeted framework. dotnet clean uses the same targets as build, publish, etc, so after a change in target frameworks the dotnet restore must happen before the dotnet clean to update the dependent files. In hindsight this makes sense because you want to restore dependencies to the proper target framework before you do any building or deploying.

This may only affect projects with upgraded target frameworks but I have not tested it.

score 1 · Answer 18 · answered Dec 29 '20 at 21:45

1

Receiving similar error for 'netcoreapp3.1' when building using command line. It turned out to be an MsBuild switch that caused the issue. Specifically speaking:

/p:TargetFramework="netcoreapp3.1"

Removed the switch and the error was fixed.

answered Dec 29 '20 at 21:45

Hamed

279
1
3
13

score 1 · Answer 19 · answered Sep 20 '22 at 08:32

1

I upgraded from netstandard to net6.0, when publishing had to change TargetFramework to net6.0

answered Sep 20 '22 at 08:32

Sergio Solorzano

476
9
29

score 0 · Answer 20 · answered Apr 20 '21 at 14:30

0

In my case updating visual studio 2019 to the latest version, fixed the issue.

answered Apr 20 '21 at 14:30

TheLoneWolf91193

415
7
19

score 0 · Answer 21 · edited Feb 16 '22 at 07:41

In my case, if you have TargetFrameworks and TargetFramework together in the csrpoj file, remove TargetFramework will solve the problem.

edit it from:

<Project Sdk="Microsoft.NET.Sdk">
    <PropertyGroup>
        <TargetFrameworks>netstandard2.0;net461;</TargetFrameworks>
        <TargetFramework>net461</TargetFramework><!--remove this line-->
    </PropertyGroup>
</Project>

to

<Project Sdk="Microsoft.NET.Sdk">
    <PropertyGroup>
        <TargetFrameworks>netstandard2.0;net461;</TargetFrameworks>
    </PropertyGroup>
</Project>

score 0 · Answer 22 · answered Apr 06 '22 at 18:03

0

From my experience if you have dependencies in your solution built using "ProjectSection(ProjectDependencies) = postProject" then in this case dotnet build goes nuts.

answered Apr 06 '22 at 18:03

Viacheslav Mikhaylov

1
1

willbush · Answer 23 · 2022-05-19T04:38:30.023

I ran into the NETSDK1047 when playing around with Docker in a brand new dotnet project created using dotnet new worker and the docker file from dotnet-docker samples.

❯ docker build -t dockertest .

output elided...

/usr/share/dotnet/sdk/6.0.300/Sdks/Microsoft.NET.Sdk/targets/Microsoft.PackageDependencyResolution.targets(267,5): error NETSDK1047: Assets file '/source/obj/project.assets.json' doesn't have a target for 'net6.0/linux-musl-x64'. Ensure that restore has run and that you have included 'net6.0' in the TargetFrameworks for your project. You may also need to include 'linux-musl-x64' in your project's RuntimeIdentifiers. [/source/dockertest.csproj]
The command '/bin/sh -c dotnet publish -c release -o /app -r linux-musl-x64 --self-contained true --no-restore /p:PublishTrimmed=true /p:PublishReadyToRun=true /p:PublishSingleFile=true' returned a non-zero code: 1
dockertest on  main [✘] via .NET v6.0.202  net6.0
❯

The issue was because I forgot to add a .dockerignore file ignoring the bin and obj directories.

I only realized why because I tried different Dockerfiles from the dotnet-docker repo and got a different error which has this same resolution. I'll try to make a PR to the docs of NETSDK1047 to add this resolution. edit: link to PR https://github.com/dotnet/docs/pull/29530

score 0 · Answer 24 · edited Jun 19 '22 at 21:37

0

Had the same problem, for me it was that I had a space before my TargetFramework

<TargetFramework> net6.0</TargetFramework>

edited Jun 19 '22 at 21:37

Lee Taylor

7,761
16
33
49

answered Jun 17 '22 at 13:35

antca230

56
4

score 0 · Answer 25 · answered Dec 06 '22 at 15:42

On my end I had this issue with net6.0 at build time, even before trying to publish. Even if everything was pointing to csproj and it had all the right TargetFramework, the issue was that our repo had a Nuget.Config at it's root and it included a configuration for a local disk Nuget Repo of another programmer. I disabled the Nuget.Config file and I was able to build the project. It was probably unable to restore the Nuget Packages but the error message was misleading.

score -1 · Answer 26 · answered Feb 16 '23 at 05:07

-1

clean cache and restart VS then it worked for me.

answered Feb 16 '23 at 05:07

Saige Zhang

737
1
7
18

Assets file obj\project.assets.json doesn't have a target - VS2017

26 Answers26