Similarly I would like to see a schema for nuget.config

Things we need to do:

1. Figure out if we can ship the schema inside the nuget vsix (as we are moving away from msi going forward)
2. Generate the schema files and test them.

A schema for *.nuspec would be a good idea as well - @xavierdecoster has a package with an older XSD for NuSpec at: https://www.nuget.org/packages/NuGet.Manifest.Schema -- perhaps we can build off of this and install the content as part of the VSIX

I'm putting together 2 schemas - packages.config and updating the nuspec schema from the NuGet.Manifest.Schema package.

This is not a schema problem as such because it only happens if the file happens to be open. This is like only reporting errors in C# files that happen to be open rather than any errors in the project. This is why I consider such messages as a spurious byproduct of search opening up the XML file.

(Would be nice if the standard search had an option to not search such files)

@emgarten give me the link to the schema for package.config. I'll link to it from docs.

I know the nuspec schema is here https://github.com/NuGet/NuGet.Client/blob/dev/src/NuGet.Core/NuGet.Packaging/compiler/resources/nuspec.xsd

@karann-msft, I found couple of results elsewhere on GitHub:

https://github.com/search?q=extension%3Axsd+targetFramework+allowedVersions&type=Code
https://github.com/search?q=filename%3Apackages.xsd+targetFramework+allowedVersions&type=Code

not sure which one is most complete.

@karann-msft I don't think there is an xsd in the nuget or nuget2 codebase, I'm not finding it anyways.

One would need to be created. I'm not sure further work like this for packages.config would be useful however, users should move to PackageReference.