get error Assets file 'obj\project.assets.json' doesn't have a target for '.NETCoreApp,Version=v2.2'

Question

I upgrade my MVC Core Project from 2.2 to 3.0 with microsoft

and change many recommended here: https://stackoverflow.com/

It works fine when run it in Local, but when I want publish in local folder I get this error :

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

Ii have 3 projects and all of them upgrade to MVC core 3.0 also upgrade all packages to 3.0 also remove object folder and bin folder and build projects again, close VS and open it again but the error stil exists.

UPDATE: mvc project csproj

<Project Sdk="Microsoft.NET.Sdk.Web">

<PropertyGroup>
  <TargetFramework>netcoreapp3.0</TargetFramework>   
</PropertyGroup>

<ItemGroup>
 <!--<PackageReference Include="Microsoft.AspNetCore.App" />-->
  <PackageReference Include="Microsoft.AspNetCore.Identity.UI" Version="3.0" 
 />      
   <PackageReference Include="Microsoft.VisualStudio.Web.CodeGeneration.Design" 
Version="3.0.0" />
</ItemGroup>

<ItemGroup>
  <Folder Include="Areas\Admin\Data\" />
  <Folder Include="Areas\Admin\Models\" />
 </ItemGroup>

<ItemGroup>
  <ProjectReference Include="..\project.Model\project.Model.csproj" />
  <ProjectReference Include="..\project.Repo\project.Repo.csproj" />
</ItemGroup>

</Project>

My project.Model.csproj

<Project Sdk="Microsoft.NET.Sdk">

<PropertyGroup>
  <TargetFramework>netcoreapp3.0</TargetFramework>  
</PropertyGroup>

<ItemGroup>
  <PackageReference 
Include="Microsoft.AspNetCore.Identity.EntityFrameworkCore" Version="3.0.0" />
<PackageReference Include="Microsoft.AspNetCore.Identity.UI" Version="3.0.0" />
<PackageReference Include="Microsoft.EntityFrameworkCore.Design" 
 Version="3.0.0">
  <PrivateAssets>all</PrivateAssets>
  <IncludeAssets>runtime; build; native; contentfiles; analyzers; 
   buildtransitive</IncludeAssets>
  </PackageReference>
  <PackageReference Include="Microsoft.EntityFrameworkCore.SqlServer" 
 Version="3.0.0" />
<PackageReference Include="Microsoft.EntityFrameworkCore.SqlServer.Design" 
 Version="1.1.6" />
<PackageReference Include="Microsoft.EntityFrameworkCore.Tools" 
 Version="3.0.0">
  <PrivateAssets>all</PrivateAssets>
  <IncludeAssets>runtime; build; native; contentfiles; analyzers; 
 buildtransitive</IncludeAssets>
 </PackageReference>
 </ItemGroup>

 </Project>

Can you post your csproj file content ?

Tony
– Tony

2019-11-14 00:18:11 +00:00
Commented Nov 14, 2019 at 0:18 — Tony
– Tony, Commented Nov 14, 2019 at 0:18
Update question and post my .csproj files

sunny
– sunny

2019-11-14 18:01:06 +00:00
Commented Nov 14, 2019 at 18:01 — sunny
– sunny, Commented Nov 14, 2019 at 18:01

Mike · Accepted Answer · 2020-06-03 11:57:25Z

11

In our case we had a very similar error when Publishing, after switching from netcoreapp30 to netcoreapp31 as the target Framework. We solved it by:

Closing Visual Studio
Deleting the file \obj\project.assets.json
Opening the solution again
Rebuild Solution

After that we were able to Publish the project fine.

answered Jun 3, 2020 at 11:57

Mike

1,90621 silver badges16 bronze badges

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

2 Comments

Daryl Over a year ago

This is very common for me when one branch is on a different version. When switching branches with different versions, deleting the obj folder and restarting VS resolves my issue.

pat capozzi Over a year ago

Thank god for SO. I had erased the json file but had not closed and opened the solution. So bizarre!

Jim Wilcox · Accepted Answer · 2019-11-22 21:03:28Z

7

Make sure your Publish Profile says netcoreapp3.0 for the TargetFramework.

answered Nov 22, 2019 at 21:03

Jim Wilcox

1,58316 silver badges39 bronze badges

2 Comments

kingrazor Over a year ago

This was my issue. I upgraded from .netcore 2.2 to 3 and my publish profile did not get updated. Even though the UI said that it was targeting .netcore 3.1, it was not. I went and looked at the .pubxml file and it still had .netcoreapp2.2 which was not reflected using the publish configuration UI.

Faraz Ahmed Over a year ago

@kingrazor mine issue is solved by your comment description

Pale Ale · Accepted Answer · 2020-01-17 20:11:00Z

4

In your Package Manager Console run the following command: dotnet restore SolutionName.sln

answered Jan 17, 2020 at 20:11

Pale Ale

4777 silver badges11 bronze badges

1 Comment

Jean-David Lanz Over a year ago

Worked great for me, thanks! Interestingly, the console raised an error message "MSBUILD : error MSB1009: Project file does not exist." (and keeps raising it) but the solution still builds fine after that.

pawan nepal · Accepted Answer · 2020-05-08 02:35:27Z

1

This happens usually when you upgrade the .net core version. The solution is to create new publish profile. Not edit, simple create new publish profile and target the new .net core version that you have upgraded.

answered May 8, 2020 at 2:35

pawan nepal

4973 silver badges10 bronze badges

1 Comment

SPDeveloper Over a year ago

I Had similar issue , Updating Publish profile settings to correct >net version solved the issue.

Peter Csala · Accepted Answer · 2021-07-26 07:05:49Z

1

If you are doing this in a lambda then make sure to update aws-lambda-tools-defaults.json and serverless.template files.

edited Jul 26, 2021 at 7:05

Peter Csala

23.7k16 gold badges51 silver badges96 bronze badges

answered Jul 23, 2021 at 20:54

Hemant Mulay

213 bronze badges

Comments

Adamy · Accepted Answer · 2021-08-02 05:08:29Z

0

If you run publish with the command line (dotnet publish), make sure you specified the correct framework with option "-f".

answered Aug 2, 2021 at 5:08

Adamy

2,8493 gold badges30 silver badges25 bronze badges

Collectives™ on Stack Overflow

get error Assets file 'obj\project.assets.json' doesn't have a target for '.NETCoreApp,Version=v2.2'

6 Answers 6

2 Comments

2 Comments

1 Comment

1 Comment

Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

6 Answers 6

2 Comments

2 Comments

1 Comment

1 Comment

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related