Managing Bookmarks Within Visual Studio (2005, 2008, 2010, 20-whatever)

Question

The bookmark feature in Visual Studio 2005 is nice and I am now very used to it.  However, it is frustrating that if I copy a solution to another directory, the bookmarks "File Location" still points to its previous value.

Is there a way to update the paths to change to the new directory to which I've copied my solution?  Is there an export function for bookmarks?  Is there an import function for bookmarks?

Answer 1

Hi kooth,

Thanks for your post.

In order to give specific suggestions regarding your question, would you please provide steps to reproduce this issue?

I'm waiting to hear from you about the status this issue.

Best Regards, 

---

Andrew Wu [MSFT]
MSDN Community Support | Feedback to us
Get or Request Code Sample from Microsoft
Please remember to mark the replies as answers if they help and unmark them if they provide no help.

Answer 2

There currently is no supported way to preserve bookmarks across moves.  Relative paths could be used so this could theoretically be changed in a future version but currently it won't work.  Breakpoints have a similar problem but they added export capability in 2010.

You could write an extension that enumerates the bookmarks in the current solution and saves them to a file using relative paths (or absolute if the path isn't relative to the solution).  You could then import the bookmarks after copying the solution.  Someone might have written an extension already but I don't know of one.  Here's a discussion about it in the forums: http://social.msdn.microsoft.com/Forums/en/vsx/thread/2743de02-7d4b-4cdb-b9d3-cc55f033e83d

Michael Taylor - 8/10/2011
http://msmvps.com/blogs/p3net

Answer 3

Really?  You want the steps? 

 

1. In any project, make a bookmark on a line of code.
2. Close the solution.
3. Copy the solution directory to a new location.
4. Open the solution.
5. Click on the bookmark.
6. What opened for you?

Answer 4

Hi Kooth,

File Locations of bookmarks are stored in the .suo file(Besides the .sln file, defaultly hidden). Unfortunately, that file is a binary file and not easy to hack on.

Here's a little more info about suo file: http://msdn.microsoft.com/en-us/library/bb165909(VS.80).aspx