If module version is not specified, composite configurations fail to load
Version occurs in: WMF5 Production Preview
Previous versions? No.
In a composite configuration scenario, if one of the composite resources contains an import-dscresource statement, and multiple versions of the module are available, the resource fails to load unless a moduleversion is specified.
The resource works fine if there is only one version available on the machine in question, or a minimum version is specified.
This behavior is common to all DSC resources, if I understand your issue correctly. If there are multiple versions of a module installed on your authoring system, you must specify the version that you intend to use in your configuration.
What behavior are you expecting?
AdminMark Gray (Admin, Windows Server) commented
Totally get it, Justin. Thanks for the additional context.
I have filed a bug for this and we will take it into consideration.
Justin DynamicD commented
I would expect it to default to the latest version, possibly return a warning that multiple versions were detected and that version x.x.x was used.
Currently, you get no indication that it's even a version issue as the composite resource refuses to load at all so the error you get when trying to compile a mof is that it can't find said composite resource. It's only when you open it in ISE do you see the warning that it's expecting the version to be defined because multiple versions exist.
This could be a curve ball for anyone making their "first configuration" to have it randomly break the first time they play with "update-module"