Which installer

Custom actions should not use the UI level as a condition for sending error messages to the installer because this can interfere with logging and external messages.

Use conditional statements and Conditional Statement Syntax to ensure that your package correctly runs custom actions, does not run a custom actions, or runs alternate custom action when the package is uninstalled.

Test that the package works as expected when uninstalling custom actions. For information see Conditioning Actions to Run During Removal If the installation must be capable of being run by users that do not have administrator privileges, test to ensure that all the custom actions can be run with non-administrator privileges. Custom actions require elevated privileges to modify parts of the system that are not user specific.

The installer may run custom actions with elevated privileges if a managed application is being installed or if the system policy has been specified for elevated privileges. If you use assemblies, follow good assembly practices If your package uses software assemblies , follow the guidelines for Adding Assemblies to a Package , Updating Assemblies , and Installing and Removing Assemblies.

Do not ship concurrent installations. Do not use concurrent installations to install or update a shipping product.

Concurrent installations should not share components. An administrative installation should not contain a concurrent installation. Integrated ProgressBars should not be used with concurrent installations. Resources that are to be advertised should not be installed by a concurrent installation. A package that performs a concurrent installation of an application should also uninstall the concurrent application when the parent product is uninstalled.

Give your. The product code is the principal identification of an application and must change whenever there is a comprehensive update to the application. Changing the name of the application's. The package code is the primary identifier used by the installer to search for and validate the correct package for a given installation. No two nonidentical. If a package is changed without changing the package code, the installer may not use the newer package if both are still accessible to the installer.

Note that letters in product code and package code GUIDs must all be uppercase. Installation package authors are strongly advised against using self registration and the SelfReg table. Instead they should register modules by authoring one or more of the tables in the Registry Tables Group. Many of the benefits of the Windows Installer are lost with self registration because self-registration routines tend to hide critical configuration information.

For a list of the reasons for avoiding self registration see SelfReg table. Installation package authors are strongly advised against using the TypeLib table.

Instead of using the TypeLib table, register type libraries by using Registry table. If an installation using the TypeLib table fails and must be rolled back, the rollback may not restore the computer to the same state that existed prior to the rollback. Use public properties for configuration information. Administrators can provide this information on the command-line. Do not require that the installation depend upon information gathered from user interaction with dialog boxes.

This information is not available during a silent installation. Do not automatically restart the user's computer during a silent installation. Use Digital Signatures and External Cabinet Files to ensure that the origial sources being used by the installer are secure.

An uncompressed source image stored in an public location is not secure. For information see Managing Installation Sources. Use the methods and properties of the Installer Object , Product Object , and Patch Object to retrieve and modify source list information for Windows Installer applications and patches.

Adhere to points listed in Preventing a Patch from Requiring Access to the Original Installation Source points to minimize the possibility that your patch will require access to the original sources. Store the package source files in a location that is not the system's temporary folder.

Windows Installer source files stored in the temporary folder can become unavailable to users. A very useful resource for interpreting Windows Installer log files is Wilogutl. This tool assists the analysis of log files and displays suggested solutions to errors that are found in a log file. For more information about interpreting Windows Installer log files, see the white paper available on the TechNet site: Windows Installer: Benefits and Implementation for System Administrators.

The verbose logging option should be used only for troubleshooting purposes and should not be left on because it can have adverse effects on system performance and disk space. If a file that should have been removed from the user's computer remains installed after running an uninstall, the installer may not be removing the component containing the file for one or more of the reasons described in Removing Stranded Files.

If an application must be registered, author the package to remove registry information when the application is uninstalled. If an application is not registered, the application is not listed in the Add or Remove Programs feature in Control Panel and cannot be managed by using the Windows Installer. To hide an application from the Add or Remove Programs feature in Control Panel and still be able to use the Windows Installer to manage the application, follow the guidelines described in Adding and Removing an Application and Leaving No Trace in the Registry.

Custom actions should be conditioned to run or not as needed upon uninstallation. Different custom actions may need to run on install and uninstall. User-specific customization information can be stored in a text file on the computer.

This has the advantage that the file can be removed when the application is uninstalled, even if the user of this customization is not currently logged on. Consider whether the application should be available to only particular users or all users of the computer during the development process. Test that the package works correctly for both the per-user installation and per-machine installation contexts.

Make the package easily customizable and let customers decide whether to deploy it per-user or per-machine. Consider the types of updates you expect to use to service your application in the future. The differences between these are described in Patching and Upgrades topic.

