/build/static/layout/Breadcrumb_cap_w.png

Scripting Question


Jetbrains dotpeek 2015.2.2 packaging issue

09/30/2016 1943 views
Hello Folks,

I have been working on one application called "Jetbrains dotpeek 2015.2.2". I have downloaded the standalone .exe from Jetbrain. And I can able to package it.Here is problem with this application. .It comes up with License agreement windows when we launch the application(Please see the below screenshots). 
1.How to suppress these windows?
silent installation cmd:  
C:\VendorMedia\JetBrains.ReSharperUltimate.2016.2.2.exe /SpecificProductNames=dotPeek /Silent=True /VsVersion=2016;2;2 /LogFile=test.txt

3pTItp.png
6Ikbpd.jpeg
cmScFl.jpeg
2.Dotpeek files falls under APPdata\Local\JetBrains\... etc how to redirect to ProgramFiles?
 Tried to copy files by using VBscript, but It didn't work for me 

3. It pops up with Feedback window after uninstallation done. how to suppress this window?
Uninstall cmd: C:\Users\xxxx\AppData\Local\JetBrains\Installations\dotPeek06\JetBrains.Platform.Installer.exe /HostsToRemove=dotPeek06 /PerMachine=False

0 Comments   [ + ] Show comments

Comments


All Answers

0
1) Use RegShot to see where its writing the registry settings. Once  you have the information, you can either use (MSI) self repair to action the keys into the HKCU or you can use a batch file replacing the shorcut to JetBrains (this is more of a Citrix HKCU population method). So the batch will copy settings to HKCU then start JetBrains. Hope you get what I mean, its not the best method but if you dont have MSI experience then this is the best alternative.

2) No idea what your on about there.

3) Dont know.


Good luck!
Answered 10/01/2016 by: rileyz
Red Belt

0

1. As above, use your favoured lightweight snapshot to capture where the setting is stored that records you've seen the policy. It's probably in HKCU but could equally be in an XML/INI/whatever file somewhere in the logged-in user's profile.

Ditto for point 3.

2. This is the behaviour of an installer which has been run under an ordinary, non-privileged account.

To bypass all of this nonsense, I'd re-package it into an MSI. For the user profile stuff, you'll need to use self-healing. Search for John Mc Fadyen's oeuvre on self-healing.

Answered 10/03/2016 by: anonymous_9363
Red Belt

0
1. If the windows appear only the first time the user starts the program, then a flag is being written to their user profile, either in the registry or in a configuration file, to record that the display has been made. You need to capture where this is happening and add it to your package.
2. As VBScab has mentioned, this can be the behaviour of an installer that is either designed to be run by a non-admin user or it has been installed by a non-admin user. HOWEVER, it is also possible that the Appdata content is user-specific and needs to stay where it is.  Although more commonly found under the "roaming" subfolder, it is not unusual for user config information to be stored under the "local" folder for apps that have a per-user license.  Mess with that at your peril.
3.  It is interesting to note that you have /PerMachine=False in the UNINSTALL command rather than the INSTALL command. Setting per-user or per-machine configuration is normally only done on install.  If /PerMachine=False is the default install option, then try installing with /PerMachine=True and see if your AppData content moves to a "common" area, eg under ProgramData.  Suppressing uninstall dialogs is not easily done unless you have access to the installer source. Did you check what installer technology the native install is using?  NSIS can be edited and recompiled, and if the internal installer is an MSI, you can harvest it from the TEMP folder (usually), typically when the first install dialog is displayed during a manual installation.  Otherwise, you can capture it to an MSI, but you really need to understand how the app works to make sure that you do not mess with file locations and break the application.

Finally, a product called AutoIT by Hiddensoft could offer you a way of managing the dialog on uninstall. Basically you create an AutoIT program that watches for the appearance of the dialog and then presses the appropriate button to make it go away. The user just sees a momentary flash on the screen but does not need to do anything.  You would point your app's UnInstallstring in the registry to the AutoIT script which would then run the actual UninstallString and manage the dialog before closing.  You could also use AutoIT to manage the installation for you as well as updating the registry, acting as a "wrapper" script for your install.
Answered 10/10/2016 by: EdT
Red Belt

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