Skip to content

Instantly share code, notes, and snippets.

View msys-vagrant-up
5
FO global: Vagrant version: 2.2.15
INFO global: Ruby version: 2.6.6
INFO global: RubyGems version: 3.0.3
INFO global: VAGRANT_EXECUTABLE="C:\\HashiCorp\\Vagrant\\embedded\\gems\\2.2.15\\gems\\vagrant-2.2.15\\bin\\vagrant"
INFO global: VAGRANT_INSTALLER_EMBEDDED_DIR="C:\\HashiCorp\\Vagrant\\embedded"
INFO global: VAGRANT_INSTALLER_ENV="1"
INFO global: VAGRANT_INSTALLER_VERSION="2"
INFO global: VAGRANT_LOG="debug"
INFO global: VAGRANT_POWERSHELL_VERSION_DETECTION_TIMEOUT="99999"
@MBetters
MBetters / vs2010-and-win7-sdk-on-win10.md
Last active Dec 30, 2020
VS2010 + Win7.1 SDK on Win10 VS2019
View vs2010-and-win7-sdk-on-win10.md

Getting a Clean Install of Visual Studio 2010 and the Win 7.1 SDK on Win 10 and Using It from Visual Studio 2019

I found this process extremely laborious and full of dead-ends. I had to combine several processes found on the internet into one procedure. This is probably missing a few steps. I hope it's helpful to people googling for this. If I'm missing steps please leave comments.

The Surgical Procedure

  • Uninstall any existing 2010-related packages (both x86 as well as x64) from Control Panel > Programs and Features or Add or Remove Programs. Uninstall the components in the order laid out by this MSDN docs section.
  • Recursively delete all the following registry keys, if they exist:
    • Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\VisualStudio\10.0
    • `Computer\HKEY_USERS.DEFAULT\Software\Microsoft\VisualStudio\10.0
View vagrant_init_succeeded.txt
PS C:\Projects> vagrant init --debug ubuntu_base > d.txt
INFO global: Vagrant version: 2.2.9
INFO global: Ruby version: 2.6.6
INFO global: RubyGems version: 3.0.3
INFO global: VAGRANT_EXECUTABLE="C:\\HashiCorp\\Vagrant\\embedded\\gems\\2.2.9\\gems\\vagrant-2.2.9\\bin\\vagrant"
INFO global: VAGRANT_INSTALLER_EMBEDDED_DIR="C:\\HashiCorp\\Vagrant\\embedded"
INFO global: VAGRANT_INSTALLER_ENV="1"
INFO global: VAGRANT_INSTALLER_VERSION="2"
INFO global: VAGRANT_LOG="debug"
INFO global: VAGRANT_POWERSHELL_VERSION_DETECTION_TIMEOUT="99999999"
View vagrant_init_fail_win10_powershell7
PS C:\Projects\ubuntu-vm> vagrant init --debug ubuntu_base > d.txt
INFO global: Vagrant version: 2.2.9
INFO global: Ruby version: 2.6.6
INFO global: RubyGems version: 3.0.3
INFO global: VAGRANT_EXECUTABLE="C:\\HashiCorp\\Vagrant\\embedded\\gems\\2.2.9\\gems\\vagrant-2.2.9\\bin\\vagrant"
INFO global: VAGRANT_INSTALLER_EMBEDDED_DIR="C:\\HashiCorp\\Vagrant\\embedded"
INFO global: VAGRANT_INSTALLER_ENV="1"
INFO global: VAGRANT_INSTALLER_VERSION="2"
INFO global: VAGRANT_LOG="debug"
WARN global: resolv replacement has not been enabled!
@MBetters
MBetters / cloudSettings
Last active Apr 7, 2020
Visual Studio Code Settings Sync Gist
View cloudSettings
{"lastUpload":"2020-04-07T19:08:44.842Z","extensionVersion":"v3.4.3"}
@MBetters
MBetters / cloudSettings
Created Jan 10, 2020
Visual Studio Code Settings Sync Gist
View cloudSettings
{"lastUpload":"2020-01-10T18:24:51.670Z","extensionVersion":"v3.4.3"}
@MBetters
MBetters / set_kits_env_vars.sh
Last active Jun 13, 2020
Script to manually set the environmentVariables of all the kits in VSCode's CMake Tools' .vscode/cmake-kits.json
View set_kits_env_vars.sh
#!/bin/bash
# Usage: source ./set_kits_env_vars.sh /path/to/your/environment/setup/script
# Prerequisites: jq (sudo apt-get install -y jq)
# This script sources the environment script provided by the given argument
# and sets all the "environmentVariables" fields in .vscode/cmake-kits.json accordingly.
# TODO: