Start Menu Shortcut & config.xml

[Ommina]

OK, forgive me if these have already been covered, but "start menu" and "config.xml" are not especially rare terms.

So - two questions, guess both for you sub:

First. My plugin has an external exe for a long-running process that is inappropriate to perform inside the config application. I would like to provide a a shortcut to this .exe on the start menu, ideally under "Programs | GB-PVR | Third Party | name".

I'm hoping the "Third Party" will be sufficient to let users know that what follows is not part of the base GB-PVR installation, and, as such, is not your problem, but I would like to clear it with you first. Creating its own folder under programs is an option of course, but as a GB-PVR plugin, it makes more sense to me to keep it all together.

Second. If a plugin makes changes to config.xml (under the appropriate <PluginSettings> node), will the changes be kept, or am I risking them being overwritten? (Hmm, I suppose I could just try it and find out...)

[sub]

First. My plugin has an external exe for a long-running process that is inappropriate to perform inside the config application. I would like to provide a a shortcut to this .exe on the start menu, ideally under "Programs | GB-PVR | Third Party | name".

I'm hoping the "Third Party" will be sufficient to let users know that what follows is not part of the base GB-PVR installation, and, as such, is not your problem, but I would like to clear it with you first. Creating its own folder under programs is an option of course, but as a GB-PVR plugin, it makes more sense to me to keep it all together.

I've got no objections to you creating the shortcuts there.

Second. If a plugin makes changes to config.xml (under the appropriate <PluginSettings> node), will the changes be kept, or am I risking them being overwritten? (Hmm, I suppose I could just try it and find out...)

It does try to retain these settings during upgrades.

[Ommina]

I've got no objections to you creating the shortcuts there.

Thanks - then I shall! (In fact, have.)

It does try to retain these settings during upgrades.

I'm more concerned with day-to-day operations.

Essentially, I want to maintain some user state information between restarts of GB-PVR. In my case, a single entry in the config.xml file is sufficient. But I don't know what kind of behaviour to expect from the config.xml between the time I make my change, and the user exiting the PVR. In short, if I, inside the plugin, make a change in 'my' section of <PluginSettings>, am I risking that change being overwritten later?

I did try the XmlDocument returned by pluginhelper.GetDocument, thinking it might work like the document provided to the config form, but didn't have much luck. (Or I missed a step.)

Would I be better off just creating a table in (my plugin's) db3 and store it there?

[sub]

Essentially, I want to maintain some user state information between restarts of GB-PVR. In my case, a single entry in the config.xml file is sufficient. But I don't know what kind of behaviour to expect from the config.xml between the time I make my change, and the user exiting the PVR. In short, if I, inside the plugin, make a change in 'my' section of <PluginSettings>, am I risking that change being overwritten later?

I'd only use the config.xml for storing configuration, not state related stuff. Your plugin should treat the config.xml as read only except when accessed via a configuration form in the config app.

You should store state in the registry or a file or a database.

I did try the XmlDocument returned by pluginhelper.GetDocument, thinking it might work like the document provided to the config form, but didn't have much luck. (Or I missed a step.)

PluginHelperFactory.GetInstance().GetConfiguration() should return you the XmlDocument holding config.xml.