November 13, 2012 at 3:43 am
Hi,
Facts:
We use Subversion (TortoiseSVN) for version control.
In Visual Studio 2010, we use AnkhSVN as Plugin.
The whole solution with all projects is committed to svn, but not the .suo- and .user-files.
So far, so good.
When I open a dtsx-package within the solution, it automatically is marked as changed and increments the VersionBuild-Number.
Why?
Screenshot DIFF after opening the package: Bild
At the end of a day, there is a huge list of "peding changes" and you can't remember, in which package you really made a change and which you only opened for viewing.
By the way, this behaviour does not belong to all packages. Some are marked as changed on open, some not.
November 14, 2012 at 1:25 am
I see this a lot in multi-user environments. Chances are good that you and your colleagues are not running the exact same build number of SSIS, i.e. same SQL Server Service Pack or list of post-SP hotfixes.
When you open a package, Visual Studio recognizes this fact, automatically checks the file out and updates the package to contain your build number.
I deal with this by keeping the list of patches necessary to bring a workstation to a specific SSIS build number in a common location so all developers can maintain the same build number.
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply