I’m using Microsoft Visual Studio Enterprise 2022 (2) Version 17.5.3, and trying to create a Mix project in it. (In case it matters, I’m using Mix 1.14.3 compiled with Erlang/OTP 25.)

I don’t care whether I use cmake, nmake, msbuild, whatever – I only want to configure my codebase such that VS 2022 on my machine (and the machines of any future collaborators) will call mix for the key operations, to be able to press Ctrl_F5 to call mix run, etc., without hacky workarounds like “just rebind your hotkeys to run globally hard-coded commands”.

I’m new to progamming on Windows, and also new to Elixir. I have intermediate experience with Python programming and packaging on Linux. I tried reading this article, but got a bit lost since I’m not clear on how much of what they’re saying is specific to C-like toolchains or depends on tight couplings between the editor and the codebase that simply aren’t possible with languages the editor wasn’t hard-coded to support.

So, what kind of project metadata file can I create to correctly indicate a Mix project to Visual Studio Enterprise 2022, at least just to support basic tasks like compiling and running?