I am trying to install TinyCAD on a laptop at a large defense company where IT intercepts every install and determines whether to give the user permission to install or not. It would make this process easier if you modified the manifest for the installer to fill in the fields for the following missing Windows properties: Program name, Program publisher, Description, Version, Language. If you view the properties of any .exe file, these are the fields shown under the tab named "Details". The reason is that a security product called FortiClient (possibly a McAfee product - not sure) intercepts the attempt to install and captures these 2 properties from the installer properties. It then creates an IT request to approve the install and you then have to wait for IT to get back to you with a magic code. If the program name and properties are simply blank, IT will almost certainly reject the installation!
I know that you can access the Manifest of TinyCAD itself from within Visual Studio, but I am not sure if that will carry through to the installer or not. I used to use the Manifest option for the older TinyCAD executables, but I don't think that I ever implemented them for the installer... The installer probably has some special keyword commands to initialize these variables for you.
Thanks,
Don Lucas
The last time that I checked, this is done by creating a program manifest file for the installer program. It might also be able to be done within the installer framework input commands - not sure.
Hi Matt -
I am trying to install TinyCAD on a laptop at a large defense company where IT intercepts every install and determines whether to give the user permission to install or not. It would make this process easier if you modified the manifest for the installer to fill in the fields for the following missing Windows properties: Program name, Program publisher, Description, Version, Language. If you view the properties of any .exe file, these are the fields shown under the tab named "Details". The reason is that a security product called FortiClient (possibly a McAfee product - not sure) intercepts the attempt to install and captures these 2 properties from the installer properties. It then creates an IT request to approve the install and you then have to wait for IT to get back to you with a magic code. If the program name and properties are simply blank, IT will almost certainly reject the installation!
I know that you can access the Manifest of TinyCAD itself from within Visual Studio, but I am not sure if that will carry through to the installer or not. I used to use the Manifest option for the older TinyCAD executables, but I don't think that I ever implemented them for the installer... The installer probably has some special keyword commands to initialize these variables for you.
Thanks,
Don Lucas
The last time that I checked, this is done by creating a program manifest file for the installer program. It might also be able to be done within the installer framework input commands - not sure.