dotnet build doesn't compile with 2.0.0-preview2-final for MVC template #8426

vRITHNER · 2017-06-20T12:08:25Z

Steps to reproduce

Add new project from VS (mvc --auth Individual):

Build
Build 100%

Do the same from shell command:

dotnet new mvc --auth Individual
dotnet build

Expected behavior

build

Actual behavior

error NU1003: PackageTargetFallback and AssetTargetFallback cannot be used together. Remove PackageTargetFallback(deprecated) references from the project environment.

Environment data

    <PackageReference Include="Microsoft.AspNetCore.All" Version="2.0.0-preview2-final" />
    <PackageReference Include="Microsoft.EntityFrameworkCore.Tools" Version="2.0.0-preview2-final" PrivateAssets="All" />
    <PackageReference Include="Microsoft.VisualStudio.Web.CodeGeneration.Design" Version="2.0.0-preview2-final" PrivateAssets="All" />

dotnet --info output:

 Version:            2.0.0-preview2-006470
 Commit SHA-1 hash:  4ea3671bbd

Runtime Environment:
 OS Name:     Windows
 OS Version:  10.0.16215
 OS Platform: Windows
 RID:         win10-x64
 Base Path:   C:\Program Files\dotnet\sdk\2.0.0-preview2-006470\

Microsoft .NET Core Shared Framework Host

  Version  : 2.0.0-preview2-25407-01
  Build    : 40c565230930ead58a50719c0ec799df77bddee9

The text was updated successfully, but these errors were encountered:

livarcocc · 2017-06-20T16:46:36Z

This has been fixed in the latest preview2 build.

vRITHNER · 2017-06-21T15:04:56Z

Looks like it's not the same story between VS latest and dotNet/CLI latest (2.0.0-preview2-006497);

from CLI:
dotnet new mvc --auth Individual -uld

The template "ASP.NET Core Web App (Model-View-Controller)" was created successfully.
This template contains technologies from parties other than Microsoft, see https://aka.ms/template-3pn for details.

Processing post-creation actions...
Running 'dotnet restore' on D:\Temp\IdTest7\IdTest7.csproj...
Restoring packages for D:\Temp\IdTest7\IdTest7.csproj...
Restore completed in 42.09 ms for D:\Temp\IdTest7\IdTest7.csproj.
Restore completed in 42.21 ms for D:\Temp\IdTest7\IdTest7.csproj.
Restore completed in 49.63 ms for D:\Temp\IdTest7\IdTest7.csproj.
D:\Temp\IdTest7\IdTest7.csproj : warning NU1701: Package 'Microsoft.Composition 1.0.27' was restored using '.NETPortable,Version=v0.0,Profile=Profile259, .NETFramework,Version=v4.6.1' instead the project target framework '.NETCoreApp,Version=v2.0'. This may cause compatibility problems.
D:\Temp\IdTest7\IdTest7.csproj : warning NU1701: Package 'SQLitePCLRaw.lib.e_sqlite3.linux 1.1.5' was restored using '.NETPortable,Version=v0.0,Profile=Profile259, .NETFramework,Version=v4.6.1' instead the project target framework '.NETCoreApp,Version=v2.0'. This may cause compatibility problems.
D:\Temp\IdTest7\IdTest7.csproj : warning NU1701: Package 'SQLitePCLRaw.lib.e_sqlite3.osx 1.1.5' was restored using '.NETPortable,Version=v0.0,Profile=Profile259, .NETFramework,Version=v4.6.1' instead the project target framework '.NETCoreApp,Version=v2.0'. This may cause compatibility problems.
D:\Temp\IdTest7\IdTest7.csproj : warning NU1701: Package 'SQLitePCLRaw.lib.e_sqlite3.v110_xp 1.1.5' was restored using '.NETPortable,Version=v0.0,Profile=Profile259, .NETFramework,Version=v4.6.1' instead the project target framework '.NETCoreApp,Version=v2.0'. This may cause compatibility problems.
Generating MSBuild file D:\Temp\IdTest7\obj\IdTest7.csproj.nuget.g.props.
Generating MSBuild file D:\Temp\IdTest7\obj\IdTest7.csproj.nuget.g.targets.
Restore completed in 2.69 sec for D:\Temp\IdTest7\IdTest7.csproj.

At least the build is successful.

