使用'.NETFramework，Version = v4.6.1'而不是项目目标框架'.NETCoreApp，Version = v2.0'恢复了软件包'Faker.Net 1.0.3'

Question

I'm new to .NET core tools and just ran into an issue while running the following command; I can see that it's just a warning but it's not creating the "publish" folder even with " sudo dotnet publish -o /publish "

dotnet publish -o /publish

As you can see there's no publish folders

/home/joel/workspace/asp (copy)/api/api.csproj : 
        warning NU1701: Package 'Faker.Net 1.0.3' was restored using '.NETFramework,
    Version=v4.6.1' 
    instead of the project target framework '.NETCoreApp,Version=v2.0'. 
This package may not be fully compatible with your project.

            Microsoft (R) Build Engine version 15.4.8.50001 for .NET Core
            Copyright (C) Microsoft Corporation. All rights reserved.

            /home/joel/workspace/asp (copy)/api/api.csproj :
         warning NU1701: Package 'Faker.Net 1.0.3' was restored using '.NETFramework,
    Version=v4.6.1' 
    instead of the project target framework '.NETCoreApp,Version=v2.0'. 
    This package may not be fully compatible with your project.
              api -> /home/joel/workspace/asp (copy)/api/bin/Debug/netcoreapp2.0/api.dll
            /usr/share/dotnet/sdk/2.0.2/Sdks/Microsoft.NET.Sdk/build/Microsoft.NET
        .Publish.targets(67,5): 
        error MSB3191: Unable to create directory "/publish2/". 
Access to the path '/publish2/' is denied. [/home/joel/workspace/asp (copy)/api/api.csproj]

Answer 1

The warning shown has nothing to do with the publish problem. It just states that Faker.Net 1.0.3 targets .NET Framework and have been resolved for that target runtime despite the application will be running on .NET Core. That is possible due to .NET Standard shim, however that library might be not fully compatible with .NET Core, so you'd rather check its compatibility with .NET Portable Analizer

Now the actual problem is the directory you are writing the output to is restricted for access. Thus to make it work you should get the privilege first.

try dotnet publish -o ./publish2 (note the dot before the path)