Before shipping your application, test that it works as expected after servicing with each update type. Use a delta patch to update the baseline versions of your application, such as the RTM version and the service pack versions. Follow the guidelines for using delta patches described in the topic: Reducing Patch Size. Consider providing the needed components to users as another Windows Installer installation.

The size and latency of the download required for users to obtain an update is increased compared to downloading a patch.

The entire updated Windows Installer package and source files must download, recached, and reinstalled. Users are unable to installation-on-demand and repair applications from an updated administrative installation until they recache and reinstall the application. Applying a patch to an administrative installation removes the digital signature from the package. An administrator must resign the package.

For more information about using digital signatures, see Digital Signatures and Windows Installer. Many binary patches target the RTM image of the application and require a previous file version. The local instance of an application installed from an updated administrative installation may not work with other updates.

Many binary patch applications can fail. Applying a patch to an administrative installation updates the source files and the. Users cannot determine which updates they have received from the administrative installation. This makes it impossible to sequence updates applied on the user side with those already applied on the administrative image side.

Patches applied to an administrative installation are not uninstallable patches. This can prevent the package code cached on the user's computer from becoming different than the package code on the administrative installation. If the package code cached on the user's computer becomes different from that on the administrative installation, reinstall the application from the administrative installation and then patch the client computer.

Silent Installation The installer can be executed in silent mode by executing the package with the -s flag. Table 3. Driver Subpackages Display. Required to run CUDA applications. Extracting and Inspecting the Files Manually Sometimes it may be desirable to extract or inspect the installable files directly, such as in enterprise deployment, or to browse the files before installation.

Note: Accessing the files in this manner does not set up any environment settings, such as variables or Visual Studio integration. This is intended for enterprise-level deployment. The installation steps are listed below. Installation To perform a basic install of all CUDA Toolkit components using Conda, run the following command: conda install cuda -c nvidia. To verify a correct configuration of the hardware and software, it is highly recommended that you build and run the deviceQuery sample program.

Figure 1. Figure 2. If your pip and setuptools Python modules are not up-to-date, then use the following command to upgrade these Python modules.

If these Python modules are out-of-date then the commands which follow later in this section may fail. Install the CUDA runtime package: py -m pip install nvidia-cuda-runtime-cu The following metapackages will install the latest version of the named component on Windows for the indicated CUDA version.

These metapackages install the following packages: nvidia-nvml-dev-cu nvidia-cuda-nvcc-cu nvidia-cuda-runtime-cu nvidia-cuda-cupti-cu nvidia-cublas-cu nvidia-cuda-sanitizer-api-cu nvidia-nvtx-cu nvidia-cuda-nvrtc-cu nvidia-npp-cu nvidia-cusparse-cu nvidia-cusolver-cu nvidia-curand-cu nvidia-cufft-cu nvidia-nvjpeg-cu Compiling Sample Projects The bandwidthTest project is a good sample project to build and run.

Sample Projects The sample projects come in two configurations: debug and release where release contains no debugging information and different Visual Studio projects. A few of the example projects require some additional setup. Table 4. Alternatively, you can configure your project always to build with the most recently installed version of the CUDA Toolkit.

First add a CUDA build customization to your project as above. Then, right click on the project name and select Properties.

Notices Notice This document is provided for information purposes only and shall not be regarded as a warranty of a certain functionality, condition, or quality of a product. Windows Windows Server MSVC Version x. Visual Studio CUDA Runtime libraries. Extracts information from cubin files. I was wondering how to find the installers that other applications use by just having the executable. I don't really want to use a third party tool to repackage right now. I want to be able to script most of the install.

I would like to be able to install and uninstall. There maybe better ways but I use Universal Extractor. Even if it can't extract the files it will ID the program used to create the executable. Then I search for silent install parameters, etc. Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Windows Installer 4. If all the packages in the transaction cannot be installed successfully, or if the user cancels the installation, the Windows Installer can roll back changes and restore the computer to its original state. The installer ensures that all the packages belonging to a multiple-package transaction are installed or none of the packages are installed. Beginning with Windows Installer 5.

The package can specify a security descriptor that denies permissions, specifies inheritance of permissions from a parent resource, or specifies the permissions of a new account.

For information, see Securing Resources. The Windows Installer 5. For more information, see Enumerating Components. Setup developers can use Windows Installer 5. Windows Installer enables the efficient installation and configuration of your products and applications running on Windows. The installer provides new capabilities to advertise features without installing them, to install products on demand, and to add user customizations. Windows Installer 5.

A Windows Installer package, patch, or transform that has not been signed by Microsoft cannot be installed on Windows RT. The Template Summary property indicates the platform that is compatible with an installation database and in this case should include the value for Windows RT.