You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 23, 2021. It is now read-only.
Content/README.txt and tools/install.ps1 are just placeholders with any content
Run dotnet pack with the 1.0.0-preview2 tooling, and inspect the generated NuGet package. Notice that the README.txt and install.ps1 are in the right place:
Delete global.json
Run dotnet migrate and dotnet restore
Run dotnet pack again.
Expected behavior
Package should be built exactly the same as it was with the old tooling
Actual behavior
Warning is thrown while packing:
warning : Issue found with package 'nugetbug'. [C:\temp\nugetbug\nugetbug.csproj]
warning : Issue: PowerShell file outside tools folder. [C:\temp\nugetbug\nugetbug.csproj]
warning : Description: The script file 'content\tools\install.ps1' is outside the 'tools' folder and hence will not be executed during installation of this package. [C:\temp\nugetbug\nugetbug.csproj]
warning : Solution: Move it into the 'tools' folder. [C:\temp\nugetbug\nugetbug.csproj]
warning : Issue: PowerShell file outside tools folder. [C:\temp\nugetbug\nugetbug.csproj]
warning : Description: The script file 'contentFiles\any\net40\tools\install.ps1' is outside the 'tools' folder and hence will not be executed during installation of this package. [C:\temp\nugetbug\nugetbug.csproj]
warning : Solution: Move it into the 'tools' folder. [C:\temp\nugetbug\nugetbug.csproj]
README.txt and install.ps1 are in the wrong place: content/Content/readme.txt and content/tools/install.ps1
This is due to an issue in the generated csproj file. The following segment is added to the file:
.NET Command Line Tools (1.0.0)
Product Information:
Version: 1.0.0
Commit SHA-1 hash: e53429feb4
Runtime Environment:
OS Name: Windows
OS Version: 10.0.16188
OS Platform: Windows
RID: win10-x64
Base Path: C:\Program Files\dotnet\sdk\1.0.0
* Upgrade to Visual Studio 2017 + csproj tooling
* Include workaround for NuGet/Home#4337 (explicitly specify version when restoring NuGet packages)
* Work around dotnet/cli-migrate#11
* Upgrade to .NET Core 1.1.x
* Remove VersionPrefix from all csproj files
* Legacy NuGet restore is no longer needed
* Disable CS1701 warning for sample projects
* Turns out we actually do need the legacy NuGet restore
* Use VS2017 AppVeyor image
* Remove project dependencies to work around NuGet/Home#5193 and NuGet/Home#4578
* Use MSBuild 15 on AppVeyor
* Enforce .NET Core tools 1.0.0 in global.json
* Use newer npm on AppVeyor (as a workaround for https://github.com/dotnet/cli/issues/6561 and dotnet/msbuild#406), and run correct test command
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
From @Daniel15 on May 8, 2017 5:39
Steps to reproduce
Repro project: nugetbug.zip
project.json:
global.json:
Content/README.txt
andtools/install.ps1
are just placeholders with any contentdotnet pack
with the1.0.0-preview2
tooling, and inspect the generated NuGet package. Notice that theREADME.txt
andinstall.ps1
are in the right place:global.json
dotnet migrate
anddotnet restore
dotnet pack
again.Expected behavior
Package should be built exactly the same as it was with the old tooling
Actual behavior
README.txt
andinstall.ps1
are in the wrong place:content/Content/readme.txt
andcontent/tools/install.ps1
This is due to an issue in the generated
csproj
file. The following segment is added to the file:However, it's missing the
PackagePath
to place the files in the right location. The correct XML looks like this, as per the documentation at https://docs.microsoft.com/en-us/nuget/schema/msbuild-targets#including-content-in-a-packageEnvironment data
dotnet --info
output:cc @blackdwarf and @livarcocc
Copied from original issue: dotnet/cli#6544
The text was updated successfully, but these errors were encountered: