jkell wrote: While this looks to be affecting an InstallShield file, this looks to be more of something occurring on the source control side of things than something with InstallShield itself. I did some quick digging around online and came up with the below that may help guide you to what may be causing the issue. =================== In Visual Studio you may be able to see what the changes are by going to: View -> Other Windows -> Pending Changes If you had more than one VS instance open at any time, the window content might be out-dated, so hit the "Refresh" button on top of Pending Changes tool window to be sure. http://stackoverflow.com/questions/2137027/how-do-i-view-all-of-my-pending-changes-in-vsts-source-control-explorer?noredirect=1&lq=1 =================== First part: maybe yes, but it's only affecting the .isproj file, thus I assume, that during build Installshield changes something (modify date, ...) so that Visual Studio thinks it has changed, even there are no textual changes, because Second part: that's exactly how I came upon this issue, because I saw in Pending Changes that the Setup.isproj file is listed and when I click Compare with latest version, they are Identical (not even any newline or whitespace are different). And when I click Undo, it is still listed (that part I guess is Visual Studio). But since this behavior is only for the .isproj file, I guess it has something to do with InstallShield as well ... ... View more