From VS (latest 15.3.0 Preview 2.1), new project to create the same type of project:
I can't compile it

txs
-Vince

vRITHNER · 2017-06-21T15:08:03Z

if I change back the line in Csproj

<AssetTargetFallback>$(AssetTargetFallback);portable-net45+win8+wp8+wpa81;</AssetTargetFallback>

to

<PackageTargetFallback>$(PackageTargetFallback);portable-net45+win8+wp8+wpa81;</PackageTargetFallback>

VS compile but not DotNet cli

andrewlock · 2017-06-28T19:40:52Z

I can reproduce this too, when running dotnet new mvc --auth Individual -uld

Tealons · 2017-06-30T08:55:01Z

I have the same problem with 2.0.0-preview2-006497.

@livarcocc : Can you reopen this issue? Is seems to be back...

livarcocc · 2017-06-30T17:23:08Z

@mlorbetske @balachir can you guys take a look at this?

mlorbetske · 2017-06-30T19:04:58Z

I think this is because the change to support AssetTargetFallback came in 15.3 Preview 3, so updating VS to the very latest preview again should work.

andrewlock · 2017-07-01T11:56:14Z

I'm only compiling via the command line (I haven't installed VS) and I see the restore warnings, namely

warning NU1701: Package 'Microsoft.Composition 1.0.27' was restored using '.NETPortable,Version=v0.0,Profile=Profile259, .NETFramework,Version=v4.6.1' instead the project target framework '.NETCoreApp,Version=v2.0'. This may cause compatibility problems.

I assume dotnet build doesn't have a dependency on the VS version?

WestDiscGolf · 2017-07-19T18:35:00Z

I'm getting a very similar error ...

Warning NU1701 Package 'Microsoft.Composition 1.0.27' was restored using '.NETFramework,Version=v4.6.1' instead of the project target framework '.NETCoreApp,Version=v2.0'. This may cause compatibility problems. BackEnd

And I'm trying to run through @jongalloway conference workshop examples from - https://github.com/jongalloway/aspnetcore-app-workshop/blob/master/docs/2.%20Build%20out%20BackEnd%20and%20Refactor.md - and I'm up to "Add a new database migration" and it won't build.

I've tried updating the package references:

   <ItemGroup>
     <PackageReference Include="Microsoft.AspNetCore.All" Version="2.0.0-preview2-final" />
     <PackageReference Include="Microsoft.EntityFrameworkCore.Tools.DotNet" Version="2.0.0-preview2-final" />
     <PackageReference Include="Microsoft.VisualStudio.Web.CodeGeneration.Design" Version="2.0.0-preview2-final" />
     <PackageReference Include="Swashbuckle.AspNetCore" Version="1.0.0" />
   </ItemGroup>

and the cli tools references ...

 <ItemGroup>
    <DotNetCliToolReference Include="Microsoft.VisualStudio.Web.CodeGeneration.Tools" Version="2.0.0-preview2-final" />
    <DotNetCliToolReference Include="Microsoft.EntityFrameworkCore.Tools.DotNet" Version="2.0.0-preview2-final" />
  </ItemGroup>

Have I missed something?

Running dotnet run or dotnet restore on the command line I get ...

error NU1003: PackageTargetFallback and AssetTargetFallback cannot be used together. Remove PackageTargetFallback(deprecated) references from the project environment.

livarcocc · 2017-07-19T18:41:25Z

@WestDiscGolf we have updated the SDK to have an implicit AssetTargetFallback to net461. Your project probably has a PackageTargetFallback property and the two are mutually excluding, like the error message suggests.

So, you can either update your project and replace PackageTargetFallback with AssetTargetFallback, or you can disable the implicit ATF by setting DisableImplicitAssetTargetFallback to true in your project.

WestDiscGolf · 2017-07-19T19:57:34Z

@livarcocc Thanks for the speedy response. On replacing PackageTargetFallback with AssetTargetFallback I get, in yellow in powershell, the following:

