Visual Studio Project Import Errors and Warnings

Check the Knowledge Base for information about this error, or request technical support.

This error may occur if the Visual Studio setup or merge module project file is corrupted or if InstallShield cannot correctly read the Visual Studio setup project file. To resolve this error, request technical support.

This error occurs if InstallShield cannot create a Basic MSI project from the Visual Studio setup project or a Merge Module project from the Visual Studio merge module project. InstallShield tries to save the project in the same folder that contains the Visual Studio project file (.vdproj).

To resolve this error, see if the folder that contains the Visual Studio project file is read-only, and change it to writable.

This error may occur if the Visual Studio project file is corrupted or if InstallShield cannot correctly read the Visual Studio project file. To resolve this error, request technical support.

This error may occur if the Visual Studio project file is corrupted or if InstallShield cannot correctly read the Visual Studio project file. To resolve this error, request technical support.

This error may occur if the Visual Studio setup or merge module project file is corrupted or if InstallShield cannot correctly read the Visual Studio setup project file. To resolve this error, request technical support.

This error may occur if the Visual Studio project file is corrupted or if InstallShield cannot correctly read the Visual Studio project file. To resolve this error, request technical support.

This error may occur if the Visual Studio project file is corrupted or if InstallShield cannot correctly read the Visual Studio project file. To resolve this error, request technical support.

This error may occur if the Visual Studio project file is corrupted or if InstallShield cannot correctly read the Visual Studio project file. To resolve this error, request technical support.

This error may occur if the Visual Studio project file is corrupted or if InstallShield cannot correctly read the Visual Studio project file. To resolve this error, request technical support.

This error may occur if the Visual Studio project file is corrupted or if InstallShield cannot correctly read the Visual Studio project file. To resolve this error, request technical support.

This error may occur if the Visual Studio project file is corrupted or if InstallShield cannot correctly read the Visual Studio project file. To resolve this error, request technical support.

This error may occur if the Visual Studio project file is corrupted or if InstallShield cannot correctly read the Visual Studio project file. To resolve this error, request technical support.

This error may occur if the Visual Studio project file is corrupted or if InstallShield cannot correctly read the Visual Studio project file. To resolve this error, request technical support.

This error may occur if the Visual Studio project file is corrupted or if InstallShield cannot correctly read the Visual Studio project file. To resolve this error, request technical support.

This error may occur if the Visual Studio project file is corrupted or if InstallShield cannot correctly read the Visual Studio project file. To resolve this error, request technical support.

This warning occurs if the Command property for the specified file type was left blank in the File Types Editor in Visual Studio. The warning alerts you that InstallShield could not configure the file extension during the conversion process.

To resolve this issue, specify a command for the file type in Visual Studio, and then convert the Visual Studio setup project to an InstallShield project. Otherwise, you can add and configure the file extension in the File Types area of the Components view in InstallShield.

This error may occur if the Visual Studio setup or merge module project file is corrupted or if InstallShield cannot correctly read the Visual Studio setup project file. To resolve this error, request technical support.

This error may occur if the Visual Studio setup or merge module project file is corrupted or if InstallShield cannot correctly read the Visual Studio setup project file. To resolve this error, request technical support.

This error may occur if the Visual Studio setup or merge module project file is corrupted or if InstallShield cannot correctly read the Visual Studio setup project file. To resolve this error, request technical support.

This error may occur if the Visual Studio setup or merge module project file is corrupted or if InstallShield cannot correctly read the Visual Studio setup project file. To resolve this error, request technical support.

This error may occur if the Visual Studio setup or merge module project file is corrupted or if InstallShield cannot correctly read the Visual Studio setup project file. To resolve this error, request technical support.

This error may occur if the Visual Studio setup or merge module project file is corrupted or if InstallShield cannot correctly read the Visual Studio setup project file. To resolve this error, request technical support.

This error may occur if the Visual Studio setup or merge module project file is corrupted or if InstallShield cannot correctly read the Visual Studio setup project file. To resolve this error, request technical support.

This error may occur if the Visual Studio setup or merge module project file is corrupted or if InstallShield cannot correctly read the Visual Studio setup project file. To resolve this error, request technical support.

This warning occurs if you convert a Visual Studio project that includes support for a language, but InstallShield does not have built-in support for that language.

Edition • The Premier edition of InstallShield includes multilanguage support, but the Professional edition does not.

This warning occurs if the Condition property for the specified launch condition was left blank in the Launch Conditions Editor in Visual Studio. The warning alerts you that InstallShield could not configure the launch condition during the import or conversion process.

To resolve this issue, specify a condition in Visual Studio, and then convert or import the Visual Studio project into an InstallShield project. Otherwise, you can add and configure the launch condition in the General Information view in InstallShield after you have converted or imported the Visual Studio project.

