spacer spacer

Desktop Ticker



Deployment Guide

 

Configuration Files

The Desktop Ticker application stores data in three XML files. Feeds.opml stores the list of RSS feeds, History.xml stores the list of items that have been hidden, and Settings.xml stores the configuration data. The default location of these files is in the user profile folder ("%APPDATA%\Desktop Ticker"). Unticking the "Store Settings in User Profile" option on the File menu will cause the application to store the settings in the same folder as the DesktopTicker.exe executable file. This is achieved by creating a file called DesktopTickerSaveLocal in this folder. When Desktop Ticker is run it checks for the presence of this file, and if found it will use the settings stored in the same folder. Running the application this way allows multiple users to share the same configuration.

 

Locking the settings

Desktop Ticker checks if it is able to write to the four files, Feeds.opml, History.xml, Settings.xml and DesktopTickerSaveLocal. If it cannot write to any of these files then the corresponding options/features in the application are disabled, for example if the Feeds.opml file is read-only then the user will not be able to edit the list of RSS feeds.

 

Note that if Common Feed List synchronisation is enabled, users will be able to modify the feed list using other applications even if the Feeds.opml file is read-only.

 

Removing the Yahoo! Finance feed

The Yahoo! Finance feed is added each time the application is run to provide a simple way to get stock information. To prevent this feed from being shown, run the application with the /NOSTOCKS switch.

 

DesktopTicker.exe /NOSTOCKS

 

Disable the upgrade notification

By default, an upgrade notification is displayed when a new version of the application is released. To disable this, click the Menu button and go to Help -> About, then untick the "Check for updates at startup" option.

 

Running from a network location

By default, the .NET Framework assigns a restricted set of permissions to applications run from a network location. This restriction causes Desktop Ticker to fail, so client computers require a configuration change to run it in this way.

 

The Code Access Security Policy tool can be used to assign to required permissions to the Desktop Ticker executable file. An example is below.

 

CasPol -m -ag 1.2 -url "file://\\sharename\foldername\DesktopTicker.exe" FullTrust

 

CasPol Tool

 

By default, CasPol will prompt the user for confirmation. To run as part of a script, this confirmation can be disabled by running the following command beforehand:

 

CasPol -pp off

 

Afterwards run the following command to restore the default behaviour:

 

CasPol -pp on

 

More information on the Code Access Security Policy tool can be found on the MSDN website here.

 

Donate

 

If you like Desktop Ticker please consider making a donation via PayPal or take a moment to leave a comment or review on a website.
  
Donate your computer's spare power to scientific research. Join World Community Grid today! BOINC: compute for science

 

Back

 

 

Copyright © 2016 Mike Batt