Bad Error message for wildcard usage in directories

Jun 9, 2011 at 2:53 PM

In a nuspec file if you have the files section defined as:

<files>
  <file src="bin\*\*.pdb" target="lib" />
</files>

Executing a pack results in the extremely unhelpful message of: "Illegal characters in path."

This message really should return something along the lines of "* detected in path location, * wildcard is for filenames, ** wildcard for path locations"


On a separate note, why does this even matter? What benefit do we gain by having this differentiation? I think this just makes it harder to work with. Atleast if the error message is fixed everyone will get the error message and know to use the ** but that goes back to my question here, if you have to learn it from the error message is it helpful?

Developer
Jun 9, 2011 at 5:11 PM
This discussion has been copied to a work item. Click here to go to the work item and continue the discussion.