P4VS prompts for delete when closing file?
Posted 04 January 2016 - 06:00 PM
In our Solution setup we have solution folder, in this folder is a bunch of header files that are added to it. These files are also added to our version control. When I double click one of these headers from this solution folder to open it, upon closing it, I get a prompt from version control asking if I want to delete the file from Version control?? I have attached a screen shot of the prompt I get.
I am not sure if it is because it these header files are not added to any specific Project in our solution or not as header files I tried the same open/close on that are in projects in the same solution do not exhibit the behavior..
Any thoughts or suggestions??
Posted 29 January 2016 - 12:58 AM
Thank you for reporting this. Sorry that you ran into this bug. I have added your comments and email to an existing bug regarding the unneeded "Would you like to Mark for Delete the file in the Depot" pop up dialog.
Posted 22 March 2016 - 05:12 AM
Posted 25 March 2016 - 12:02 AM
Thanks for your feedback. I have added your comments to the existing bug report for this issue on your behalf. After the fix is released you will receive notification by email.
In terms of a scheduled fix, I cannot say for sure but it might be in the next release. However, checking the release notes will always update you on all the new features and fixes:
In addition, here is another good link that covers patch notes:
Posted 22 April 2016 - 12:01 AM
Posted 25 April 2016 - 06:50 AM
Please ping back when this is solved!
Posted 18 July 2016 - 01:36 AM
Posted 03 January 2017 - 01:14 PM
Close a source file that is not a part of the solution (e.g. a 3rd party source file) and the aforementioned dialog will pop up.
A fix would be greatly appreciated.
Posted 08 February 2017 - 10:20 AM
I tried older version of P4V (2014.3), but it did not help.
No only it is dangerous, but also frequent deletions of crucial headers (I'm deleting few wxWidgets headers per hour now) force my project to complete rebuild, because restored headers are marked as modified.
This costs me a lot of time.
If I cannot get my hands on some older (actually working) versions of P4VS I'm simply ditching this plugin as completely unusable.
Is anybody working on fixing this? Is there some kind of roadmap? A date of expected release of fixed version? Any information would be helpful.
Posted 08 February 2017 - 02:10 PM
But this happens constantly when VisualStudio intellisense is closing files in the background (or it might be Visual Assist plugin, I'm not sure), which happens in the middle of me typing some code,
which results in actually marking the file for delete and closing the annoying pop-up. And then after a while I realize that if have just deleted some library files I had no idea were even opened in the background.
Is there any quick fix for this? Something about workspace configuration maybe?
Posted 28 February 2017 - 10:56 PM
Posted 01 March 2017 - 02:54 AM
First check the “Prompt for changelist when checkout or adding file”.
This will allow the ablity to not add the file to Perforce.
Second uncheck the “Automatically add new files to Perforce”
This will not cause the p4 add to happen and therefore the delete dialog should not show up when the file is closed.
Then at some point in time select the Project or Solution and select Mark for Add and the files that were added in the solution will be added to Perforce.
Posted 15 March 2017 - 04:56 PM
This makes stepping through the debugger REALLY frustrating.
I have used this plugin every day and find it valuable, but this bug renders it pretty much unusable.
Posted 17 March 2017 - 01:20 AM
Posted 22 May 2017 - 10:20 AM
I get that same behaviour under slightly different conditions:
- open a file which is not part of the current VS-solution (but anyway is under version control by P4)
- close the file
- open and close the file again
On the 2nd close, the prompt for delete appears.
I'm not sure if this is the same bug, but it certainly seems related. The workaround mentioned above does not fix the issue.
Please note that this is a very common workflow for me (e.g. for debugging, as mentioned above by others, or for having a quick look into a file from a related library). Several people in my organization suffer from the issue and I'd like to upvote the importance of this bug.
Version of P4VS is 2016.2.147.9832. Version of Visual Studio is 14.0.25431.01 Update 3.
Posted 18 September 2017 - 01:56 PM
I'm using P4VS version 2017.1.152.674, and the "Mark for delete" dialog keeps appearing from time to time in VisualStudio 2015.
I can reproduce the problem very easily by using the "Go to definition/implementation" function of VisualAssistX, if a temporary file that is not in the solution was previously opened. P4VS will ask to "mark for delete" the last opened temporary file (the file last opened in the "Preview" tab).
What's really dangerous is that the default button in that dialog is "Yes", so if you accidentally hit Enter it marks the file for delete even if you never intended to do that.
Posted 07 November 2017 - 01:21 PM
Posted 07 November 2017 - 01:33 PM
Yes, this is fixed. Here's the relevant extract from the P4VS Release Notes:
1561829 (Bug 81180) *
P4VS will no longer mark a file for delete if the OnDelete
signal from Visual Studio has been erroneously sent for a file
closed in the editor that is under source control, but not
part of the currently active solution.
Posted 07 November 2017 - 02:16 PM
After updating P4VS to version 2017.2.158.2681, it still prompts to delete a file every time I close it on the editor.
This happens with files which are not part of a Project, but are part of a solution folder.
Microsoft Visual Studio Professional 2015
Version 14.0.25431.01 Update 3
Posted 07 November 2017 - 02:52 PM
You comments will be passed back to the developers (If you have a support agreement with Perforce it would help if you could you open a case to help investigate).
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users