[wix-users] VSIX Install Falling

Mon Feb 21 10:11:06 PST 2022

You set the vsix project to not build a container and to copy it's files to a directory.  Then in your installer you author those files into components.  Use VS Extension directory to get the extensions directory of VS  and   Copyfile elements to duplicate your files to those directories.    Finally call devenv.exe /setup.

This is how IsWiX deploys it's addin.  You can pluck through the source at https://github.com/iswix-llc/iswix/tree/master/Installer

I'd be happy to spend 30 minutes with you showing the whole process from scratch.

________________________________
From: Coryat, Jim <Jim.Coryat at softprocorp.com>
Sent: Monday, February 21, 2022 10:16 AM
To: Christopher Painter <chrpai at iswix.com>; WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org>
Subject: RE: VSIX Install Falling

This message was sent securely using Zix®<http://www.zixcorp.com/get-started/>

I was given the location of the vsix file and the existing batch file installer and was asked to create a real installer with logging etc.  I was unaware you can compile an extension project into an msi.  I’ve not built one before.  Would seem a lot easier to package into an installer for a deployment.  Guess the vsix is for general user consumption.

I would be interested in seeing a sample.

From: Christopher Painter <chrpai at iswix.com>
Sent: Thursday, February 17, 2022 4:57 PM
To: WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org>
Cc: Coryat, Jim <Jim.Coryat at softprocorp.com>
Subject: Re: VSIX Install Falling

IMPORTANT NOTICE - This message sourced from an external mail server outside of the Company.

VSIX has two deployment methods

vsixinstaller using vsix file

deployed by MSI

 have you considered the latter?   I have samples I can share with you.  Basically I use the VS extension to detect Visual Studio, DuplicateFile all my files to certain directories if found and call devenv.exe /setup.  Have been doing it this way for about 14 years and it works very well.

________________________________

From: wix-users <wix-users-bounces at lists.wixtoolset.org<mailto:wix-users-bounces at lists.wixtoolset.org>> on behalf of Coryat, Jim via wix-users <wix-users at lists.wixtoolset.org<mailto:wix-users at lists.wixtoolset.org>>
Sent: Wednesday, February 16, 2022 4:50 PM
To: WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org<mailto:wix-users at lists.wixtoolset.org>>
Cc: Coryat, Jim <Jim.Coryat at softprocorp.com<mailto:Jim.Coryat at softprocorp.com>>
Subject: [wix-users] VSIX Install Falling

I Have an install that installs an SDK for internal consumption.  One of the components is a .vsix file for VS2019 and/or VS2022

In the component file for the vsix the VsixPackage element looks like this:

<vs:VsixPackage PackageId="MyVisxPackage.a5326796-1266-4b41-8a6c-0db3d89547f6" />

This fails because it chooses the VS2014 VSIXInstaller.exe which does not know about any later versions.  That's what I deduced when I executed the command line at a command prompt and looked in the log file and reviewed the error.

Looking through the source code I see that the property VS_VSIX_INSTALLER_PATH contains the location of the VSIXInstaller.exe so I added a SetProperty similar to what is in the VsixPackage.wks and set it to the VSIXInstaller.exe that is installed with VS2019/VS2022, using the location identified in AppSearch using a file search.

This is the error displayed:
MSI (s) (D0:40) [17:43:37:769]: Executing op: ActionStart(Name=vim925A50D7601FA96A310238BC0296ED40,,)
Action 17:43:37: vim925A50D7601FA96A310238BC0296ED40.
MSI (s) (D0:40) [17:43:37:774]: Executing op: CustomActionSchedule(Action=vim925A50D7601FA96A310238BC0296ED40,ActionType=3122,Source=C:\Program Files (x86)\Microsoft Visual Studio\Installer\resources\app\ServiceHub\Services\Microsoft.VisualStudio.Setup.Service\VSIXInstaller.exe,Target=/q  "C:\Program Files (x86)\SoftPro\Exchange\v3.1\vsix\x86\SoftPro.Exchange.Product.VisualStudio.Package.vsix" /admin,)
CustomAction vim925A50D7601FA96A310238BC0296ED40 returned actual error code -2146233088 (note this may not be 100% accurate if translation happened inside sandbox)

The visx installs running it interactively.  What am I missing?
________________________________
NOTICE: The information contained in this message is proprietary and/or confidential and may be privileged. If you are not the intended recipient of this communication, you are hereby notified to: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately.

____________________________________________________________________
WiX Toolset Users Mailing List provided by FireGiant http://www.firegiant.com/<https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.firegiant.com%2F&data=04%7C01%7CJim.Coryat%40softprocorp.com%7C536ee14b0b254cbb037108d9f2607566%7C8a807b9b02da47f3a903791a42a2285c%7C0%7C0%7C637807318374097110%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&sdata=kgudeNOzEJGfX79Ck5EoFTN7RQvk6GgdfjDXDLwqu0Y%3D&reserved=0>

-------------------------------------------------------------------------
This message was secured by Zix<http://www.zixcorp.com>®.