home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 2
General
Extension Management powered by NuGet engine
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="chefkoch" data-source="post: 1029211" data-attributes="member: 10438"><p>Sorry, but what are you trying to achieve?</p><p></p><p>Are you trying to <strong>setup your repository / project to use nuget</strong> packges, i.e. the Bass.NET dll? </p><p>This I already have prepared in my own fork of your plugin, but I am planning to improve the plugin development a bit more. Especially the references to MP2 core projects/ binaries like MediaPortal.Common , MediaPortal.Utilities etc...</p><p>I will also make sure that it my solution can be use for various plugin repos like Webradio and OnlineVideos, so it also would be easier to build those plugins by continuous integration tools.</p><p>Nevertheless, this is not related to this thread.</p><p></p><p>In case you are trying to pack your plugin into a nuget package, what this thread is about, I would say, don't do it and simply release it as a zip file.</p><p>Why?</p><p>Because we don't have any extension management in MP2 yet. NuGet can be the container for the extensions, but there needs to be a extension management developed first. I.e.</p><ul> <li data-xf-list-type="ul">a service which is able to apply changes to the ProgramFiles directory without the need for a uac window</li> <li data-xf-list-type="ul">a specification (directory structure) how files are organized inside a nuget / mp package</li> <li data-xf-list-type="ul">a gui (most likely an in-GUI plugin) which is able to<ul> <li data-xf-list-type="ul">collect infos of installed extensions and available extension</li> <li data-xf-list-type="ul">receive user input</li> <li data-xf-list-type="ul">download packages and</li> <li data-xf-list-type="ul">advice the service (point 1) to apply it</li> </ul></li> </ul><p>There are things that needs to be thought about like</p><ul> <li data-xf-list-type="ul">an extension cache (to revert to previous installed versions),</li> <li data-xf-list-type="ul">how the service/gui handles<ul> <li data-xf-list-type="ul">server and client specific plugins,</li> <li data-xf-list-type="ul">locally and on remote machines in the MP2 network</li> </ul></li> </ul><p></p><p>Unless you are targetting to think about (some of) these points and read even more <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite7" alt=":p" title="Stick Out Tongue :p" loading="lazy" data-shortname=":p" /> and work and try out concepts etc...., I suggest not to pack your plugin into nuget packages, yet.</p></blockquote><p></p>
[QUOTE="chefkoch, post: 1029211, member: 10438"] Sorry, but what are you trying to achieve? Are you trying to [B]setup your repository / project to use nuget[/B] packges, i.e. the Bass.NET dll? This I already have prepared in my own fork of your plugin, but I am planning to improve the plugin development a bit more. Especially the references to MP2 core projects/ binaries like MediaPortal.Common , MediaPortal.Utilities etc... I will also make sure that it my solution can be use for various plugin repos like Webradio and OnlineVideos, so it also would be easier to build those plugins by continuous integration tools. Nevertheless, this is not related to this thread. In case you are trying to pack your plugin into a nuget package, what this thread is about, I would say, don't do it and simply release it as a zip file. Why? Because we don't have any extension management in MP2 yet. NuGet can be the container for the extensions, but there needs to be a extension management developed first. I.e. [LIST] [*]a service which is able to apply changes to the ProgramFiles directory without the need for a uac window [*]a specification (directory structure) how files are organized inside a nuget / mp package [*]a gui (most likely an in-GUI plugin) which is able to [LIST] [*]collect infos of installed extensions and available extension [*]receive user input [*]download packages and [*]advice the service (point 1) to apply it [/LIST] [/LIST] There are things that needs to be thought about like [LIST] [*]an extension cache (to revert to previous installed versions), [*]how the service/gui handles [LIST] [*]server and client specific plugins, [*]locally and on remote machines in the MP2 network [/LIST] [/LIST] Unless you are targetting to think about (some of) these points and read even more :P and work and try out concepts etc...., I suggest not to pack your plugin into nuget packages, yet. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 2
General
Extension Management powered by NuGet engine
Contact us
RSS
Top
Bottom
