I live & breath in WSL bash. But I use slickedit on the Windows side. Share file systems. So .. edit code in Windows and run code, side-by-side on WSL. A very happy environment for me.
Thanks. I'd be interested in hearing about the types of projects on which you use this.
When applicable, I do this too. This works great when I'm using msbuild and msbuild invokes the compiler in wsl. For projects that are created in Visual Studio this is really easy to do. The projects so generated also work well in SlickEdit from windows.
I've not found it to be as simple with large linux buidls. I prefer to build launching the build configuration I'm interested in from an IDE, as the commandlines for some of our builds are quite lengthy, and there are hundreds of configurations. (This is a large set of projects.) It's easy to get a build option wrong. The builds take a while.
These larger linux builds require chroot, and invoke gmake, and some custom hacks, I mean tooling. I'm not sure I can make these work under MSBuild with it ssh'ing into WSL2. Depending on how you set it up, msbuild sometimes feels it needs to rsync things, and that would be unpleasant on this project, as it's quite large. I guess I could try this, although I expect file searches from windows -> wsl2 fs would probably be not especially pleasant. This is a LOT of source.
IDK, I guess I could try to see if I can make MSBuild invoke the build - but I have a sinking suspicion it'll choke and die on the chroots invoked by the build. But I haven't tried it myself to know for sure.
I am reasonably certain I could make all of this work from windows using VSCode -> WSL2. The thought of moving my SE project files over to VSCode makes me want to cry, however. If I have to do that to operate in WSL, I'll likely just switch to VSCode for everything, although I don't like it very much. It's too difficult to maintain the project files for all of this across multiple IDEs and I expect I'd hate that more than I hate VSCode. If MSBuild can successfully build these projects under WSL, then Visual Studio would be a reasonable choice too - and somewhat easier since we have tools to automatically create and update VS projects, presuming I can convince it not to rsync the world constantly. I don't love VS as an editor, however.