Expose project build configuration in scripts section of project.json

[troydai]

There are a few variables surfaced in the scripts section of project.json. However, the current build configuration is not among them.

The variable is useful in such a scenario: copying the output to a folder other than default output

{
  "scripts":{
    "postbuild": [
      "xcopy /F /Y /I bin\\%project:BuildConfiguration%\\* C:\\Playground"
    ]
  }
}

It worth to mention that kpm build support multiple configurations in one build run. If this variable is exposed, the scripts need to be executed multiple times to match each configuration.

[borgdylan]

👍

[dougbu]

kpm build support[s] multiple configurations in one build run

should add at least a prebuild.perconfiguration (sample name) script since prebuild is executed just once and repeating it may mess up other uses. also recommend adding prebuild.perframework which would execute once per configuration : target framework pair.

I'll send a PR out containing this fix shortly.

[Eilon]

In the design meeting we need to discuss whether doing #2450 would eliminate or at least alleviate the need for the feature in this issue.

[glennc]

Will run the *build *pack method per configuration and pass the configuration in.

[victorhurdugaci]

Assigning to Pawel because he needs this to unblock his other change

[apawsey]

Hi guys,

Can we actually run a different script depending on build configuration or architecture now then? If so how?

Thanks.