I am working on a project where it needs to create a setup file (.msi) which install require third party driver during my setup of windows application.
Let me clear with example.
My application setup file - "mysetup.msi"
Other third party setup files - "installer.ini"
Is it possible that mysetup.msi automatically execute the setup for third party so my end user do not need to worry about the third party installation to use my software???
If you are installing drivers your best bet is to use DifXApp, the MSI version of the Driver Install Frameworks. Wix and InstallShield include these out of the box.
Related
Is this command required to enable saml in Liberty server?
bin/installUtility install samlWeb-2.0
I have configured <feature>samlWeb-2.0</feature> in my server.xml and able to get metadata file using the url https://ip:port/ibm/saml20/defaultSP/samlmetadata
It's <feature>samlWeb-2.0</feature> that enables the feature, but you can't enable what you don't have, which is where bin/installUtility would come in (if necessary).
Liberty is available in several packages which dictate which set/sub-set of features are available immediately after installation (custom packages of Liberty can also be created to further customize the available set of features available to the runtime). Features that are not included in the package can be installed afterwards using bin/installUtility (bin/featureManager has been deprecated).
The command bin/installUtility install samlWeb-2.0 retrieves (from a repo) and installs the samlWeb-2.0 feature if it wasn't already installed in your Liberty runtime. For example, if the Liberty package was that of just the Liberty Kernel, than bin/installUtility install samlWeb-2.0 would download the samlWeb-2.0 feature along with all other pre-req features. However, if your Liberty package was that of the entire Base edition (wlp-base-all) than it would already include the samlWeb-2.0 feature and you would not need to run bin/installUtility prior to enabling it.
I've developed an application for Hololens, so the only way I know to install the application in hololens is by visual studio, so I want an application package to be able to install without needing Visual Studio. I tried to follow this tutorial here
"https://learn.microsoft.com/pt-br/windows/uwp/packaging/create-app-package-with-makeappx-tool"
but I can not find these two .appx and .appxsym files.
If anyone knew, I appreciate that.
Maybe you know some steps, but I will go the full way (it's only deploying without visual Studio):
In Unity:
File> Build Settings
Choose Universal Windows Plattform (older Versions Windows Store). Make sure your settings are right (for hololens, sdk enabled...)
hit "Build"
Now you have to select a Folder to build. In my Projects I create just an "App" Folder
Once it is build navigate to this Folder (if it's not opening automatically).
Open the Solution (in the App Folder, not the Unity one)
In the Explorer right Click on the "Project Properties" which are named like your Project and Select "Store>create App Package (or maybe build, i got it on German)"
If you want only the appx File select "no" at the Windows Store question
Select an Output Folder and Version Number (count's up itself, newer numbers will overwrite older versions on Hololens automatically) and for Hololens only select x86 (the others are not needed. Just consume time). Now hit the "create"(again i hope i translate it right) Button.
Apply on Hololens:
Connect the hololens via USB (you can do it with wifi too, but not in our Network, so i never tried)
Open a browser and type "127.0.0.1:10080" so you get access to your hololens
Navigate to "System>Apps" and under Install App select the appx file (in my case under: (myUnityProject/App/AppPackages/myUnityProject/myUnityProject_1.0.0.0_Win32_Master_Test)
First time deploying select the dependencies (Dependencies/x86)
Hit "go" to Deploy (wait until everything is uploaded)
Some Notes:
To build the Apps i needed mvs 2015 installed (just installed), but this was before the Fall creators Update. Now newer Versions (should) work fine. Also I needed to install the windows "buildtools 2015"
https://www.microsoft.com/de-de/download/details.aspx?id=48159
Hope it works and have fun!
I have an open source tool that I want to make available from Chocolatey. Right now the application is just an EXE and config file (and a couple extra dlls). Can I build a package for just these files or do I need to create an installer first? If I can do it without the installer, is there an example of this? If using a MSI is a better practice, I can create one.
Thanks,
Mike
Yes, you can create a package just for those files without creating an installer first.
Those kind of packages are usually referred to as portable packages (packages that do not require administrative privileges to install).
Basically all you need to do, is add the files inside the package, create a VERIFICATION.txt file which details how moderators can verify the binaries (remember to also include that you're the software author), and a LICENSE.txt (can be named differently) with the license of the software.
An example of such a package would be my own package for electrum-ltc.portable:
https://chocolatey.org/packages/electrum-ltc.portable
I am trying to install a PKCS#11 module into Mozilla Firefox via an MSI setup application. After doing some search through the internet, I bumped into the modutil tool which has a wide variety of responsibilities especially in my case for installing / uninstalling the PKCS#11 module to NSS security databases. I downloaded the latest source code of modutil and built it using MozillaBuild.
Also, I writing a C code to add module to database using secmod_addnewmodule, which returns "-1" as a error.
Following is my code to add module where configdir is the path to secmoddb database.
int rv = NSS_Initialize(configdir, "", "", SECMOD_DB, NSS_INIT_FORCEOPEN );
hr = SECMOD_AddNewModule("test","D:\\Pkcs\\PKCS11_VSC.dll",internalMechanismFlags,internalEnableFlags);
Does anybody know how I can overcome this issue, and is there any unseen aspect to work with this utility. Also, is there a solution to install/uninstall pkcs#11 module for all user profiles with one common process. Finally, is there a better solution to do the task of installation using my setup. I am using WiX Toolset to create MSI setup
if NSS_Initialize fails to open secmod database we cannot add the module to database.
the nss library automatically takes the default flags required for adding database.
secmod _deletemodule deletes the module which is added to the database.
For Linux packages, specifically RPMs with stored checksums, we always can check two things: the contents of package is ok and the installation from this package is ok. When someone modifies parts of the installation he shouldn't, we can see it by running rpm -Vp my-precious-package. In our busyness it is not only recommended, but obligatory to provide our packages with tools for this purpose and for Linux these are just simple bash scripts.
Now I have to do something similar for Windows. Basically what I want is to provide some batch file by running which one can get assured, the installation is the same as it meant to be in the package. I'm using InstallShield for packaging, and yet it has some great visual tools, I still haven't found a way to verify package checksums in the command line.
Is it even possible, or should I reinvent the wheel writing my own checking utils?
Take a look at MakeCat and SignTool from Microsoft, both in SDK
http://msdn.microsoft.com/en-us/library/windows/desktop/aa386967%28v=vs.85%29.aspx
http://msdn.microsoft.com/en-us/library/windows/desktop/aa387764%28v=vs.85%29.aspx
Windows Installer has a feature called resiliency that supports auto repair of products and there are ways to call it for self checks only. (This is assuming by InstallShield you mean Windows Installer based projects.)
Here's a couple links to read to get you started:
INFO: Description of Resiliency in Windows Installer
Resiliency
Application Resiliency: Unlock the Hidden Features of Windows Installer
MsiProvideComponent function (See dwInstallMode flags)
This also assumes all files are key files. Companion files are not managed by the installer. Also changes performed by custom actions outside of the installer aren't managed.