Reply to thread

Message

<blockquote data-quote="sa_ddam213" data-source="post: 1012114" data-attributes="member: 89205">I am happy to go the Nuget direction. and as I see it MPEM would:&nbsp;1. Have a Data connection to both MP and TVServer for installing/updating plugins via the MPEM InstallerService2. Will be the only way to install plugins(other than a possible GUIWindow version hosted inside MP)3. If any plugin components need to be installed on a machine other than MP or TVServer the developer could host that installer separately on their own website or add a function inside MPEM to extract that installer to a specified directory for that user to copy to the designated machine to continue installation.&nbsp;If everyone is happy with those 3 points I think we should just go ahead with the Nuget approach, as like you said the benefits around dependencies versioning is great and if it can be hosted easily on the website side then it seems like a no brainer.</blockquote>

[QUOTE="sa_ddam213, post: 1012114, member: 89205"] I am happy to go the Nuget direction. and as I see it MPEM would: 1. Have a Data connection to both MP and TVServer for installing/updating plugins via the MPEM InstallerService 2. Will be the only way to install plugins(other than a possible GUIWindow version hosted inside MP) 3. If any plugin components need to be installed on a machine other than MP or TVServer the developer could host that installer separately on their own website or add a function inside MPEM to extract that installer to a specified directory for that user to copy to the designated machine to continue installation. If everyone is happy with those 3 points I think we should just go ahead with the Nuget approach, as like you said the benefits around dependencies versioning is great and if it can be hosted easily on the website side then it seems like a no brainer. [/QUOTE]

Verification