Reply to thread

Message: <blockquote data-quote="chefkoch" data-source="post: 1012086" data-attributes="member: 10438">The point is: your concept having the MPEM browser and the MPEM UpdaterService are definitely required components. These perfectly fit into a Extensions Management concept, but how do you plan to define dependencies between plugins, additional specific versions or version ranges. This is fundamental for the extension management, and I think here is already a lot of work done by the NuGet.Core. NuGet packages itself are no executables, these are just zip files having a different file extensions and containing the files that have been defined to be packed into the package of course <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink    ;)" loading="lazy" data-shortname=";)" /> and the metadata. Using the NuGet core it should be possible to read such metadata applications like the MPEM browser and MPEM Updateservice.The good thing is the metadata is the same specification inside the nuget package as well as when creating the package or when retrieving the available inforamtion from the nuget gallery (website). Like I already wrote in the other thread I am very sorry I can not help with working actually on this topic, current, even not on the nuget area, as I am finishing my studies these weeks and still have a lot to do to make it in time, but other than using NuGet for development dependencies I also did not work more with it, yet. So my knowledge about using it in your own application is the same as yours, nevertheless I believe this is the worth to take a look at it even if it takes some time.I would understand if you don't want to put so much efforts into it when working alone, so it would be great if there are others who could contribute and support you.I was asked for my opinion and wrote it down, the concerns about Wix and an alternative which comes with a versioning and dependency concept, a package creator, a server component for hosting the packages and a gallery for browsing these online. It's your decision, you also can go the WiX route and if you prove it's working the team will be happy to have it. The offer I can make from my side is assisting in any overall questions, do some testing and reviewing concepts and code, but I won't be able to take over any development tasks this year anymore.</blockquote>

Verification