Today AI opened with a previous Library Key OK, and I made a couple of builds, then closed it. I committed my code in VS 2017, used GitKraken to push the code to the server. When I re-opened AI, the Library Key was corrupt again. Could this process be related to the issue?
I also use the Microsoft Visio Solution Publishing Too :
The Microsoft® Visio® Solution Publishing tool generates entries for the PublishComponent table, one of several database tables that are stored in a Microsoft Windows® Installer .msi file. Windows Installer, which is available as part of Windows, is used to write installation programs that can be configured during setup or at run time. The PublishComponent table in an .msi file contains a list of files that are published to an end user's computer when your application is installed. For more information about Windows Installer and the PublishComponent table, see the Windows Installer Software Development Kit (SDK) on MSDN®, the Microsoft Developer Network.
The Solution Publishing tool works with Windows Installer to help you add Visio-specific entries, such as Visio add-ons (.vsl and .exe files), stencils (.vssx, .vssm, .vsx, and .vsx files), templates (.vstx, .vstm, .vst, and .vtx files), and Help files (.chm files) to the PublishComponent table of the .msi file that you create to install your solution on your users' computers. The Solution Publishing tool is not designed to be an .msi file editor. It requires that you edit an existing .msi file that already contains a PublishComponent table that you can use to add information about the Visio files that you want to publish. The Solution Publishing tool works with Windows Installer version 2.0 and later.
You can save files that you create in the Solution Publishing tool as Visio Solution Publishing Configuration (.vpc) files.
David J Parker,
Microsoft MVP (Visio)