Click here to Skip to main content
15,887,683 members
Please Sign up or sign in to vote.
1.00/5 (1 vote)
See more:
A co-worker is having an issue with TortoiseSVN. When she rebuilds a solution in Visual Studio 2010, Tortoise is flagging all the attached DLLs in the project as "modified", but they haven't been touched. Does anyone know why this would happen? I'm fairly new to Tortoise, so if it is obvious, please be gentle. :)
Posted
Comments
Sergey Alexandrovich Kryukov 1-May-14 14:02pm    
Not enough information. I suspect the file was actually modified. Why do you store DLL in code base at all? Why storing it as SVN "external"?
—SA
CeiThor 1-May-14 14:05pm    
I checked the file with the "Diff" command and it said nothing was changed! That is the odd part. I'm not sure why they are storing the DLLs with the codebase, I just started this past Monday. I'm hoping I can convince them to stop, but that still wouldn't solve this. I'm starting to think it is a bug.

I dug this up and it took care of things:

Third party libraries
When there are third party libraries stored in the working copy directly, i.e., not via the svn:externals property, then updating those is not quite easy.

Just copying over the new version will work of course, but if the new version has files removed, those files will still be in your working copy.

In version 1.8 TortoiseSVN offers an easier way to do this: just right-drag the folder with the new version of the library to the version stored in your working copy, then select SVN vendor branch here

from the context menu. TortoiseSVN then scans both directories, copies all new files, removes files that are not present anymore in the new version.

After TortoiseSVN updated the folder, all you have to do is commit the new version.
 
Share this answer
 

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900