Reply to thread

Message

<blockquote data-quote="chefkoch" data-source="post: 1011912" data-attributes="member: 10438">Question is: can other skins register themselves to your plugin? to prevent the need for shipping this plugin specially designed with every skin?&nbsp;Even if some people do not like to hear this: But such limitations are a result of the MP1 architectural design. It's not required to implement such functionality into the core application just to make it available. Having it as a plugin the right thing. If it is not possible for other plugins to reference it or register themselves to this plugin, then there is something wrong (in general, not in your particular case <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink&nbsp; &nbsp; ;)" loading="lazy" data-shortname=";)" /> , because it might not be possible to do such things in MP1, I don't know).&nbsp;But in the beginning the very first basics should be covered: Downloading, installing and uninstalling of packages including their dependencies, a package specification and an online component that is able to serve the packages that have been uploaded. A tool that is able to build and upload packages.If these things are well designed, well structured and reliable, it can be implemented and used in GUI plugins and WPF application and extended with other components, maybe things like the incremental svn/git updater or a logo manager. But package management core is the most important part, imo.&nbsp;WiX itself is very powerful, I like it and imo it's the most reliable installation framework that is available without any costs. NSIS is can not be compared if you have more advance installation needs and requirements like reliability and logging, ...)&nbsp;Nevertheless I agree to your points about documentation and debugging.</blockquote>

[QUOTE="chefkoch, post: 1011912, member: 10438"] Question is: can other skins register themselves to your plugin? to prevent the need for shipping this plugin specially designed with every skin? Even if some people do not like to hear this: But such limitations are a result of the MP1 architectural design. It's not required to implement such functionality into the core application just to make it available. Having it as a plugin the right thing. If it is not possible for other plugins to reference it or register themselves to this plugin, then there is something wrong (in general, not in your particular case ;) , because it might not be possible to do such things in MP1, I don't know). But in the beginning the very first basics should be covered: [B]Downloading[/B], [B]installing[/B] and [B]uninstalling[/B] of [B]packages[/B] including their [B]dependencies[/B], a [B]package specification[/B] and an [B]online component[/B] that is able to serve the packages that have been uploaded. A tool that is able to [B]build[/B] and [B]upload packages[/B]. If these things are well designed, well structured and reliable, it can be implemented and used in GUI plugins and WPF application and extended with other components, maybe things like the incremental svn/git updater or a logo manager. But package management core is the most important part, imo. WiX itself is very powerful, I like it and imo it's the most reliable installation framework that is available without any costs. NSIS is can not be compared if you have more advance installation needs and requirements like reliability and logging, ...) Nevertheless I agree to your points about documentation and debugging. [/QUOTE]

Verification