Share via


Solution Building and Packaging Errors

   

<Name> could not be added

A file with the name <name> has already been added to the package.

An error occurred during packaging <name>.

An error occurred while packaging <name>

Error encountered in the format of the persisted packaging project file

Error: Failed to generate signature for CAB

Failed to generate signature for <name>, because it does not exist

Failed to generate signature for <name> (certificate file not specified)

Failed to generate signature for <name> (test certificate not found)

Failed to generate signature for <name>. See the Output Window

Failed to generate signature for <name> (test private key not found)

Failed to generate signature for <name> (private key file <name> does not exist)

Failed to generate signature for <name> (private key file not specified)

Failed to generate signature for <name> (‘javasign.dll’ can’t be found)

Failed to generate signature for <name> (no custom Java permissions)

Failed to generate signature for <name> (unknown internal error)

Failed to generate signature for <name> (‘signcode.exe’ can’t be found)

Failed to generate signature for <name> (certificate file does not exist)

If you want to create an entry in the start menu, please provide a name

In order to create an entry in the start menu, we need the command line

Internal error – packaging engine exception

Package output filename <name> was longer than 256 characters

Please fill in a value for the Installation Folder

Project outputs which are not local file URLs…

Setup Packaging Error: <name>

Setup Packaging Error: cannot create CAB for this setup

Setup Packaging Error: no input files

Setup Packaging Error: build cancelled

Setup Packaging Error: Cannot find input file

Setup packaging error: Cannot find the TLB files

Setup Packaging Error: error writing file <name>

The build configuration cannot be changed while projects are building or deploying.

The dependency <name> has already been added to the dependency list

The file <name> does not exist. Add to distribution unit anyway?

The file <name> has already been added to the distribution unit

The file <name> from source <name> conflicts with a file

The project you are removing is referenced by project

The input field for the installation directory is not a valid path

The optional redistributable files for the installer are not installed

The referenced project, <name>, is not active within the solution

The URL and Friendly name fields are required

The version number <name> is not in the correct format

Unable to load the required packaging engine

You have not applied pending changes to the currently selected configurations.