-
Notifications
You must be signed in to change notification settings - Fork 392
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Transitive package references not followed #1036
Comments
I can't reproduce this with a file new project in VS 2017 RC2 |
@davidfowl Sorry I didn't get back to you earlier. I just created a brand-new project (
I will try updating my version of the CLI and get back to you if anything changes. |
Closing this issue since the original transitive refs issue doesn't repro anymore. |
Please forgive me if this is a duplicate of something, or is filed in the wrong place; I have read several issues regarding reference handling errors and was not certain which most closely matches my symptoms.
Here is what I did to trigger this bug:
dotnet new
, thendotnet restore
. I have modified the default csproj format slightly, to fit with the requirements and quirks of my larger project. In case this affects how it is parsed by Visual Studio, I have pasted the entire csproj file from my end below.Program.cs
file within the project.Console.WriteLine()
in the example hello-world C# file does not parse properly. It tells me that "The name 'Console' does not exist in the current context." I am (supposedly) transitively referencingSystem.Console.dll
throughMicrosoft.NETCore.App
. However, this doesn't actually seem to be the case. Building usingdotnet build
at the command line also fails with the same error.It is my understanding that referencing
Microsoft.NETCore.App
should also reference the appropriate DLLs from all the packages visible on the NuGet gallery. Unfortunately, this doesn't seem to be the case. If I add a<PackageReference>
tag pointing toSystem.Console
directly, then the issue goes away. Unfortunately, when I try that I run afoul of the problem described in my comment on #785. While transitive project references are not currently implemented (cf #199), this behavior concerning transitive package references seems to be caused by a different issue.Here is the contents of the csproj file (slightly commented for readability):
The text was updated successfully, but these errors were encountered: