Visual Studio with AWS Explorer on Windows definitely makes you lazy. I mean, it's fantastic to be able to build and deploy something like a Lambda function by right-clicking on the project, but sometimes it's better to understand what is going on under the hood.
Despite which, I am now pretty committed to switching to Visual Studio Code now that I am able to build everything in a similar way. My major concern at this point was making sure that when working on Windows (which will still happen) that the build/test/deploy sequence is almost exactly the same as on Debian. I thought that perhaps I would have to pull a pile of stupid stunts like this with wacky hybrid scripts but then I remembered WSL2!
Windows Subsystem for Linux (version 2) is a proper Linux kernel running alongside your Windows system. I have been using it quite a lot when dealing with some hardware that we use, the Cassia Networks X1000 Bluetooth gateway. At SmartShepherd we are often faced with 500 or more Bluetooth LE devices we need to connect to in a short period of time and it's just not possible using the bluetooth stack on Android (or pretty much anything). I have a small server application that runs on the Cassia (they use Ubuntu containers) and the environment hosts SSH sessions and secure copy for testing new versions of this. Hence the Debian install of WSL2 was getting a workout.
However, because it's already installed I might as well go the whole hog and try to replicate the .NET environment I have on Chungus the Proliant here on BUSTER3, the Acer Nitro.