Custom Query (202 matches)
Results (28 - 30 of 202)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #29 | fixed | Environment variable SIGNTOOL in Readme | jasper | michelpons |
| Description |
The Readme file developed for explaining building of COBIA related installers starts with instructions about environment variables. (Temporary) Instructions for new release, Jasper 2020: 2 3 ENVIRONMENT 4 - Set the environment variable SIGNTOOL to point to Signtoo.exe (Win 10 SDK) Should this be a system-wide environment variable or a user environment variable? Secondly signtool.exe (missing the "l" above in the readme file) exists at two locations at least: C:\Program Files (x86)\Windows Kits\10\bin\10.0.18362.0\x64, and another one under C:\Program Files (x86)\Windows Kits\10\bin\10.0.18362.0\x86. If the environment variable is created to point to a location, which one should be used? |
|||
| #30 | fixed | Description of components within custom installation of SDK | jasper | michelpons |
| Description |
When one chooses the custom installation of the components within the COBIA SDK installation, the only piece of information displayed to the user, except the name given to the components, is the disk space to be used. If possible, it would be proper to describe what is meant by each component so that the choice made, if any, is based on as complete info as possible. |
|||
| #31 | fixed | Update stand-alone installer(s) | jasper | michelpons |
| Description |
It seems that the msi making use of both the COBIA runtime x86 merge module and of the COBIA runtime x64 merge module does not carry any dialog regarding license. Seems a bit odd. Is there anything preventing such a dialog to take place? Is this msi supposed to be used in a kind of silent mode only? |
|||