About stephen_mccullo

stephen_mccullo · ‎Feb 22, 2011

Thanks to this thread I was able to resolve about 120 errors from my TFS \ InstallShield 2011 Standalone Build configuration. I was able to determine that to fix this permanently I would have to increase the size of the ISPathVariable column of the ISPathVariable table. Here are the steps I took to fix this problem once-and-for-all: 1) Check-out your ISPROJ project from TFS then close the solution 2) Open the .ism file (located in the same folder as the .isproj file) in Notepad 3) Using the serach to to locate the table definition for ISPathVariable 4) Note that the column definition is defined by default as ISPathVariable Change the def value to a larger number such as "s64" 5) Re-open the solution in Visual Studio and open the "Direct Editor" view of your Installer project 6) Correct all of the project names in the following columns of the following tables (this is a one-time action after increasing the ISPathVariable column length): Column ISPathVariable; Table ISPathVariable Column ISBuildSourcePath; Table File 7) Save and check-in your project. Of course a larger default size of s64 would be far more reasonable then s32, but at least this can be fixed. Stephen

stephen_mccullo · ‎Feb 22, 2011

Hello all, We have a Visual Studio 2010 C#.NET solution of which we are trying to setup automated builds on our TFS 2010 server with an InstallShield SAB installation. Our solution contains a "Basic MSI" installer project which defines a number of features including a service and a windows form features. We have customized our dialogs to allow customized input values for the relevant ".config" files contained in both projects. Which means we needed to implement updates using the "XML file changes" view. Of course compiling out project via the Visual Studio IDE works fine (as has been the case regarding multiple errors reported from TFS and InstallShield SAB). But I keep coming to dead-ends trying to resolve this one. When I configured the XML file to update, I had to browse for the physical file, which of course for windows forms and services is the config file with the name that reflects the project executable. This creates an absolute path to either the bin\Debug or the bin\Release folder. Of course TFS is not aware of these locations during an automated build and throws this kind of error for each file that needs to be updated: C:\Program Files\MSBuild\InstallShield\2011\InstallShield.targets (68): -6103: Could not find file "d:\Builds\1\ \Test Release\Sources\ \bin\Release\ .exe.config" Of course it does make sense but how to fix it is the trouble. How can I define the "XML file changes" to look to the project primary output location instead of using an absolute path? Does anyone have any other suggestions? Stephen

Online Status	Offline
Date Last Visited	‎Mar 18, 2019 12:10 PM

Fixing truncated project names

TFS and IS Standalone Build errors with "XML file changes"

Fixing truncated project names

TFS and IS Standalone Build errors with "XML file changes"