Chocolatey-for-wine

Chocolatey packagemanager automatic installer in wine, handy to install quickly programs in wine (and subsequently find bugs in wine ;) )
For some bugs workarounds are added like for Visual Studio Community 2022 and nodejs, see further on.
To install Visual Studio Community 2022: do 'winetricks vs22_interactive_installer' to install something via the Visual Studio 2022 installer; 'winetricks vs22_interactive_installer' now got me in ten minutes into the main program (selected Desktop development with C++).

Install :

• Download and unzip the release zip-file and do 'wine ChoCinstaller_0.5a.735.exe' (takes about a minute to complete)

Optional:

• Check if things went well: "choco install chromium" and "start chrome.exe (--no-sandbox not needed anymore as of wine-8,4)"

Optional:

• Run the installer like 'SAVEINSTALLFILES=1 wine ChoCinstaller_0.5c.745.exe' , then the install files (like Powershell*.msi and dotnet48) are saved in '$HOME/.cache/choc_install_files' and they don't need to be downloaded again if you create a new prefix)

Optional:

• Install (rudimentary) powershell 5.1 via winetricks (see below) to get better compability for scripts: occasionally a chocolatey install script might fail as it is written for Windows Powershell (not for Powershell Core). Installing powershell 5.1 and enabling builtin powershell host might help workaround this:
  • winetricks ps51 (takes very long time to complete!, see below)
  • choco.exe feature enable --name=powershellHost

Updates:

• Update : As I was bored during lock-down I wrote a custom winetricks(.ps1) with some verbs I find handy.

About PowerShell:

• 'wine powershell.exe' starts the PowerShell-Core console.

  There's also some PowerShell 5.1 support:

• From PowerShell-Core console do 'winetricks ps51' (takes very long time to complete!!!)

  Then from PowerShell-Core console you could:

• start powershell 5.1 console by "ps51"

• or execute some command through powershell 5.1 like (an example) " ps51 '$PSVersionTable' "

• by setting environment variable "$env:PS51=1" you can start a new powershell 5.1 console by just "powershell" (or from linux bash: "PS51=1 wine powershell")

• or you could work in graphical PowerShell 5.1 Integrated Scripting Environment with 'winetricks ps51_ise'

About ConEmu:

ConEmu console suffers from a few wine-bugs:

• Ctrl^C to quit a program that doesn't return to the console doesn`t work. Use Shift^Ctrl^C instead.
• Selecting text in the ConEmu window (for copy/paste) doesn't highlight the selection. Included is a very sad hack against recent wine versions that works around this, so highlighting should just work now.

About winetricks(.ps1):

• If you don't call it ('winetricks' in powershell-console) , nothing gets downloaded so no overhead there.
• A lot of verbs (like powershell 5.1) need a few essential files to extract stuff from msu packages. Installing these essential files requires first huge downloads , and takes lots of time during 1st time usage. But after things are cached it goes quickly . For example if you might wanna try 'winetricks ps51' first, it will take about approx. 15 minutes. Some other verbs might take 5 minutes on first time usage. But after you called a verb once this nuisance is gone.
• Files are cached in directory '$HOME/.cache/winetrickxs'. If you call all verbs it'll take about 800 MB there.
• Hopefully some better 64-bit support for various verbs.
• Possibility to extract a file and (try) install from an msu file. Do 'winetricks install_dll_from_msu' to see how.
• A rudimentary Powershell 5.1.
• experimental dotnet481 installation, and dotnet35 (might be needed by apps not satisfied with current dotnet48 installation).
• Autotab-completion. Note: while using multiple verbs from command line they have to be seperated by a comma from now on (this is how powershell handles multiple arguments) So 'winetricks riched20 gdiplus' won't work anymore, use 'winetricks riched20,gdiplus' instead
• Some programs fail to install/run when you try them via Chocolatey due to wine-bugs. I added a few workarounds in winetricks for them, see below:
• A special verb to install requirements to get Affinity Photo/Designer started.
• Special verbs (winetricks vs19, vs22 and vs22_interactive_installer) to install working Visual Studio Community 2019 and 2022 (see screenshot, >10 mins to install and requires approx. 10GB!, after install start devenv.exe from directory c:\Program\ Files (x86)\Microsoft Visual Studio\2019\Community\Common7\IDE/)
• Special verb to get access to various unix commands like grep,sed, file, less, curl etc. etc. (winetricks git.portable, Disclaimer: some commands do not yet work due to wine bugs
• Also included a few powershell scripts adapted from codesnippets found on the internet:
  • How to embed an exe in a powershell script via Invoke-ReflectivePEInjection (the exe won't show up in tasklist).
  • How to make fancy messageboxes
  • Convert a powershell script (ps1) into an exe.
  • And a few other

About system programs:

Feature is added to replace simple system programs like for example setx.exe by a function in c:\Program Files\Powershell\7\profile.ps1. Or add system programs that are missing like getmac.exe. If programs fail because of insufficient mature or missing system programs one could write a function to return whatever the program expects. Like in profile.ps1 I added (amongst others) a wmic.exe that supports a bit more options, and a basic setx.exe. Or you could just manipulate the arguments passed to the system program. See profile.ps1 and choc_install.ps1. No garantuee this works for more complex programs as well...

Notes:

• Do NOT use on existing wineprefix, only on fresh new created prefix! The installer just stupidly installs dotnet48 itsself and messes with registrykeys. If you have any dotnet version already installed with regular winetricks.sh, it will likely fail, and even if it succeeds, you'll likely end up with a broken prefix. If you need to install stuff with regular winetricks.sh for programs, do NOT use any of the dotnet* verbs. BTW 'Arial' and 'd3dcompiler_47' verbs are already installed by default.
• WINEARCH=win32 is not supported!
• Updating from a previous version is for now not (yet) supported, maybe later

Compile:

• If you want to compile yourself instead of downloading binaries: see compilation instructions in mainv1.c
• Then copy choc_install.ps1 into the same directory
• Then do 'wine ChoCinstaller_0.5a.735.exe'