Hello I need help packaging the above note pad ++ version. I have run the .exe and captured this into an MSi which is deploying nicely. However I would like to ensure that users are not confronted with the update prompt as well as change the default save As location to the users My Documents. I can see that these two settings are controlled by the following XML file C:\Users\%USERNAME%\AppData\Roaming\Notepad++\config.xml. My question is how can I edit this file? It is generated when the program is launched not at install. Additional how can I pass the environment variable %USERNAME% to the xml file.

I assuming you have to edit the MSI to say at launch (Self Repair) do the following  - set environment variable - copy file to location - Edit XML file with environment variable 

XML extract that controls Save As path:
<GUIConfig name="openSaveDir" value="0" defaultDirPath="NEED PATH HERE" />

XML extract that controls Updates:
<GUIConfig name="noUpdate" intervalDays="15" nextUpdateDate="20080426">no</GUIConfig>

Im using Admin Studio, deploying to Windows 7 64bit.

Not sure how this can be achieved?
Answer Summary:
Cancel
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Answer Chosen by the Author

0
Once packaging is complete modify the following files

c:\Users\triplowadm\AppData\Roaming\Notepad++\plugins\config\PluginManager.ini
c:\Users\triplowadm\AppData\Roaming\Notepad++\config.xml

These will define if updates are run and where the Save As defaults to.

INI files may not be captured by Admin Studio depending on your Admin Studio settings

Also I used Active Setup to deploy these to the App Data folder.
Answered 05/13/2015 by: stavbergenstein
White Belt

  • For lack of understanding I believe that Notepad is regenerating this folder on first run. If I copy down my app data from the package I have created I get my Save As location and no updates. If I delet this folder from the workstation It regenerates with the standard settings. How can I stop this repair?
Please log in to comment

Answers

0
Once you have installed your current package, run another capture and record the changes made to the machine when you start the application and then configure it to your requirements. Then add a custom action to your package which will write a correctly configured XML file to the user profile.
Answered 05/06/2015 by: EdT
Red Belt

  • Can you please provide more detail on this part of your comment " Then add a custom action to your package which will write a correctly configured XML file to the user profile." I cant do it on capture as I don't know who the user is at launch.
    • Basically a VBScript that writes the XML file line by line, where you can also use the vbscript to extract environment variables and write them into the file where required. In fact I wrote a wisescript some years ago which does most of the work for you and you can find it on Symantec Connect as an article.
Please log in to comment
0
To disable the update prompt you need to rename or delete the updater folder. This can be done by a script.

if exist "%ProgramFiles%\Notepad++\updater" (ren "%ProgramFiles%\Notepad++\updater" "updaterdisabled")
if exist "%ProgramFiles(x86)%\Notepad++\updater" (ren "%ProgramFiles(x86)%\Notepad++\updater" "updaterdisabled")
Answered 05/07/2015 by: aragorn.2003
Red Belt

Please log in to comment
0

if you have AdminStuio, they have an option to configure XML files.

So as above, get those files, put them into your package, then use the AdminStuido GUI to edit the sections you need.

Answered 05/07/2015 by: Badger
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity