[wix-users] Official 3.14 release date

Tue Jun 11 06:14:42 PDT 2019

You run vswhere.exe, it doesn't display any information and yet I'm wrong?

I suggest that you read:

https://github.com/wixtoolset/issues/issues/5979

Take a look at the comments made by Heaths regarding "launchable"  instances of VS.

I have multiple machines with VS2017 installed also and it's working just fine for me.  As is vswhere.exe.

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

Christopher,

You are wrong . The installation is not corrupt. I have already stated I have tested on clean machine and I have tested on multiple VS 2017 versions. WiX 3.11 handles VS 2017 installation properly. WiX 3.14 beta breaks the support.

On Jun 11, 2019, at 8:48 AM, Christopher Painter <chrpai at iswix.com<mailto:chrpai at iswix.com>> wrote:

You have a corrupt installation of Visual Studio.  It should display a lot of information.   Try running the VS Installer and see if it wan't any repair actions or anything.

________________________________
From: Ivan Peev <ivan.peev at gmail.com<mailto:ivan.peev at gmail.com>>
Sent: Tuesday, June 11, 2019 6:52 AM
To: Christopher Painter
Cc: Rob Mensching; WiX Toolset Users Mailing List
Subject: Re: [wix-users] Official 3.14 release date

Christopher,

This is the only printout:

On Tue, Jun 11, 2019 at 7:49 AM Christopher Painter <chrpai at iswix.com<mailto:chrpai at iswix.com>> wrote:
Please run C:\Program Files (x86)\Microsoft Visual Studio\Installer\vswhere.exe  and post the results.

________________________________
From: Ivan Peev <ivan.peev at gmail.com<mailto:ivan.peev at gmail.com>>
Sent: Monday, June 10, 2019 8:46 PM
To: Christopher Painter
Cc: Rob Mensching; WiX Toolset Users Mailing List
Subject: Re: [wix-users] Official 3.14 release date

Christopher,

Find attached the log file.

On Mon, Jun 10, 2019 at 6:25 PM Christopher Painter <chrpai at iswix.com<mailto:chrpai at iswix.com>> wrote:
If you don't mind, please log the installation of:

https://github.com/iswix-llc/iswix/releases/tag/v4.14.5

Just get to the welcome dialog and cancel out.  You don't need to install all the way.

________________________________
From: Ivan Peev <ivan.peev at gmail.com<mailto:ivan.peev at gmail.com>>
Sent: Monday, June 10, 2019 5:12 PM
To: Christopher Painter
Cc: Rob Mensching; WiX Toolset Users Mailing List
Subject: Re: [wix-users] Official 3.14 release date

Christopher,

Please tell me what tables I should check. Isn't AppSearch command done by the WiX engine?

On Mon, Jun 10, 2019 at 5:59 PM Christopher Painter <chrpai at iswix.com<mailto:chrpai at iswix.com>> wrote:
I see the differences in the log including the MSI name was different.

I don't know how these were built.  Have you compared the databases using ORCA and compared the relevant tables?

________________________________
From: Ivan Peev <ivan.peev at gmail.com<mailto:ivan.peev at gmail.com>>
Sent: Sunday, June 9, 2019 9:23 PM
To: Christopher Painter
Cc: Rob Mensching; WiX Toolset Users Mailing List
Subject: Re: [wix-users] Official 3.14 release date

Hi Christopher,

I'm not talking about the WiX plugin for VS 2019. The issue is VS2017DEVENV property is not available during installation on system with VS 2017. If I run the installer on a system with VS 2019, VS2019DEVENV property is available.

If I go back to WiX 3.11, VS2017DEVENV  property is again working properly when running on VS 2017 system.

On Sun, Jun 9, 2019 at 10:10 PM Christopher Painter <chrpai at iswix.com<mailto:chrpai at iswix.com>> wrote:
I have VS2019 15.9.4 installed on my build server with the 1.0.0.2 WiX VS 2017 extension and WiX 3.14.0.2927 installed.  Everything works just fine.

________________________________
From: Ivan Peev <ivan.peev at gmail.com<mailto:ivan.peev at gmail.com>>
Sent: Sunday, June 9, 2019 4:32 PM
To: Christopher Painter
Cc: Rob Mensching; WiX Toolset Users Mailing List
Subject: Re: [wix-users] Official 3.14 release date

Hi Rob,

It appears my conclusion was too quick. The support for VS 2019 is working fine. However, the support for VS 2017 is now broken. I have tested with the following VS 2017 versions - 15.9.9, 15.8.6, 15.5.2, 15.4.1

I have done the test on a clean machine with no other VS version installed on it. After I went back to WiX 3.11, the installation is again working properly for VS 2017. Version 3.14.0.2927 is broken.

On Tue, May 28, 2019 at 8:16 AM Christopher Painter <chrpai at iswix.com<mailto:chrpai at iswix.com>> wrote:
Ah, I was looking at https://wixtoolset.org/releases/ since it had the 1.0.0.2 of 2019.

I've installed all of them and 3.14 on my build box and 3.14 and updated IsWiX to use the 2019 detection feature in 3.14 and everything looks good to me.

The only thing of note is how much smaller the 2010-2015 versions of the extension are and how quickly they installed.  I had an initial sense that they were missing something and the installation success was a false positive but everything seems to be there just fine.

________________________________
From: Rob Mensching <rob at firegiant.com<mailto:rob at firegiant.com>>
Sent: Tuesday, May 28, 2019 12:10 AM
To: Christopher Painter; Ivan Peev
Cc: WiX Toolset Users Mailing List
Subject: RE: [wix-users] Official 3.14 release date

Yes. VS2017 (and all the others) exist here: https://github.com/wixtoolset/VisualStudioExtension/releases/tag/v1.0.0.2

_____________________________________________________________

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

From: Christopher Painter <chrpai at iswix.com<mailto:chrpai at iswix.com>>
Sent: Monday, May 27, 2019 7:35 PM
To: Rob Mensching <rob at firegiant.com<mailto:rob at firegiant.com>>; Ivan Peev <ivan.peev at gmail.com<mailto:ivan.peev at gmail.com>>
Cc: WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org<mailto:wix-users at lists.wixtoolset.org>>
Subject: Re: [wix-users] Official 3.14 release date

Rob:

RE the VS2019 extension and the item template issue...   does that need a new build of the VS2017 extension also?