Visual SVN client commit solution files only - visual-studio

I have VisualSVN client integrated in my Visual Studio and I want to commit modified files. The problem is when I right-click on the solution file item in the solution explorer and choose 'Commit', VisualSVN is trying to commit all modified files in my trunk. This is the same problem if I choose 'Commit' from the VisualSVN menu item.
Is it possible to just show the modified files linked with my solution and not all the trunk files?
I know that with AnkhSVN, this works perfectly but I think I missed something with VisualSVN client.

Use VisualSvn menu or context menu in Solution Explorer and choose "Show Changes". It could also be that you have fiddled with the VisualSvn->"Set Working Copy Root" option. Set it back to automatic mode if possible.
As VisualSvn uses TortoiseSvn in the background, it works only with folders so if there is a modified file in the folder not belonging to the solution side by side with a modified file belonging to the solution you will see both files.

Related

Subversion - Can't commit message & View History

Which tortoise subversion which integrated with Visual Studio can be able to enter messages while committing, view history of others and my file
The functionality you're describing is not specific to Tortoise, it's a standard functionality of Subversion itself. However, you have the option of integrating TortoiseSVN in Visual Studio as well as just using VisualSVN if you're trying to integrate a SVN client into VS.
That being said, if you're using TortoiseSVN, simply right click on the file folder you want to commit and click SVN Commit... and specify your comment as normal. To view the history of a file or folder, right click on the file or folder and go to TortoiseSVN > Show Log... to see the revision history.

How do I update a solution to latest in AnkhSVN?

I'm using AnkhSVN in Visual Studio 2013 and grabbing code from an Unfuddle repository. I'm not a dev, but my job is dev-adjacent and I'd like to be able to look at people's code.
In VS, I can figure out how to get a local copy of the solution file using the Unfuddle repository URL, but I can't figure out how to update the solution to the latest version. When I right-click on the solution in Solution Explorer, there's no "update" option, and in the Pending Changes window, "Update" is grayed out.
So when I want to get latest, I go to "Repository Explorer" in VS, click the connect icon, enter the URL for the repository. Then I right-click on the file I want to copy over, and select "Copy to Working Copy". I choose a location, and VS informs me that it is "not in a working copy; would I like to export the file instead?" I say yes, and it copies everything over.
I have to do this whole process every time I want to get latest. What am I doing wrong?
Thanks!
Figured it out! The solution wasn't added to Subversion. I needed to go to the Working Copy Explorer, right-click the directory in question, select "Add Solution to Subversion", then enter the repository URL.

How to have TFS 2010 detect changes done to files outside of Visual Studio?

