The Package Location describes where the package will be found at deployment time. It is derived differently depending on the type of component. Type 'Builds with application' The Package Location is constructed from the drop location of the build that will be selected at release time plus the relative path of the component (subfolder) defined here. Therefore, the relative path is to be supplied here. Type 'Builds independently' The Package Location is built from the drop location of the build that will be selected at release time plus the Relative Path to Package (subfolder) already defined in the component. Nothing more needs to be supplied here. Type 'Builds externally' The Package Location is built from the UNC Path to Package already defined in the component plus the version (subfolder) defined at release time. Nothing more needs to be supplied here.
The output name extension doesn't match the options used. If '-a' or '-target:library' is used the output file name must ...
The output of the active configuration of this project will be profiled. It is recommended that you choose a non-debug (i.e. ...
The output path is not trusted. The application may throw security exceptions when it attempts to perform actions which require ...
The owner of this snapshot is not the same as the owner of the environment. Ensure that the snapshot was taken with the host ...
The Package Location describes where the package will be found at deployment time. It is derived differently depending on ...
The package path relative to the build drop location is required for component bound with the release template. If the package ...
The package path relative to the build drop location is required for component integrated with Team Build. If the package ...
The package that imports elements. Element definitions in the importing package can refer to the definitions of the imported ...
The package whose elements are imported. The element definitions of the imported package cannot refer to the definitions ...