6 ms·
Regarding the issue of a special command prompt.. I haven't touched it in years and probably not up to date with the latest vs, but I had a small project that w
by asveikau 6y ago
Regarding the issue of a special command prompt.. I haven't touched it in years and probably not up to date with the latest vs, but I had a small project that would scan the registry for VS installs and try to find cl.exe.
https://github.com/asveikau/clwrapper https://github.com/asveikau/clwrapper
It is a hackish solution and I would be weary deploying it to customers. New versions of VS would break it. It was good enough for my own use on 1-person projects though.
- genocidicbunny 6y agoHave you used this with the newer VS versions? Starting from 2017 and on, they're using a private registry hive for storing configuration, so you have to first know where to load the private hive from before you can use it.
- asveikau 6y agoThanks for the heads up. Maybe I will try it sometime and update that project.