[FAQ] io.Connect 9.x Installation Location and Packaging

io.Connect Desktop
,
1

Note: This article applies only to the io.Connect Desktop 9.x version stream. The deployment and packaging model changed significantly in io.Connect Desktop 10.0 and beyond. The extensible installer was replaced by the seed project approach, and the gilding executable was removed.
For full details on the 10.0 changes, see:

Q: What is the default installation location for io.Connect Desktop 9.x?

The default installation path under C:\Users\<user id>\AppData\Local\interop.io\io.Connect Desktop is part of the current application design and does not affect the operation of the platform.

Re: io.Connect Desktop 10.0 version stream - the io.Connect Desktop installation folder can be placed at any location.

Q: Can I install io.Connect Desktop under C:\Program Files or C:\Program Files (x86) instead?

There is no technical limitation preventing the application from being installed under C:\Program Files or C:\Program Files (x86).

However, if the installation path is changed, the user data and cache paths should be updated accordingly to ensure proper operation. The Instances directory cannot be relocated, and certain runtime components will continue to reside under the user’s local AppData folder by design.

For details on how to customize the installer (including the installation location), see the documentation:

Q: After installation, an executable runs from the %TEMP% folder (for example, a tmp.exe-style path). Is this expected? Is this caused by an expired certificate?

Yes. The executable running from the %TEMP% folder is expected. This behavior is part of the application’s design. This behavior is not related to expired certificates, and providing a new certificate does not change it.

Q: Endpoint protection or application packaging tools are blocking the executable. What is the recommendation?

Whitelist the Glue42 process to allow execution from the %TEMP% directory. This will prevent it from being flagged or blocked by endpoint protection or application packaging tools.

Notes

  • This article applies only to the 9.x version stream.