Same for me on fresh install of VS2015, followed by installation of the installer project extension.
You can work around the problem with editing the installer project file (*.vdproj):
- Open the
YOUR-SETUP-PROJECT-NAME.vdproj
file in a text editor
- Search for
"Release"
, including the quotation marks (or any custom configuration profile name you are targeting)
- Make sure you found s. th. similar to the structure I inserted below and that your found structure is below/within a section named
"Configurations"
- Either: completely disable the installer bootstrapper prerequisites with changing
"Enabled" = "11:TRUE"
to "Enabled" = "11:FALSE"
- Alternatively: edit the
"Items"
list to suit your needs (you have to search for the correct entries there, of course - maybe you have an older installation of VS to produce the entries you need, or you may find matching entries via web search)
My section now looks like that:
"Release"
{
"DisplayName" = "8:Release"
"IsDebugOnly" = "11:FALSE"
"IsReleaseOnly" = "11:TRUE"
"OutputFilename" = "8:Release\\My Setup File Name.msi"
"PackageFilesAs" = "3:2"
"PackageFileSize" = "3:-2147483648"
"CabType" = "3:1"
"Compression" = "3:2"
"SignOutput" = "11:FALSE"
"CertificateFile" = "8:"
"PrivateKeyFile" = "8:"
"TimeStampServer" = "8:"
"InstallerBootstrapper" = "3:2"
"BootstrapperCfg:{63ACBE69-63AA-4F98-B2B6-99F9E24495F2}"
{
"Enabled" = "11:FALSE"
"PromptEnabled" = "11:TRUE"
"PrerequisitesLocation" = "2:1"
"Url" = "8:"
"ComponentsUrl" = "8:"
"Items"
{
}
}
}
As you can see, I followed the path to completely disable those prerequisites which is fine for our use cases, but may be different for others of course.