MicrosoftWindows Sandbox has been great so far.
One aspect that would be nice is if it was possible to map 'some' environment variables from the host machine into the sandbox.
I'm thinking that the interface for this would be to expose another set of elements <MappedEnvVariables> (maybe just MappedEnvVars)
<Configuration>
<MappedEnvVariables>
// full syntax (can allow for mapping host system env var to unique name)
<MappedEnvVariable>
<HostEnvVariable>ComputerName</HostEnvVariable>
<SandboxEnvVariable>HostComputerName</SandboxEnvVariable>
</MappedEnvVariable>
// short syntax (for generic env vars)
<MappedEnvVariable>VSTEST_RUNNER_DEBUG</MappedEnvVariable>
</MappedEnvVariables>
// maybe even support glob format (expose all VSTEST_ environment variables)
<MappedEnvVariable>VSTEST_*</MappedEnvVariable>
</Configuration>
This would make the Sandbox more useful for some automated testing frameworks.
I would think that it would actually be a onetime 'copy' of the environment variables done at Sandbox startup. So that within the Sandbox if the environment variable was changed, it would ONLY affect the Sandbox, not the Host. And that reserved environment variables (like ComputerName in the Sandbox) would not be settable
