Update NU1100.md

[waldyd]

NU1100 may also be caused by the lack of a NuGet configuration file

[opbld32]

Docs Build status updates of commit b111b96:

✅ Validation status: passed

File	Status	Preview URL	Details
docs/reference/errors-and-warnings/NU1100.md	✅Succeeded	View

For more details, please refer to the build report.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

For any questions, please:

• Try searching the docs.microsoft.com contributor guides
• Post your question in the Docs support channel

[JonDouglas]

Thank you kindly for the contribution!

[nkolev92]

NuGet would normally be creating the user-wide configuration file if it doesn't already exist.

Can you elaborate how you hit this?

[waldyd]

The issue can be reproduced by: 1. Installing .NET Core 2. Installing VS Code 3. dotnet new mvc 4. dotnet build. On systems without NuGet (or tools that install it, i.e. Visual Studio). .NET app building will trigger this issue. Thanks.

…

On 2/08/2022, at 2:04 PM, Nikolche Kolev ***@***.***> wrote:  @nkolev92 commented on this pull request. In docs/reference/errors-and-warnings/NU1100.md: > @@ -17,11 +17,16 @@ f1_keywords: <pre>Unable to resolve 'Dependency (>= 1.0.0)' for 'TargetFramework'</pre> ### Issue -A dependency could not be resolved. This is a generic issue for types that are not packages or projects. +A dependency could not be resolved. This is a generic issue for types that are not packages or projects. + +This issue may also be caused by the lack of a NuGet configuration file. NuGet would normally be creating the user-wide configuration file if it doesn't already exist. Can you elaborate how you hit this? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.

[nkolev92]

@JonDouglas I think we merged prematurely here.

I think we need to confirm this repro first, as it doesn't really make sense to me immediately.

[JonDouglas]

@nkolev92 A simple reproduction is to remove the contents of a nuget.config file as if it were "empty". i.e. leave only the xml & configuration tags.

I repro'd it and the contribution here is helpful as the first scenario asks to check if dependencies exist on package sources, but the reality is the config may be generated by other tooling causing issues and one may want to check the config for accuracy.

This is similar to the problem of other nuget-powered tooling generating an empty config and the user has no idea how to resolve it.

[nkolev92]

A simple reproduction is to remove the contents of a nuget.config file as if it were "empty". i.e. leave only the xml & configuration tags.

That's not what the update says. It talks about a missing nuget.config, which is different.

[JonDouglas]

@nkolev92 The assumption here is that there exists no config in the project/solution and the error is thrown because the user-level is problematic (i.e. empty from other tooling or similar).

using the dotnet new nugetconfig generates a proper configuration at the project level that will override the user-level and thus works.

Perhaps the language we want to instill here is fixing these items at the user-level or inspecting the various configs to ensure the sources exist in the first place?

I still think the contribution is fine as is, but we can improve more later.

That is my understanding and reproduction of the issue however!

[nkolev92]

I don't think we can say missing config because a missing config altogether causes NuGet to create one.
It is a critical onboarding experience.

The context with which it gets created is irrelevant imo.
The docs shouldn't contradict the actual tool behavior even if it's not the most user friendly description.

Perhaps the language we want to instill here is fixing these items at the user-level or inspecting the various configs to ensure the sources exist in the first place?

I'll take a crack at updating this and create a PR. I think it'll be easier to make progress that way :D

[JonDouglas]

@waldyd As one last question, can you let us know the contents of your user config?

https://docs.microsoft.com/nuget/consume-packages/configuring-nuget-behavior#config-file-locations-and-uses

[nkolev92]

Hoping the following version improves clarity.

#2838.

[waldyd]

I did not have a nuget.config file at a user level neither at global level. When the issue arose I had to create it at project level by issuing dotnet new nugetconfig.

…

On 3/08/2022, at 1:11 PM, Jon Douglas ***@***.***> wrote:  @waldyd As one last question, can you let us know the contents of your user config? https://docs.microsoft.com/nuget/consume-packages/configuring-nuget-behavior#config-file-locations-and-uses — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.

[nkolev92]

NuGet creates a settings file if there's none.
That's the onboarding experience when you install new tools. There's no other component that creates a config file by default other than NuGet.

cc @v-luzh

Can you please try to repro this?

Start off with a new windows machine and follow the steps here:

#2829 (comment)