This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Geeting Error while checkin installshield on TFS 2010 Build
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Jun 07, 2014
04:35 AM
Geeting Error while checkin installshield on TFS 2010 Build
Hello,
I'm trying to build a setup .
I installed InstallShield 2013 on that machine, but when I queue a new build with the Team Foundation Server 2010 there is always this error:
C:\Builds\3\PO\PO_Commit_Build\Sources\PerformanceOptimizer\PerformanceOptimizer.Installer\PerformanceOptimizer.Installer.isproj (30): The imported project "C:\Program Files (x86)\MSBuild\InstallShield\2013Limited\InstallShield.targets" was not found. Confirm that the path in the declaration is correct, and that the file exists on disk.
I'm trying to build a setup .
I installed InstallShield 2013 on that machine, but when I queue a new build with the Team Foundation Server 2010 there is always this error:
C:\Builds\3\PO\PO_Commit_Build\Sources\PerformanceOptimizer\PerformanceOptimizer.Installer\PerformanceOptimizer.Installer.isproj (30): The imported project "C:\Program Files (x86)\MSBuild\InstallShield\2013Limited\InstallShield.targets" was not found. Confirm that the path in the
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Jun 09, 2014
03:29 PM
if you have installed Installshield LE on your build server, verify that the targets file does exist at that path. When we had that problem it was just after we upgraded from ISLE2012 to ISLE2013 and it was looking in the wrong path for the targets file.
if the file is there, verify that your build service account has access to that directory.
if the file is there, verify that your build service account has access to that directory.