I'm using Team Foundation Server 2010 with Visual Studio 2010.
Whenever I modify a file outside of Visual Studio, TFS doesn't seem to detect the change done to the file, and thus doesn't offer me the option to check-in the file after it has been modified.
How can this be solved?
TFS has a "Reconcile" command for this:
Open the Source Control Explorer
Right-click on the folder with the changes and choose Compare
Select the files you want to reconcile (press CTRL+A to select all files)
Click on the Reconcile button
Set the options in the Reconcile Folder Differences dialog. Make sure Files that do not have pending changes is set to Check Out
Click OK
If you have local changes the Check Out dialog will be shown. Set the preferred Lock type
Click Check Out
See also: Reconcile differences between folders
If you have a network connection to your server while you're working outside of Visual Studio, it's probably best to go ahead and check the file out before editing it, either using the tf command line client, or using the Windows Explorer shell integration that's available in the TFS Power Tools release. (Plus an increasing number of other tools have TFS integration that makes this automatic, but if you're just using notepad, this still needs to be a manual step.)
Of course, there are many times when you're working and you don't have a network connection available that allows you to check out the files.
If you know what files you've modified, you can just check them out from within Visual Studio, then you'll be able to check them back in.
If you don't know what files you've edited, you can detect the changes by running the tfpt online command (also part of the Power Tools release). This will locate the files that have been modified locally and check these files out from the server.
This worked for me, using the TFS Power Tools:
tfpt online /adds /deletes /diff /noprompt /recursive directory-name
(where directory-name is the path to the directory to be updated, otherwise it will detect changes throughout your entire TFS repository)
If you want to know what it would do without it actually making any changes, you can force it to do a dry run by adding the /preview switch.
*1- make changes outside of Visual Studio
2- go to Visual Studio and open Source Control Explorer
3- right click on the folder > "Check Out for Edit" > "Check Out"
4- right click on the same folder > "Undo Pending Changes..." > "Undo changes" > "No to All"*
I tested this workaround on a branch and it helped me a lot. But there are only new files and new folder who has to be done manually.
I recommend to create a branch before the operation. It isolates you the time of the operation.
Note: This technique does also the files identical cleanup that TFS always marks as modified.
Try this. It's some sort of workaround, but it works:
make changes outside of Visual Studio
go to Visual Studio and open Source Control Explorer
right click on the folder > "Check Out for Edit" > "Check Out"
right click on the same folder > "Undo Pending Changes..." > "Undo changes" > "No to All"
That's it. The changes are visible now.
There's also another solution to get TFS to figure out the files that have changed outside of Visual Studio:
Open the solution offline
In Solution Explorer select the solution file and then press the Go Online button ()
TFS will automatically scan the solution for changes after this.
Step one can be achieved in a number of different ways. Here are some:
Use the GoOffline Extension - very simple and effective.
If you're asked for TFS credentials when opening the solution (no automatic domain auth), then don't enter the credentials. The solution will open offline and you'll login after pressing the Go Online button
(extreme solution) Disconnect your network cable; Open the solution; Connect the network cable.
Visual Sourcesafe works like this too and the way I get VSS or TFS to notice the change is by checking the file out once inside Visual Studio.
Open Source Control and go to your TFS folder. Right-click on the folder and choose 'Compare'.
Notice that your edited files show up marked in red.
I find this is better than tfpt online which also gets you files that are not readonly and not edited.
I had this problem in the past, when my Internet was down and I worked offline, and most of my changes didn't appears in Team Explorer.
Following these steps:
First, In the solution explorer, select the folder that you want to re-conciliate (for me, it was my entire solution folder), and select Compare...
Click in Modify Filter, and in the filter text-box, you could type:
*.cs;!obj\;!bin\;!packages\;
In this example, it will include in the search only C# files and exclude in the folders: bin, obj and packages.
Notice the column Pending Change has the info whether the file is marked as edit, add, etc... or nothing...
To mark as edit (when the local item has a matching server item), select the file and choose Check out for Edit...
To mark as add (when the local item doesn't have any server item), select the file and choose Add Files
Finally, I am not sure why the projects are not listed here (after I remove *.cs filter, still doesn't show up), so rebuild the solution to make sure the projects updates as well
+ In the solution, click the connect button (if shows up) that said Go Online.
I found that in Visual Studio 2015, with the project open, Visual Studio discovered for itself that files had been modified externally, and automatically checked them out without me having to do anything. Checking in the project in the normal way saved the external modifications.
In my case, the following worked (at least the one time I tried it):
Go to the Pending Changes panel
Select View Options under either Included or Excluded changes.
Switch between Show All and Show Solution Changes
Switch back if desired
Changing the View Option appears to force a refresh of modified files.

How to add TFS bindings to a Visual Studio 2010 project?

There's a question already discussing how to add project/solution bindings to TFS, however it seems to only apply to Visual Studio 2008 (I am unable to find the "Change Source Control" dialog in VS2010).
I have a solution and source code on my local machine already in TFS, however it does not have TFS bindings (the thing that produces the padlock icon in the Visual Studio Solution Explorer and allows automatic checkout).
How can I add bindings to an existing TFS project using Visual Studio 2010?
In VS2010 check Tools>Options>Source Control and see if set to TFS. If not that might be why you don't see File->Source Control->Change Source Control.
I ran into this problem and, for me, the issue was that my solution was offline with respect to TFS. Upon trying to change source control, I received a message stating that it is already associated with source control but is offline. I placed the solution on-line, per my recollection, using the File->Source Control->Go Online menu option and this seemed to fix the problem.
Go to the source control explorer under Team Explorer, where you can see your repository. Right click on the top folder that maps to the folder on your local machine. There's an option called "Map to local folder". Map this to the folder on your local machine. This will set up all the bindings for TFS for your project.
I had the same problem and the following steps solved it for me in VS 2008.
Unfortunately, I didn't record the exact steps and don't want to add a new project to our TFS to try again, so the steps are from memory.
Go to File Menu -> Source Control -> Open from source control
Select solution file from TFS hierarchy
Accept any warning about project already being on local disc
A popup dialog comes up saying something along the lines "This solution is already under source control, but no bindings exist. Do you want to add them?"
A selector shows all projects in a grid and allows adding the required bindings. Add TFS server setting to each project (select all lines in grid at once and press a button at the top. I can't remember what it was called, but it was fairly obvious).

How to find files in source control but not in a Visual Studio solution?

I have a rather large Visual Studio 2008 solution in Subversion. It was migrated from Visual SourceSafe a few months ago. I'm starting to find that there are a number of files still in source control that were removed from the solution back when I was using VSS. They were probably renamed or deleted after they were checked out - VSS doesn't like that.
I'm looking for an easy way to find all of the files that are not in the solution but are in Subversion. Something like WinMerge's folder compare would be ideal, where one side is the Subversion working copy and the other side is the project contents.
We haven't upgraded to VS2008 yet, so I'm not sure how much of this applies, but anyway:
Approach 1: On the Solution Explorer toolbar, click "Show All Files." Then highlight the root node of the solution and hit "*" on the numeric keypad to fully expand the tree. The icons that are just outlines are files that aren't part of the solution. From those, you have to determine by hand which are unnecessarily in svn.
Approach 2: Do a "svn export" to create a secondary copy of the project somewhere. Open the new copy with VS and then choose File->Source Control->Change Source Control. In the resulting window, if any projects show as "Connected," highlight them and click "Disconnect" on the toolbar. Close the Source Control window and then, in the Solution Explorer, with "Show All Files" turned OFF, delete everything. The files remaining on disk are the extras your project is no longer using.
With both approaches, it would be smart to make a separate backup copy of the project before doing anything, just in case you nail one too many files.

Resources