chocolatey | Chocolatey NuGet - Like apt | DevOps library

While it doesn't directly answer the question (it appears that the CLI part of vscode does not respect proxy settings), I resolved my specific problem by downloading the .vsix files for the extensions required and put them in my configuration-as-code repo/deliverable.

Okay, so..., I got it working. Basically what happened was, I thought:

• We always need a forward slash before speciying the install arguments to chocolatey like so:

  choco install --install-arguments='/argument1=""someValue"" argument2=""anotherValue""'

  Turns out that this is not true. We don't need to specify any forward slash "/" before "argument1" in the PowerShell command above.

• I also believed that we need to use a pair of double quotes ("") before and after we specify the value to an argument that we pass to the native installer like this:

  --install-arguments='/argument1=""someValue"" argument2=""anotherValue""'

  Turns out this is also incorrect. We don't have to use double quotes ("") before and after we specify a value for each argument. We just have to do it normally like how the native installer expects arguments to be passed to it.

With this knowledge, I rewrote the Tableau Desktop installation PowerShell command to:

So cassandra is a bash script file; no surprise that doesn't run on Windows. I also don't see cassandra.bat or cassandra.ps1 in your ls directory output.

That last point tells me that you have downloaded the release candidate for Apache Cassandra 4.0. Windows support was removed as of Cassandra 4.0, thus the *.bat and *.ps1 files are now gone.

If you need to run on Windows you have two options:

• You can download Apache Cassandra 3.x and run that natively on Windows.
• You can use the WSL (Windows Subsystem Linux) to run Cassandra 4.0.

In the Microsoft-hosted Windows agents, the pre-installed MinGW is Mingw-w64 8.1.0, no MinGW32 installed.

To install MinGW32 on the Microsoft-hosted agents, you need to execute some related command lines in the pipeline. I searched and tried, but did not find any available command can be used to install MinGW on Windows.

As a workaround, maybe you can try manually install MinGW32 on your local Windows machine and then add a self-hosted agent on the local Windows machine to run the pipeline.

You can reference the following article to install MinGW on Windows:

• Installing the 32-bit and 64-bit C (gcc) and C++ (g++) Compilers on Windows

Are you sure, that the path to Pycharm is correct? Did you navigate to C:\Program Files\JetBrains\PyCharm\bin ? In my case the path is as follows: C:\Program Files\JetBrains\PyCharm Community Edition 2021.1\bin

To set the correct pat in Windows CMD you can do the following:

I was able to solve the issue by installing the F# Compiler Tools using paket. The F# Compiler Tools for F# 4.5 runs on .NET Framework (or or mono) unlike F# 5 which runs on .NET Core (or .NET 5).

My Dockerfile doesn't look too much different from before. I still base it on the Microsoft .NET Framework SDK 4.8 image as I want access to the .NET SDK.

I have same the failure. I can't seem to make pgAdmin 4 work. I installed PostgreSQL on a different laptop, pdAdmin 4 comes up, but then there was a different failure.

I think the reason is that when executing the script with sh test.sh we're asking the POSIX interpreter (shell) to execute the content on the script, while when executing it with ./test.sh we're asking the script to "execute itself".

For the latter, the file needs to have execution permissions, which you can add with

Had two separate Problems here

1. The MinGw installation from Chocolatey does not include mingw32-make.exe. I uninstalled it, got the MinGW-Installer and proceeded as per this answer: CMake Error: CMake was unable to find a build program corresponding to "MinGW Makefiles"

2. I had to actually run cmake --build builds after the first command, which I overlooked in the docs