According to the latest p4v documentation (https://www.perforce.com/perforce/doc.current/manuals/p4v/p4v.pdf) I should be able to unload a task stream from p4v by right clicking the stream and selecting unload. This option never appears for me. Is there some condition that must be met for this option to appear? Thanks!
Edit: I am running p4v 2018.2/1687764
You don't mention what version of P4V you're using, but as a general rule, if functionality described in the latest version of the documentation doesn't match what you see in the product, make sure you're running the latest version of the product.
If you're running the latest version of the product, try performing the analogous operation from the command line (p4 unload). If you get an error message, that'll be a strong clue as to why you can't do it from P4V.
Related
I am working on an ASP.NET application in VS2010; the repository is still VSS-2005. I am going to abandon the changes made to one of the pages and revert back to the version that existed two checkins ago (which is the current production code). My problem is that I haven't worked with VSS much and I've never done this particular thing before. I can't find any "How to" literature on VSS that tells how to do it, and when I try to do it using the intuitive thing (do a "Get" on the version I want to revert to), it does nothing.
I can View that older version using Notepad, and so I could check out the page and replace the code with the Viewed Notepad version, but this doesn't seem proper somehow.
I've been wondering about the Rollback button, but when I click it, it gives me an ominous message that I am not sure I like: "Rollback cannot be undone; some versions will be lost irretrievably! Continue anyway?"
Well, apparently there are no SourceSafe gurus out there, so I'll answer my own question. I bought a book! And it told me how to do it.
Overview:
Check out the current version manually
"Get" the version we want to revert to
Check in the older version as a newer version
Details:
Check out the current version, then use the View History command to show the History dialog and select the version that is desired to be reverted to.
After selecting/highlighting this version, click on the Get button. The Get dialog shows where the specific file version will be placed along with several options. By default the path in the To text box points to the file in our workspace, which is what we want. Don't select the "Make writable" option since the file in question is already under source control. Leave everything as defaulted, and click OK. In the next dialog, choose "Replace". SourceSafe gets the older verison and overwrites the one in the workspace.
Now that you have the older base version, all you have to do is check in the version and obtain a new version that is identical to the old one.
I got this information from the book "Visual Source Safe 2005 - Software Configuration Management in Practice" by Alexandru Serban, published by Packt Publishing Ltd. I bought the book used, but found you can still get it new from the publisher for a lot less than the list price -- $20 less! I don't know who might need a book about an obsolete source control system, but don't pay full price, get it from the publisher direct! Amazon charges the full list price on new copies (astonishing).
I had some changes on my local file but by mistake I took latest version from TFS. Now my changes have been lost. What can I do to take my unchange copy back? Please suggest.
Nothing. If you didn't commit your changes, they're gone.
Unless you added your previous changes to a shelveset (which is unlikely, otherwise you'd know they're there), your changes are gone.
Further reading, in case you don't know what a shelveset is:
What is shelving?
What is the purpose of a shelveset?
Though Daniel's answer is perfect one for the question, I want to share something with others who might face the same situation as mine. As I got latest version from TFS, new files were giving giving compilation errors hence there was change in source files but not in dlls. After surfing around I have found ILSpy link which helped to to recover my source code.
I work with a shared SVN. Occasionally, there's a problem with the latest HEAD build, and I need to rollback to a previous version that works while it's being fixed.
I do this by going into the SVN logs, right-click on the revision and select "Revert to this revision", as described here: http://tortoisesvn.net/docs/nightly/TortoiseSVN_en/tsvn-howto-rollback.html
When the problem is fixed, how do I go back to the HEAD version (i.e. undo the rollback)? Updating does nothing. The only ways I have are a) deleting all my files and doing a fresh checkout, or b) going to the commit dialog and individually reverting my files (which brings them up to the HEAD version).
This seems pretty awkward and broken, so is there a better way of doing this?
Sounds like what you actually want to do is "Update to revision...", not actually a revert operation. If you know the HEAD (or revision X) is broken, right-click and use "Update to revision..." to update to the latest working revision number. When you're ready to update back to HEAD again just do a normal update. Think that should work anyway!
Edit: Note that I've not actually tried this, but sounds workable to me.
The last TortoiseSVN Update command loaded work-in-progress code from the trunk which shouldn't have been committed yet, and overwrote the files that I had on my branch.
How do I undo that last Update command and revert back to the versions that I had on my machine before the Update?
There is no "undo" or "revert", but if you update to the previous revision, that is the recommended way to accomplish what you are asking for. In TortoiseSVN, select "Update to revision..." and enter the revision number you want to go back to.
revert back to the versions that I had on my machine
If you had local changes on your machine that were never committed (i.e., no revision number), and you updated over them, then you are out of luck. The only way to get back your local changes is if you have a backup (check the "Previous Versions" tab in Windows Explorer...)
Check out this guide for undoing revisions on TortoiseSVN. The entire concept of version control supports the issue you've created for yourself so it is a popular action.
This is called update to revision... In the ui you can choose which version you want to go back to. Make backup copy of your local svn tree first to be safe!
You can update to a specific revision by right clicking on your working copy, Under the TortoiseSVN menu item, there is a update to revision menu option that will allow you to change your working copy to the revision of your choice. If you do a show log on the repository you can get an idea of when the offending code got committed and revert back to the prior repository revision. As a precaution, I would make a copy of and working copy, or important files in your working copy, to ensure that if things go bad, you can always get back to where you are now.
Now this changes your working copy, not the repo, so if you are wanting to revert the repository back, then that is a different issue, but I do not think that is what you are asking for.
I have a custom action that no longer exists (I deleted it and it is no-where to be seen at all in InstallShield. I compile and rebuild InstallShield. When I click "Run" to install the product, it gets close to the end, then spouts:
error #1721: Cannot execute "Run_exe.exe".
The custom action no longer exists, and it still seems to attempt to run it... I took it out of the list of events as well. Why is it doing this when I have completely removed it?
If your ISM file is stored in the XML format, I would open the ISM file with a text editor and search for the name of the custom action. That should indicate where it is still being referenced.
Perhaps it didn't truly get deleted? Try going through InstallShield's "Direct Editor". Go to the "CustomAction" table. Right-click the custom action you want removed and select "Drop row".
I get errors like that cropping up all the time, because I make a lot of changes to the installer from version to version. The only way I've found to deal with it is to start a new project and copy all the properties from one to the other. Not very efficient, granted, but it's better than nothing.