Notepad 6.7.5 packaging edit default Save As location & Updates
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?
0 Comments
[ + ] Show comments
Answers (4)
Answer Summary:
Please log in to answer
Posted by:
stavbergenstein
8 years ago
Top Answer
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.
Comments:
-
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? - stavbergenstein 8 years ago
Posted by:
EdT
8 years ago
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.
Comments:
-
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. - stavbergenstein 8 years ago
-
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. - EdT 8 years ago
Posted by:
aragorn.2003
8 years ago
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")
Posted by:
Badger
8 years ago
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.