It happens...
A Laptop 'goes south' and disk and/or data are unable to be recovered.
Or a co-worker wins the lottery and moves on to greener pastures...
In any case, some development effort may have been lost if work was being saved locally (versus committed/pushed with aldongit or saved in a Private Version on the server). If the files cannot be recovered, we may need to cancel the checkouts from the LMe repository.
What to do if there is an active checkout to a workstation that is no longer available for use?
If we attempt to cancel a checkout that is associated with your workstation, will find that this is not allowed:
AFF0172 You cannot cancel the check out for the part or parts you selected. One of the following has occurred: (1) The parts are not checked out, and therefore you cannot cancel the check out. (2) The part or parts for which you are trying to cancel check out are not checked out to your development environment.
So how do we remove the checkout to move forward?
What is the 'trick'?
~~
The LMe repository knows about the relationship of the Development Environment to a workstation and path.
When you define a development environment (manually, or automatically when working with Plugins or Visual Studio IDEs), we associate your computer and the development working file location.
To get around the checkout AFF0172 error, we'll update the Developer Environment to point to your current/active workstation.
This will allow us to cancel the checkout for the 'lost' development environment.
~~
For a simple example
, can see multiple files checked out to my Dev Environment.
Here are some screenshots and a quick recap (as well as a quick demo attached for download).
------------------------------
Dale
L3 bits for Enterprise stuff...
Rocket Software
------------------------------