On 9/1/13, Brad Anderson <e...@gnuk.net> wrote: >> What I need from you guys and your different VS installs is, >> for each one, a bug report with what is necessary to get it >> installed. Then we can add it to the modern version of my >> floppy disk "linker collection". > > This can be automated easily enough. The installer can detect > what versions of VS are installed and either set an environment > variable or modify sc.ini (your choice). It could probably be > made forward compatible since Microsoft has been using basically > the same paths and registry keys for every new release since at > least VS 2005.
Yes, and VS comes out what, maybe once a year? This is possible to implement and maintain. If it weren't, then installing VS plugins would be impossible, but as far as I know it mostly works out of the box (hell, VisualD does it, so why can't we do something as simple as detect VS paths?)
