I am trying to run AzureAD Module PowerShell commands inside windows container but due its dependency with "IEFRAME.DLL" its throwing error
I also tried by copying dll inside container to windows system folder but it still complains
Is there any workaround or hack available to get it work inside windows container?
Related
Currenlty I am using Visual Studio community edition and Gtest.
When I run my test using the Visual Studio debug, my test are running fine
But when I build the solution and run my test fail.
Is there a way I can pass the PATH environment to the command I am runnig?
Try to set the PATH on powershell so it would load while running the command.
Thanks to #273k I was able to solve my problem.
The reason this test did not pass on the command line, was due to this was being run on a different folder.
Once I moved the relevant support files in the same folder the test started to pass
I am launching PowerShell via blueprism and need to change the expiration date on some users.
I have the packages installed on the machine and can run the code if I open PowerShell outside of the blueprism environment.
Blueprism start location is "C:\Program Files\Blue Prism Limited\Blue Prism Automate"
Local PowerShell starts in network drive "G:" where the packages are installed.
I have tried to change the location, but it does not help.
Elevated permission is not the problem and I have checked that the code works.
This is the error message: Set-ADAccountExpiration : The 'Set-ADAccountExpiration' command was found in the module 'ActiveDirectoryModule', but the module could not be loaded.
EDIT NOTE: I'm launching blueprism via the
application modeler.
I created a classic CI pipeline in azure devops to run aws commands using "AWS CLI template". I used "aws configure sso" command in AWS CLI but when I run the pipeline, I'm getting this error- No windows console found. Are you running cmd.exe? And the process failed with exit code 255" what is this error exactly and please anyone tell me, how can I remove it?
What is the OS of the agent you used to run the CI pipeline? Windows, Linux or macOS?
According to the introduction about the extension "AWS Toolkit for Azure DevOps", the AWS CLI task is only available on Windows agent.
Looks like this task can only call the cmd.exe to execute the command. And the cmd.exe is only available on Windows.
[UPDATE]
What agent did you use? Microsoft-hosted Windows agent, or self-hosted Windows agent?
Please make sure the cmd.exe has been installed on the Windows machine, and has been added to the system environment variable.
You can run the bash command printenv to list all the system environment variables, then check if this COMSPEC=C:\Windows\system32\cmd.exe is listed.
If the cmd.exe also has been installed correctly on your local Windows machine, you can try directly executing the related AWS CLI command on you local Windows machine to see if the same issue occurs. If the same issue occurs, the problem should occur on the AWSCLI itself.
If the issue only occurs when using the AWS CLI task, the issue should occur on the task itself, you can report this issue on the Q & A tab of the extension on Marketplace.
I am trying to install Emscripten on my computer, and I have run into trouble getting Emscripten actually installed.
I am using the same commands as can be found on the project webpage, but when I try to run
emsdk install latest
Powershell (which is what I am using, but the basic command prompt is behaving the same way) doesn't do anything at all - it just returns without installing anything.
For reference, I have installed Emscripten on this same computer before, but decided to try and do a fresh install of Emscripten after running emsdk activate latest decided to "stop working" as well (whereas it worked just fine last week) - running the command, Powershell simply returned without actually doing anything.
Any ideas on what to check to see why these commands don't seem to run?
I think I solved it. When running the install command in Powershell ISE, it threw the error "Python was not found but can be installed from the Microsoft Store: https://go.microsoft.com/fwlink?linkID=2082640"
despite me having Python installed. Changing the order of my PATH variables to set my Python install directory above the Winapps directory solved the issue with running the install command.
Is it possible to have the AWS SDK module loaded once VS Code starts?
Running on OSX, VSCode has the PowerShell extension installed and working.
In a terminal I can type "powershell" and it automatically loads the AWS module because "Microsoft.PowerShell_profile.ps1" has
Import-Module AWSPowerShell.NetCore
Set-DefaultAWSRegion -Region eu-west-1
in there so they are loaded once I start PowerShell.
I was hoping to have the same in VSCode and not having to add these 2 lines inside the PowerShell script(s).
You can add your modules and scripts to launch.json to facilitate this.
More detail can be found at the following link:
https://blogs.technet.microsoft.com/heyscriptingguy/2017/02/13/debugging-powershell-script-in-visual-studio-code-part-2/