42c-ast.exe isnt signed and you can’t change the location which may cause issues for some like me on a corporate locked down devBox.
Any chance of a fix?
Yea that makes sense to me, and I’m pretty sure it’s already planned; though mightn’t be available yet in beta.
Will check to see what I can find out…
1 Like
Happy to report that the ability to change the location for the binary executable file is indeed planned for inclusion in an upcoming release 
Don’t have an eta at this point.
@mcrobbj I just checked the new v4.28 extension release for VSCode and looks like that feature to specify a custom location for the binary executable is now available.
I’m curious to hear if this enables API Audit and/or API Scan to be run on a corporate locked down devBox?
