Menu
▾
▴
[NSIS-Bugs] [ nsis-Feature Requests-867084 ] Ability to Create MSI Packages
|
From: SourceForge.net <no...@so...> - 2005-07-21 10:33:34
|
Feature Requests item #867084, was opened at 2003-12-29 15:19 Message generated for change (Comment added) made by shiphrah You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=373088&aid=867084&group_id=22049 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: General Group: None Status: Open Priority: 1 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Ability to Create MSI Packages Initial Comment: Adding the ability to create Microsoft Installer packages (MSI) would be very beneficial for the project. What I envision is using NSIS to script a number of registry changes and basic system configuration settings, then using Group Policy to deploy the bundle. Unfortunately, this currently requires the package to be in an MSI format. Additionally, there are no light weight nor inexpensive products to create MSI's, and there is definitely a need for one. This link is to the MSDN content for Windows Installer, which includes the MSI information. http://msdn.microsoft.com/library/default.asp?url=/library/en-us/msi/setup/roadmap_to_windows_installer_documentation.asp ---------------------------------------------------------------------- Comment By: Juergen Hofmann (shiphrah) Date: 2005-07-21 12:33 Message: Logged In: YES user_id=1160914 The GUI is realized with a fragment (actually assembled via dark, Orca, MSI SDK samples, manually). We use the same UI fragment for all setups, configuring it as needed via properties. dark will give you a good start for the UI. We don't need multiple languages for MSI, but it's more or less easy to do with Wix. The only thing that's probably not possible is to support multiple languages in one MSI, but you would have to supply one MSI for each language. But perhaps somebody has an idea how to do it. ---------------------------------------------------------------------- Comment By: Leonard Ritter (paniq) Date: 2005-07-21 12:05 Message: Logged In: YES user_id=337105 how do you set up a GUI for WiX? are you making use of multiple languages? where do you take those resources from? ---------------------------------------------------------------------- Comment By: Juergen Hofmann (shiphrah) Date: 2005-07-21 11:18 Message: Logged In: YES user_id=1160914 Have a look at http://wix.sourceforge.net. For my projects I use a little tool which builds setups with both NSIS and WiX (thus MSI). It's up to the customers which one they prefer and actually there seems to be a need for both. I prefer to see NSIS keep small and efficient. ---------------------------------------------------------------------- Comment By: Leonard Ritter (paniq) Date: 2005-07-21 10:58 Message: Logged In: YES user_id=337105 actually i didnt mean parachute. i meant paper umbrella. i'm so worthless. ---------------------------------------------------------------------- Comment By: Leonard Ritter (paniq) Date: 2005-07-21 10:55 Message: Logged In: YES user_id=337105 nsis is completely useless for anything that is targeted for automated deployment. therefore it cant be considered for non-consumer deployment. on the other hand, the nsis scripting language/vm is well established. the script could be translated to an msi database, and as you are the people most familiar with the insides of nsis scripting, it would be an easy task writing an nsis script -> msi xml translation tool (check WIX, an xml->msi compilation tool, also released on sf.net). i'm aware that your precious vm is effectively not being used, but that doesn't narrow down the extreme usefulness of your scripting language. nobody expects you to create an actual msi builder. just writing tools for helping with the transition would be benefitial to everybody. if you keep being ignorant towards this requirement, nsis will go down the drain. the only reason why our company can't use your product is exactly this. why is this priority 1? you should at least think about it. hard. with a drink in your hand. which contains a parachute. and ice. as nsis rocks. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2004-08-26 23:26 Message: Logged In: NO Cool idea but MSI does not Compile the Files like NSIS does. with MSI the files have to be inrange to Install the files ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2004-04-06 09:29 Message: Logged In: NO For a project I'm working on, we needed an installer. I tried out NSIS 2.0 and found it exceptional, except for one thing: It couldn't create MSI packages. While we don't need that right now, we don't want to remove the option for us, in case we may need it in the future. Hence, the only reason for not chosing NSIS for our project is the lack of MSI support. - Tue Wennerberg ---------------------------------------------------------------------- Comment By: Joost Verburg (joostverburg) Date: 2004-03-22 08:23 Message: Logged In: YES user_id=604457 NSIS is an installer system with an own installer VM and script language. That makes it small, quick and efficient. If you want a new tool to create MSI packages, you should start another open source project. This would be a totally different thing. ---------------------------------------------------------------------- Comment By: George Tsiokos (gtsiokos) Date: 2004-03-22 05:32 Message: Logged In: YES user_id=543781 Since non-MSI installers are non-Windows 2000, XP, and 2003 logo compliant, perhaps a "totally different engine" should be considered. MSI is the manageable installer technology administrators have been looking for. Adobe has made the leap with Acrobat 6 making it painless to deploy in an organization. ---------------------------------------------------------------------- Comment By: zarg (zarg) Date: 2003-12-30 23:55 Message: Logged In: YES user_id=145909 Windows 2000 comes with its own light weight MSI creator package, it can be found on the cd under \valueadd\3rdparty\mgmt\winstle. They also have an MSI editor called Orca which can be downloaded from http://www.microsoft.com/msdownload/platformsdk/sdkupdate /. There is an open source MSI creators called MakeMSI http://www.labyrinth.net.au/~dbareis/makemsi.htm ---------------------------------------------------------------------- Comment By: Joost Verburg (joostverburg) Date: 2003-12-30 22:21 Message: Logged In: YES user_id=604457 NSIS has it's own VM and creates installers that do not require MSI. A system that creates MSI files would be something totally different. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=373088&aid=867084&group_id=22049 |
