Notepad++ Convert to MSI
-
How Can I Using Command Prompt Convert File
-
Could you be a little more specific about what exactly you want to achieve?
-
@ekopalypse Can I use the tools that come with Windows to convert it into an msi installation package
-
@mre819 ,
Notepad++ already comes bundled in an executable installer; there is no reason that I know of to want it in an MSI installer instead, because an executable installer can do everything necessary to install Notepad++.
If you can explain why MSI is better , or allows something different than EXE, please share that knowledge. (But if you already know that, then you apparently know more about MSI than we do.)
The developer obviously chose NSIS->Executable instead of MSI or other installer solutions for a reason. So Notepad++ doesn’t officially support MSI, or any other install method other than the NSIS-created EXE or the distributed ZIP- and 7z-based portable versions. That, combined with the fact that “how to convert exe installer to msi” is really more of a Windows/programming question than a Notepad++ specific question, means that your question is technically off-topic.
edit: rephrased second and third paragraphs
-
@peterjones said in Notepad++ Convert to MSI:
there is no reason that I know of to want it in an MSI installer
There must be some reason, because people keep asking for this. :-)
-
@alan-kilborn said in Notepad++ Convert to MSI:
There must be some reason
Then I wish someone would explain why MSI is better.
Searching the forum for MSI, I see that I at least once said MSI when I should have said NSIS; whoops. I do see a few times where people were asking about an MSI… though a lot more times of people who apparently have rolled their own MSI, or have (like me) mistakenly called the executable installer an MSI when it’s not. But given that some people roll their own, it’s too bad none of them have shared how they did that.
-
@peterjones said in Notepad++ Convert to MSI:
why MSI is better.
A couple of quick web searches and reading headlines and skimming a couple paragraphs, especially at:
Apparently, MSI are good at integrating with ActiveDirectory setups (so makes it easier for IT to deploy to all users).
NSIS (what Notepad++ uses) and InnoSetup (another common mention) both output EXE, whereas WIX is a free .MSI generator. And there apparently do exist tools (free or otherwise) which claim to be able to take executable installers and convert to MSI installers. InstallShield apparently can generate either, though it seems to embed the MSI in the EXE when it generates an EXE.
-
I said (in my rephrased version):
means that your question is technically off-topic.
But we obviously found it more interesting upon reflection. My further research provides some links that may allow you to convert the executable to MSI format, or at least gives you further places you can study, to see if those techniques will work in the Notepad++ installer circumstances.
If you ever come back to look at replies, I hope you are able to explain why you want the MSI as opposed to the executable installer. And maybe some day, those who want MSI, or those who are active in the “deployment” realm of IT, can help us make a FAQ entry for “how to easily deploy a customized Notepad++ installation to hundreds of users”, which is where I think your question was eventually leading (and is similar to other requests)
-
@peterjones I hope to deploy notepad++ through mdt, which is more efficient
-
@peterjones The main reason a MSI file is asked for is that they are used when distributing software using a deployment solutions in an organisation, most commonly Microsoft SCCM or deploying software using ActiveDirectory.
For example, I repackage software that do not offer a MSI file so that I can distribut them within my organisation by running the installer and a repackage software that analyse what changes the installer makes to the system and then compile those changes to a MSI-file.
The best solution is off cause if a MSI-file is offered from the creator.With a MSI file we can easy do a silent install, we can repair the software using built in MSI solutions, uninstall silently, version controll, have a log file created and modify settings like disable automatic updates using a Transform file (as it’s something organisations do not want to have enabled as users usually do not have admin access to the local computer and therefor can’t install any updates to the program).
A MSI-file can also easily be converted to a file format compatible with Intune distribution (Microsoft offeres free software for converting).I hope this explains why IT-professionals ask for MSI-files.
