Russian Federation
Hi guys!
I just want to tell that continuing idea of MPEM https://forum.team-mediaportal.com/categories/mediaportal-extension-manager-mpem.655/ and discussions of future of MPEI and its limitation with UAC I did some coding to make simple windows service for managing extensions.
It's still in pre-pre-alpha stage. Source code is here https://code.google.com/p/mpeiservice/source/browse/
It is using WCF communication protocol based on named pipes.
Current features are:
- install plugin by ID and version
- uninstall plugin by ID
- update known extensions list.
It's my very first look in WCF so don't expect any masterpiece in code.
Next to sources of service itself you can see little test client which can connect to service and install/uninstall plugins (Need VS compiling skills)
I compiled service so at least you could test if it could be installed https://dl.dropboxusercontent.com/u/7658963/MPEIService.zip
Service installation:
- Unpack service to your MP directory in Program Files.
- Open cmd.exe with admin rights
- Change directory to mp's and execute command "MPEIService.exe -install" (or -uninstall to delete service)
To test service you could run step by step debuggin with test client or probably use slightly changed MPEInstaller.exe from here
https://dl.dropboxusercontent.com/u/7658963/MpeInstaller.zip
Since error handling is almost missing it could fail accidently i.e. if you want to install plugin unknown to service.
Known bugs/ not yet implemented features:
- it can't get new extension list from mp site yet
- all mp processes should be closed to install/uninstall extensions.
- service only know how to install actual files and don't perform other installation actions (scripts, consecutive extension installs etc) since I'm still investigating this part of mpei
- I compiled all files against MP 1.3 so assuming most of you are using later version it could failed to work
Have fun and post comments
I just want to tell that continuing idea of MPEM https://forum.team-mediaportal.com/categories/mediaportal-extension-manager-mpem.655/ and discussions of future of MPEI and its limitation with UAC I did some coding to make simple windows service for managing extensions.
It's still in pre-pre-alpha stage. Source code is here https://code.google.com/p/mpeiservice/source/browse/
It is using WCF communication protocol based on named pipes.
Current features are:
- install plugin by ID and version
- uninstall plugin by ID
- update known extensions list.
It's my very first look in WCF so don't expect any masterpiece in code.
Next to sources of service itself you can see little test client which can connect to service and install/uninstall plugins (Need VS compiling skills)
I compiled service so at least you could test if it could be installed
https://dl.dropboxusercontent.com/u/7658963/MPEIService.zipService installation:
- Unpack service to your MP directory in Program Files.
- Open cmd.exe with admin rights
- Change directory to mp's and execute command "MPEIService.exe -install" (or -uninstall to delete service)
To test service you could run step by step debuggin with test client or probably use slightly changed MPEInstaller.exe from here
https://dl.dropboxusercontent.com/u/7658963/MpeInstaller.zip
Since error handling is almost missing it could fail accidently i.e. if you want to install plugin unknown to service.
Known bugs/ not yet implemented features:
- it can't get new extension list from mp site yet
- all mp processes should be closed to install/uninstall extensions.
- service only know how to install actual files and don't perform other installation actions (scripts, consecutive extension installs etc) since I'm still investigating this part of mpei
- I compiled all files against MP 1.3 so assuming most of you are using later version it could failed to work
Have fun and post comments
Last edited: