May 14, 2015 at 2:20 pm
I'm frustrated by this:
My SSIS projects are in TFS. Say I create a new package in Visual Studio/BIDS (SS2008R2), test it, like it, then check it into TFS.
Later, I open the package up in BIDS again. It gets automatically checked out of TFS by Visual Studio/BIDS, even if I just want to look at it in the designer.
Now, even if I change nothing, BIDS generates new GUIDs throughout, which naturally makes it "more recent" than the latest checked-in copy, even though nothing else (and nothing of substance) has changed.
I wind up either discarding the "changes" or checking it back in with some comment like "version bump"
I'm tired of doing this and wonder if there is a way to tell BIDS, "Don't regenerate the GUIDs or bump the version unless something actually changes!"
Or perhaps a way to open a package in the designer without checking it out.
Oh, BTW, running the package in the debugger has the same effect even if I don't open it in the designer
Gerald Britton, Pluralsight courses
May 16, 2015 at 4:53 pm
IIRC the GUID is calculated on a binary pattern including volatile attributes such as "Last Opened/Edited/Modified...", most likely the reason.
😎
May 16, 2015 at 8:18 pm
That sounds likely but it is still unacceptable since I changed nothing
Gerald Britton, Pluralsight courses
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply