Create install file visual studio

Instead, I used this method: Close all but one instance of Visual Studio. Jazimov Jazimov I would need more information than "not working". Setup project required. Net Framework 4. Win 7 SP1 only Supporting 4. Net Version on VS Community edition? Antosujesh I have also faced same issue. I searched for 4. And also updated DefaultLocation.

What is the difference between this answer and the higher answer? Show 2 more comments. Sign up or log in Sign up using Google.

Creates a CAB file for downloading to an earlier Web browser. Unlike the other deployment project types, there are no editors provided for working with Cab projects.

Files and project outputs can be added to a Cab project in Solution Explorer, and properties can be set in the Properties window or in the Project Property pages. After the wizard has finished, now you have completed to create an installer for your application. Now save all changes and start to build your application, if building completed successfully, build the installer.

Go to where you have saved the solution and you will see an installer file inside the debug folder in your setup project directory. But I think this is not enough for you! You need to go deeper in customization, so follow me in the following issues:. The deployment editors are used to configure an installer that you create with a deployment project. To open an editor, select a deployment project and the buttons will appear as shown below or alternatively, right-click your deployment project, point to View, and then click the name of the editor that you want to open.

File system editor; When the project is added to the solution, the first thing to be displayed is the file system editor. The picture above shows file system editor. To put shortcut of your application in start menu or desktop go to application folder , right click on primary output from … Or any other files which you want to create shortcut for them , select create shortcut to… then the shortcut will appear, cut it and paste to the folder where you want a shortcut to appear.

Also you can add project outputs in the target folder using the same way explained below just select project output… instead of a file. The user interface editor helps you to customize the installation wizard interface.

The Install section contains dialog boxes that will be displayed when the end user runs the installer; the Admin section contains dialog boxes that will be displayed when a system administrator uploads the installer to a network location. The Registry Editor allows you to specify registry keys and values to be added to the registry of the target computer. Playing with registry need more experienced person otherwise it may course some trouble in target computer, but you can add or remove keys according to what your project needs.

To add a registry key select a top level node, in the action menu click new key , then type the new name and edit properties of the key in the properties window as necessary. To add a sub key select a key node, in the action menu point to new and then key and you can edit its properties from the properties window. Also you can remove a key by selecting it and then click Delete from Edit menu. During installation the values will be written to the registry and any existing values will be overwritten by the values that you specify.

Here you can specify additional actions to be performed on the target computer at the end of an installation. When these components are configured as installation components, they are wrapped in an installer class and are recognized by the deployment system as a custom action. The editor contains four folders, each corresponding with a phase of installation: Install Commit, Rollback, and Uninstall which are run in the same order that they are displayed in the editor.

To add custom actions first must be compiled as a. NET framework component and added to a project as a script or assembly before they can be added to a deployment project.

Then right click on one of the four folders and chose Add custom action then select your item to be added. This also adds the item to your project. To add a custom action to all four folders, select the Custom Actions node in the editor, and choose Add Custom Action.

File Types editor allows you to specify document types and associate them with file extensions. In addition, you can specify the verbs or actions for each document type and specify MIME types for the document types for use in browsers.

The File Types Editor contains a single pane with hierarchical list of file types and actions. There are three steps involved in associating a file type with your application: adding a document type, associating a file extension, and associating an executable file. Then you can associate it with file extension by going to its properties and type the extension without precede it by a period separate multiple extensions by ;.

Then you can set a command by selecting a. The Launch Conditions Editor allows you to specify conditions that must be met in order to successfully run an installation. For example you may check for the OS version, windows installer components, registry key or even a file if it exists in a target machine. To add an item to search right click on Search Target Machine and then select an item you want to be searched in the target machine and then set its properties from the properties window.

The following pictures from MSDN summaries the properties available:. Choosing prerequisites to install: Sometimes your application may depend on components that must be available in target computer before the installation can take place.

The Select and Configure Packages dialog allows you to select the supported architecture configurations. If you select a bundle it will generate a single installer, however if you don't want a bundle and prefer one package per architecture you will also get one installer file per architecture. If you're unsure which architecture s to choose, or want to learn more about which architectures are used by various devices, see App package architectures.

Here, you can specify the Installation URL and the frequency of update checks. When your app has been successfully packaged, a dialog will display the location of the output folder containing your app package.

The output folder includes all the files needed to sideload the app, including an HTML page that can be used to promote your app. To make the application available the generated files must be published to the location specified:. We will start by adding an Advanced Installer Project to an existing solution, editing it and creating a package.

Afterwards, we will include and a new Visual Studio project to the solution and build both projects in a single package. By default, when adding an Advanced Installer Project, the build output of the solution will not be automatically added to the installer project, to do this you must:.

The output of each project contained by the solution is automatically synchronized in the Advanced Installer project. Following these steps, Advanced Installer Extension for Visual Studio adds in the installer project all application references except the Microsoft.

NET assemblies. After the build is completed successfully, it will create two main files: HelloWorld. Using the Advanced Installer Project viewer, you can edit basic information about your installer like Product Details, Launch Conditions, Install Parameters, and much more. Let's suppose we have an Enterprise edition of Advanced Installer. By default, the installer project will be created based on a Freeware license. Since we want to use features from the Enterprise edition, like selecting a theme for the installation dialogs, we will need to upgrade our project type:.

Now, that we have an Enterprise project we have full access to all the available Advanced Installer Enterprise features.