This warning occurs if you have a Visual Studio project that contains a particular feature and you import that project into an InstallShield project that already contains that feature. This scenario may occur if you import the same Visual Studio project into your InstallShield project more than once.

This warning occurs if you have a Visual Studio project that contains a file that is associated with a particular file key and you import that project into an InstallShield project that already contains a file with that same file key. This scenario may occur if you import the same Visual Studio project into your InstallShield project more than once.

If you encounter this warning, check the Files area of the Components view to ensure that the file that is identified in the warning message is not missing from your InstallShield project.

Note that the Direct Editor view shows the file key that is associated with each file in your project. The file keys are the primary keys of the File table in the .msi database; the File table cannot contain duplicate file keys.

This warning occurs if you have a Visual Studio project that contains a particular file extension and you import that project into an InstallShield project that already contains that same file extension. This scenario may occur if you import the same Visual Studio project into your InstallShield project more than once.

If you encounter this warning, check the Advanced Settings area of the Components view to ensure that the file extension that is identified in the warning message is not missing from your InstallShield project.

This warning occurs if you have a Visual Studio project that contains a particular custom action and you import that project into an InstallShield project that already contains a custom action with that same name. This scenario may occur if you import the same Visual Studio project into your InstallShield project more than once.

If you encounter this warning, check the Custom Actions and Sequences view to ensure that the custom action that is identified in the warning message is not missing from your InstallShield project.

This warning occurs if you have a Visual Studio project that contains a particular registry search and you import that project into an InstallShield project that already contains a registry search with that same name. This scenario may occur if you import the same Visual Studio project into your InstallShield project more than once.

If you encounter this warning, check the System Search view to ensure that the registry search that is identified in the warning message is not missing from your InstallShield project.

This warning occurs if you have a Visual Studio project that contains a particular file or folder search and you import that project into an InstallShield project that already contains a file or folder search with that same name. This scenario may occur if you import the same Visual Studio project into your InstallShield project more than once.

If you encounter this warning, check the System Search view to ensure that the file or folder search that is identified in the warning message is not missing from your InstallShield project.

This warning occurs if you import a Visual Studio setup project that contains a prerequisite but InstallShield does not have an equivalent InstallShield prerequisite.

To resolve this warning, consider creating an InstallShield prerequisite that installs the required redistributable, and add that InstallShield prerequisite to your project. For more information, see Defining InstallShield Prerequisites and Working with InstallShield Prerequisites that Are Included in Installation Projects.

This error occurs if you convert a Visual Studio setup or merge module project that contains one or more project outputs but InstallShield encounters a problem when incorporating the project outputs into the InstallShield project.

To resolve this error, request technical support.

This warning occurs if you have a Visual Studio project that contains a project output that has a file that is associated with a particular file key, and you import that project into an InstallShield project that already contains a file with that same file key. This scenario may occur if you import the same Visual Studio project into your InstallShield project more than once.

If you encounter this warning, check the Files and Folders view to ensure that the file that is identified in the warning message is not missing from your InstallShield project.

Note that the Direct Editor view shows the file key that is associated with each file in your project. The file keys are the primary keys of the File table in the .msi database; the File table cannot contain duplicate file keys.

If you want to import into an InstallShield project a Visual Studio setup or merge module project that contains a project output, the Visual Studio project must be in the same solution as all of its project dependencies. Otherwise, this error occurs when you try to import the Visual Studio project.

To resolve this error, ensure that your InstallShield project is in the same Visual Studio solution that contains the Visual Studio setup or merge module project that you are importing. In addition, ensure that the solution also includes all of the other Visual Studio projects that are dependencies of the Visual Studio setup or merge module project. Then you can import the Visual Studio setup or merge module project into your InstallShield project.

This warning occurs if you import into an InstallShield project a Visual Studio setup or merge module project that contains a file whose Exclude property is set to True.

If you want the specified file to be excluded from your InstallShield project, you can ignore this warning.

If you want the specified file to be included in your InstallShield project, you can use the Files and Folders view in InstallShield to add it. For more information, see Adding to Your Project Files to Be Installed on Target Systems.

This warning occurs if you import into InstallShield project a Visual Studio setup or merge module project that contains a default launch condition.

If you want the specified launch condition to be excluded from your InstallShield project, you can ignore this warning.

If you want to add a launch condition to your InstallShield project to check the target system for the default launch condition that Visual Studio added to the original project, you can use the System Search view in InstallShield to add it. For more information, see Adding a System Search.

This warning occurs if you attempt to import or convert a Visual Studio setup that has a file search with an invalid value for the MaxDate property.

To resolve this warning:

This error occurs if you attempt to import or convert a Visual Studio CAB setup project in InstallShield, since InstallShield does not have support for this conversion.