Update: The issue seems to be tied to the version of Visual Studio and/or NuGet too, see below.
How to reproduce the problem
Add the NLog, NLog.Config and NLog.Schema packages to a .NET Core 2.1 Console Application project.
Expected behaviour
The XML and XSD files from NLog.Config and NLog.Schema are copied in the project root.
Actual behaviour
The files are not copied to the project root, instead they are somehow "virtually linked" there (there's no "link" at file system level) from the NuGet packages cache directories.
Why this is a problem
- The content of the files are shared between all projects using the packages: if I modify the XML in project A, project B will see the same changes since the physical file is the same.
- If the XML and the XSD are not besides each other, IntelliSense will not pick up the schema and won't provide any autocompletion.
The first problem is especially nasty since it affects every projects that is using the packages, and there's absolutely no warning about it.
Related issues
#2461, #2686, #2757
Maybe related to https://docs.microsoft.com/en-us/nuget/reference/migrate-packages-config-to-package-reference#package-compatibility-issues as suggested in #2757.
Platforms
- Visual Studio: Microsoft Visual Studio Professional 2017 Version 15.7.5
- ReSharper: JetBrains ReSharper Ultimate 2018.1.3 Build 112.0.20180626.160528
- Framework: .NET Core 2.1
- Target framework: netcoreapp2.1
- Project type: Console application
- Project SDK: Microsoft.NET.Sdk
Packages versions
- NLog: 4.5.7
- NLog.Config: 4.5.7
- NLog.Schema: 4.5.7
Screenshots
Installing the packages adds "virtual files":
The files are "linked" from the NuGet packages cache:
The packages have been added through PackageReference:
The files are not copied in the project root:
IntelliSense will not pick up the XSD schema, and the XML file is shared between every project:
(The XML file in the screenshot has not been yet modified in this project, yet its content is not the default one but the modified one from another project.)
Update: The issue seems to be tied to the version of Visual Studio and/or NuGet too, see below.
How to reproduce the problem
Add the NLog, NLog.Config and NLog.Schema packages to a .NET Core 2.1 Console Application project.
Expected behaviour
The XML and XSD files from NLog.Config and NLog.Schema are copied in the project root.
Actual behaviour
The files are not copied to the project root, instead they are somehow "virtually linked" there (there's no "link" at file system level) from the NuGet packages cache directories.
Why this is a problem
The first problem is especially nasty since it affects every projects that is using the packages, and there's absolutely no warning about it.
Related issues
#2461, #2686, #2757
Maybe related to https://docs.microsoft.com/en-us/nuget/reference/migrate-packages-config-to-package-reference#package-compatibility-issues as suggested in #2757.
Platforms
Packages versions
Screenshots
Installing the packages adds "virtual files":
The files are "linked" from the NuGet packages cache:
The packages have been added through PackageReference:
The files are not copied in the project root:
IntelliSense will not pick up the XSD schema, and the XML file is shared between every project:
(The XML file in the screenshot has not been yet modified in this project, yet its content is not the default one but the modified one from another project.)