Austria
- Moderator
- #1
ATTENTION: Please Ignore the instructions below. Due to some errors, we decided to do a static class named MediaPortal.Util.Config instead.
Hi fellow developers,
maybe you have noticed already the new way how logging is done, since a few weeks, using the Service Provider.
We have enhanced the Service Provider, to deal with Configurations.
At the moment it is only used to store Path Information for MediaPortal.
This allows us to specify for example a ConfigPath, where all the xml files are stored, instead of the Root directory of MediaPortal.
So please adjust your Plugins, to use the new model, since after a testing period, we will move all our xml files to a Config Path and you never can't rely on finding mediaportal.xml in the same directory as mediaportal.exe.
Configuration of the various Path information is done in MediaPortalConfig.xml.
Never modify this file itself, as it is a fallback. Instead, copy it to your MyDocuments\Team MediaPortal.
Please have a look at the Wiki on how to use the Service Provider.
have fun,
Helmut
Hi fellow developers,
maybe you have noticed already the new way how logging is done, since a few weeks, using the Service Provider.
We have enhanced the Service Provider, to deal with Configurations.
At the moment it is only used to store Path Information for MediaPortal.
This allows us to specify for example a ConfigPath, where all the xml files are stored, instead of the Root directory of MediaPortal.
So please adjust your Plugins, to use the new model, since after a testing period, we will move all our xml files to a Config Path and you never can't rely on finding mediaportal.xml in the same directory as mediaportal.exe.
Configuration of the various Path information is done in MediaPortalConfig.xml.
Never modify this file itself, as it is a fallback. Instead, copy it to your MyDocuments\Team MediaPortal.
Please have a look at the Wiki on how to use the Service Provider.
have fun,
Helmut