Rename manifest extension to `.dscresource.json` about dsc HOT 3 CLOSED

That's a fair point. The other option is to just have .dsc.yaml and .dsc.json for everything and rely on the $schema, but that means every file needs to be opened and read instead of just relying on the extension. So let's go with .dsc.resource.json for now.

from dsc.

foo.bar.baz.dscresource.json makes the dscresource segment slightly difficult to read - is it worth using .dsc.resource.json instead, possibly as a companion to getting authoring tools to recognize .dsc.config.yaml as a DSC Configuration file (without having to tell the tooling that this specific yaml file is a DSC Configuration)?

from dsc.

This also reminds me, can people author their manifests in YAML, or only in JSON? Should foo.dsc.resource.yaml be a valid manifest file?

from dsc.