This project is read-only.


Validate nuget.config files when using them


Cfr this stackoverflow question:

Helped out a MyGet customer using TFSOnline and a secured NuGet feed + package restore.
Turns out there was a simple typo in the solution-level nuget.config file:

<packageSource> versus <packageSources>

VERY easily overlooked, and apparently no validation happens on the nuget.config file when using it during restore. Wasted quite some time on a silently ignored validation error in the nuget.config file. It'd be nice to warn the user about this in the logs (or ship the nuget.config xsd with package restore for VS intellisense?).
Closed Jun 25, 2013 at 7:22 PM by dotnetjunky


dotnetjunky wrote Jun 25, 2013 at 7:22 PM

By design. We want to avoid validating nuget.config file so that it can be extended in future versions and still can be backwards compatible.

XavierDecoster wrote Jun 25, 2013 at 8:31 PM

How does shipping config validation with the client tools break backwards compatibility?
Or are you referring to forward compatibility (e.g. nuget.exe v2.5 validation fails against v3.0 nuget.config file)? If the validation generates warnings and not errors, what does it break? Worst case, it tells you to upgrade your client tools :)