MS Edge - restore deleted favorites folder - microsoft-edge

I keep my favorites in different folders. I have accidently deleted one of my folders. Is there any chance to restore it?
Thanks

Unfortunately, as far as I know, there seems to impossible to restore deleted favorites folder.
However, you can find some useful tips in this link. You can refer to Firedog's reply in the link, but that will only work if the bookmarks backup was created before your accidental deletion.

Related

tfs check-in project wants to delete file

I am not sure how this happen I want to check-in the project sln but it wants to include a delete. If I filter pending changes it displays this file but I dont want to delete it I want to keep it and add the lock. When I try to undo I get a message the file must be deleted.
Is there anyway around this?
It seems that there are someone deleted files but affected and did a "tf delete" on this .aspx file.
For solve this, please try with follow steps:
First, rename this file(ListOfDrug.aspx) to something else (ie
NewListDrug.aspx)
Undo pending delete of packages.config
Checkout packages.config from TFS
Delete packages.config from fileSystem
Rename newpackages.config back to packages.config
I know this may painful, especially affects many different projects at the same time. But this seem be the useful way to solve this issue.

Prevent users from deleting a file in TFS

Team,
I am having this requirement to prevent users belonging to a specified TFS group(defined in my TFS 2013) from deleting a file. I mean the option to delete a file should be grayed out for the users belonging to that group. But they should be able to add and edit the file.
May I know how to accomplish that ?
You cannot, but if you weigh in the fact that deletions are not permanent and can be easily undone in the TFS Version Control, by opposition to a simple file system, then you'll realize that you don't need to disable the Delete command.
If someone accidentally deletes such a file, you simply have to turn on the "View deleted files" option of the Source Control Explorer (usually the 2nd button of its toolbar), locate the said file, "Undelete" it and "Check In" the undeleted file.
Regards,
Dan

What do the Delete Team Projects dialog choices mean?

I've copied a folder from one Team Project to another one, and now I want to delete the original Team Project, but I want to make sure I keep my history. When I try to delete the original project, I get this dialog box:
What do these choices mean, and what should I check to make sure that I keep history on the moved folder? Will my history be preserved if I delete the original? There seems to be much confusion online about this question.
What do you mean when you say you copied a folder? If you truly mean copy, then there should be no history for those files. Copy shows up in TFS as creating new folders/files.
If you moved the folder, then there is a link back to the history in the original team project, and deleting that team project will remove that portion of the history.
If this is a concern then you don't necessarily have to delete the old team project. If you just remove everybodies access it will no longer show up in the list, but the data is still around if you ever need it.

TFS 2010: history lost after moving a folder

In order to clean up my project structure, I moved a folder into another (new) folder through the TFS Power Tools Shell-Extension (Rename/Move).
After checking the history at the new place, the move is the only entry. (I tried one folder up, down, even on single files in the moved folder.. same result.)
I had also put on some labels on versions of the folder before the move, since there were some important states of the code I wanted to get back to.
So.. what went wrong, and how can I either get the history or at least find out the label names again and check out those versions?
Turns out it is pretty easy.
In Visual Studio 2010, go to Tools->Options. There you can find the option to show "deleted" items (roughly in the middle of the dialog box). The old folder got deleted during the move - it will be displayed again after activating that option. (They will be kind of grayed with a red cross.)
Labels seem to have disappeared, though, so I had to go by version.
In the Source Explorer you have the normal operations again - like View History or Get.
DISCLAIMER: For reference of everyone that gets here, this answer is not fixing #Andreas problem, just giving some context on why this happens and offering a couple of workarounds.
Seems that losing history when moving folders in TFS 2010 is not a bug, is a "feature". (still happening in TFS2012. From this MSDN link you can read official Microsoft answer:
Thanks for the feedback here. The previous comment about this being by design is correct, and there is an option on the command line. In the UI, history of folders is recursive - always. This is because most of the time, users care about the history of the contents of the folder. Files on the other hand dont have the concept of recursive history - you always see the history for the file itself. Now, from the command line, there is an option to show recursive history (/r) and if you run tf history on a folder without the recursive option, you'll see the changes to the folder itself. This would include changes such as a rename for the folder itself.
Workaround to get history once lost: As you can see there, you have a workaround using tf history.
Workaround to avoid losing history: If you want to avoid losing history in folders instead of using move feature, you can use TFS Integration tool to migrate code from one folder to other preserving history, migrating from $/TFSCode/FolderA to $/TFSCode/FolderB. It is a little bit overkill but if the history is pretty important for you is much better than looking for it in deleted folders
It is true that the folder history is lost, but the individual file history is actually not lost. It is hidden under the little "expand me" arrow at the far left on a file history line. Expand it on the oldest history entry for a file, or anywhere you see it, and you will see history of that individual file also from an old location that no longer exists.
At the top of History window you can edit Source location, put the old name and get the full history before it has been moved.
Also, is good to mention that you can get the full history back by moving/rename the branch back to the old location/name.

TFS claiming files are locked even though they are not - Orphaned Locks

I'm trying to perform a baseless merge between two branches using tf.exe.
When I run the command, it fails and tells me that there 15-20 files that are locked by another user. I've looked at the other user's pending changes and he only has three files checked out in the target branch and none of them are locked.
Has anyone experienced something similar to this before?
Edit
With help from Robaticus, I've found that the locks are in the tbl_lock table, but the pending changes they are associated with do not exist any more. It looks like there are multiple orphaned locks other than the ones that are giving us the current merge issue.
Does anyone know what causes these or a way of fixing them that does not involved touching the DB directly? I'm off to do a little research to see if I can find anything.
Edit 2
First Google search for 'tfs orphaned locks' returns this: Orphaned locks in TFS
The TFS team recommends deleting them directly from the table, so I guess I'll have to do that.
I didn't see any posts indicating that it had been fixed yet.
You may want to check to see if they are locked in an abandoned workspace. To do this, install the TFS Power Tools (October edition) for TFS 2008. Then you can right click on a folder in the source explorer and "Find in source control." Use the "Status..." and you can find all files that are locked by that user.
If you have administrative rights, you can selectively remove the locks from any locked files.
* EDIT: Dangerous Code Ahead *
The code below can be executed against the TFSVersionControl database. This will show you all files that are locked. This might tell you if you have an orphaned file out there somewhere.
I wouldn't recommend that you make any changes within that database, and, of course, always make sure you have a current backup of your repository before you ever do something like this.
select
lck.FullPath,
wspc.WorkSpaceName,
id.DisplayName
from tbl_lock lck
inner join tbl_workspace wspc on wspc.WorkSpaceId = lck.WorkSpaceId
inner join tbl_identity id on id.IdentityId = wspc.OwnerId
Did you use the Attrice Sidekicks to look into this issue. It is a nice UI around the commandline tools of TFS.

Resources