PS C:\Users\Adam\Documents\Visual Studio 2017\Projects\Workshop\BackEnd> dotnet run
C:\Users\Adam\Documents\Visual Studio 2017\Projects\Workshop\BackEnd\BackEnd.csproj : warning NU1701: Package 'Microsoft.Composition 1.0.27' was restored using '.NETPortable,Version=v0.0,Profile=Profile7, .NETFramework,Version=v4.6.1' instead the project target framework '.NETCoreApp,Version=v2.0'. This may cause compatibility problems.
C:\Users\Adam\Documents\Visual Studio 2017\Projects\Workshop\BackEnd\BackEnd.csproj : warning NU1701: Package 'Microsoft.Composition 1.0.27' was restored using '.NETPortable,Version=v0.0,Profile=Profile7, .NETFramework,Version=v4.6.1' instead the project target framework '.NETCoreApp,Version=v2.0'. This may cause compatibility problems.

Adding in the DIATF node in the csproj file it fails with:

error NU1202: Package Microsoft.Composition 1.0.27 is not compatible with netcoreapp2.0 (.NETCoreApp,Version=v2.0). Package Microsoft.Composition 1.0.27 supports: portable-net45+win8+wp8+wpa81 (.NETPortable,Version=v0.0,Profile=Profile259)

The build failed. Please fix the build errors and run again.

Is that right? Should there still be a warning?

This is all new to me so apologies if these are stupid questions / issues.

livarcocc · 2017-07-19T20:44:46Z

The warning is expected, though in the latest versions of asp.net I believe we have moved to no longer depend on that package. So, in newer versions, the warning should not appear.

WestDiscGolf · 2017-07-19T21:04:56Z

@livarcocc Cool, thanks for letting me know!

benaadams · 2017-07-25T14:24:38Z

This causing the issue I'm seeing when trying to build coreclr (also corefx)? https://github.com/dotnet/coreclr/issues/13025

livarcocc · 2017-07-25T16:22:51Z

@benaadams You need to choose either ATF or PTF. I explained it above.

benaadams · 2017-07-25T16:32:30Z

@livarcocc not entirely sure what .\build does when compiling coreclr/corefx; its a wild ride, will see if I can work out what needs changing

benaadams · 2017-07-25T16:38:14Z

Think its the buildtools have filed issue dotnet/buildtools#1617

rrelyea · 2017-09-25T20:51:51Z

Helping search engines find the right content: https://docs.microsoft.com/en-us/nuget/reference/errors-and-warnings#nu1003

livarcocc closed this as completed Jun 20, 2017

msftgits transferred this issue from dotnet/cli Jan 31, 2020

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

dotnet build doesn't compile with 2.0.0-preview2-final for MVC template #8426

dotnet build doesn't compile with 2.0.0-preview2-final for MVC template #8426

vRITHNER commented Jun 20, 2017

livarcocc commented Jun 20, 2017

vRITHNER commented Jun 21, 2017

vRITHNER commented Jun 21, 2017

andrewlock commented Jun 28, 2017

Tealons commented Jun 30, 2017

livarcocc commented Jun 30, 2017

mlorbetske commented Jun 30, 2017

andrewlock commented Jul 1, 2017

WestDiscGolf commented Jul 19, 2017

livarcocc commented Jul 19, 2017

WestDiscGolf commented Jul 19, 2017

livarcocc commented Jul 19, 2017

WestDiscGolf commented Jul 19, 2017

benaadams commented Jul 25, 2017

livarcocc commented Jul 25, 2017

benaadams commented Jul 25, 2017

benaadams commented Jul 25, 2017

rrelyea commented Sep 25, 2017

dotnet build doesn't compile with 2.0.0-preview2-final for MVC template #8426

dotnet build doesn't compile with 2.0.0-preview2-final for MVC template #8426

Comments

vRITHNER commented Jun 20, 2017

Steps to reproduce

Expected behavior

Actual behavior

Environment data

livarcocc commented Jun 20, 2017

vRITHNER commented Jun 21, 2017

vRITHNER commented Jun 21, 2017

andrewlock commented Jun 28, 2017

Tealons commented Jun 30, 2017

livarcocc commented Jun 30, 2017

mlorbetske commented Jun 30, 2017

andrewlock commented Jul 1, 2017

WestDiscGolf commented Jul 19, 2017

livarcocc commented Jul 19, 2017

WestDiscGolf commented Jul 19, 2017

livarcocc commented Jul 19, 2017

WestDiscGolf commented Jul 19, 2017

benaadams commented Jul 25, 2017

livarcocc commented Jul 25, 2017

benaadams commented Jul 25, 2017

benaadams commented Jul 25, 2017

rrelyea commented Sep 25, 2017