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 1
MediaPortal 1 Plugins
MPEM Development Info & Testversion
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="offbyone" data-source="post: 1011791" data-attributes="member: 73415"><p>I want to give my warnings about this approach (having done a few wix installers in the past).</p><p>WIX is basically a XML wrapper around Windows Installer and therefore comes with the limitations and problems of it.</p><p> </p><ul> <li data-xf-list-type="ul">The Visual Studio extensions will not install on the Express edition that many extension devs use.</li> <li data-xf-list-type="ul">Skinner usually don't use Visual Studio and won't install it to create their package.</li> <li data-xf-list-type="ul">There is no graphical designer that will create the wix xml files.</li> <li data-xf-list-type="ul">Windows Installer is build into Windows, but is on the user`s PC in many different versions depending on OS an ServicePack Level. You have to be careful what feature you are using.</li> <li data-xf-list-type="ul">Creating a nice UI for the actual Installer that will be unique for every installer that is for MPEM will be a lot more work than doing a custom WPF app.</li> <li data-xf-list-type="ul">The feature set of Windows Installer is rich, but extensibility is not one of its strengths. I am unsure how you are planing to implement things like package dependencies (checking, auto download dependent ones). Best guess will be a swarm of custom actions, which every plugin will have to integrate again.</li> <li data-xf-list-type="ul">Creating packages must be done careful - it is easy to create MSI that will not uninstall due to some task failing at uninstall - since Windows Installer is a database we have no control over - a failed installer will stay in the users "AddRemovePrograms" and we have no chance to ever remove it plus this user wont be able to install that extension again if it uses the same ID.</li> </ul><p></p><p>I can probably think of some more points, but you get my general concern I guess. Not saying it is not possible to use MSI via WIX, just want to save you from what might be too much stress to implement. Using XML for package definition is not a real advantage of WIX - even current MPEI uses it <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink ;)" loading="lazy" data-shortname=";)" /></p></blockquote><p></p>
[QUOTE="offbyone, post: 1011791, member: 73415"] I want to give my warnings about this approach (having done a few wix installers in the past). WIX is basically a XML wrapper around Windows Installer and therefore comes with the limitations and problems of it. [LIST] [*]The Visual Studio extensions will not install on the Express edition that many extension devs use. [*]Skinner usually don't use Visual Studio and won't install it to create their package. [*]There is no graphical designer that will create the wix xml files. [*]Windows Installer is build into Windows, but is on the user`s PC in many different versions depending on OS an ServicePack Level. You have to be careful what feature you are using. [*]Creating a nice UI for the actual Installer that will be unique for every installer that is for MPEM will be a lot more work than doing a custom WPF app. [*]The feature set of Windows Installer is rich, but extensibility is not one of its strengths. I am unsure how you are planing to implement things like package dependencies (checking, auto download dependent ones). Best guess will be a swarm of custom actions, which every plugin will have to integrate again. [*]Creating packages must be done careful - it is easy to create MSI that will not uninstall due to some task failing at uninstall - since Windows Installer is a database we have no control over - a failed installer will stay in the users "AddRemovePrograms" and we have no chance to ever remove it plus this user wont be able to install that extension again if it uses the same ID. [/LIST] I can probably think of some more points, but you get my general concern I guess. Not saying it is not possible to use MSI via WIX, just want to save you from what might be too much stress to implement. Using XML for package definition is not a real advantage of WIX - even current MPEI uses it ;) [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
MediaPortal 1 Plugins
MPEM Development Info & Testversion
Contact us
RSS
Top
Bottom