You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Output from azd version
azd version 1.11.1 (commit ae08ceb)
Describe the bug
My employer uses BeyondTrust to manage what software can be installed and run by all users. With approval and assistance from our Security dept, I was able to install azd. However, attempts to run azd init in an Aspire AppHost project always fail. azd appears to generate and attempt to execute .cmd files from a 'MSBuildTemp' directory. One of my organization's active security policies prevents the execution of batch files (including .cmd files).
To Reproduce
On a computer with a policy preventing execution of .cmd files, open Terminal.
navigate to the directory of an existing Visual Studio 2022 Aspire AppHost project.
Run azd init
Choose '> Use code in the current directory' at the 'How do you want to initialize your app?' prompt
A BeyondTrust "IT Security Policy" dialog appears, with the following details:
Batch File Blocked
This Batch File has been blocked by IT
Program Name: tmp[hash].exec.cmd
Program Publisher: Unknown
Program Path: absolute path to /MSBuildTmp\tmp[hash].exec.cmd
Close the dialog.
Back in Terminal, azd init appears to be stuck endlessly waiting for .cmd execution that never happens.
Expected behavior
Running azd init should either execute using code-signed .cmd files (whose signature can be added to an allow-list), or it should fail with an appropriate error message if its .cmd execution fails.
Environment
Information on your environment:
* aspire 8.2.2/8.0.100 SDK 9.0.100, VS 17.12.35707.178
The text was updated successfully, but these errors were encountered:
Output from
azd version
azd version 1.11.1 (commit ae08ceb)
Describe the bug
My employer uses BeyondTrust to manage what software can be installed and run by all users. With approval and assistance from our Security dept, I was able to install azd. However, attempts to run azd init in an Aspire AppHost project always fail. azd appears to generate and attempt to execute .cmd files from a 'MSBuildTemp' directory. One of my organization's active security policies prevents the execution of batch files (including .cmd files).
To Reproduce
azd init
azd init
appears to be stuck endlessly waiting for .cmd execution that never happens.Expected behavior
Running
azd init
should either execute using code-signed .cmd files (whose signature can be added to an allow-list), or it should fail with an appropriate error message if its .cmd execution fails.Environment
Information on your environment:
* aspire 8.2.2/8.0.100 SDK 9.0.100, VS 17.12.35707.178
The text was updated successfully, but these errors were encountered: