[wix-devs] VS2017/2019 Detection Warning Property

[Christopher Painter]

Another takeaway from that thread is a user seems to have installed SSDT (Microsoft.VisualStudio.Product.SQL) and thinks VS2017 detection in 3.14 is broken because it (allegedly) worked for him in WiX 3.11.



________________________________
From: Christopher Painter
Sent: Tuesday, June 11, 2019 9:10 AM
To: WiX Toolset Developer Mailing List
Subject: VS2017/2019 Detection Warning Property

FWD to wix-devs per Rob.     The thread referenced (removed) dealt with a user who has a corrupt 2017 installation who is strongly convinced that WiX 3.14 is broken.


________________________________
From: Rob Mensching <rob at firegiant.com>
Sent: Tuesday, June 11, 2019 8:34 AM
To: Christopher Painter; ivan.peev at gmail.com
Cc: WiX Toolset Users Mailing List
Subject: RE: [wix-users] Official 3.14 release date


That's a totally reasonable thing to bring up on wix-devs, especially given this thread.



_____________________________________________________________

Short replies here. Complete answers over there: http://www.firegiant.com/





From: Christopher Painter <chrpai at iswix.com>
Sent: Tuesday, June 11, 2019 6:18 AM
To: Rob Mensching <rob at firegiant.com>; ivan.peev at gmail.com
Cc: WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org>
Subject: Re: [wix-users] Official 3.14 release date



Rob,



 I personally would love a safety check in the code if possible.  A property such as VSANYWHEREISSUESFOUND  that I could use in a LaunchCondition to say  please check the health of your VS instances and run [ProductName] setup again.   I think I mentioned this somewhere and Heath didn't like it.  Maybe he didn't understand what I was asking for or maybe I didn't understand why he didn't like it.



Thanks,

Chris