On a 2009 system, I have the following scenario:
- Create two multimedia components with the same binary filename
- Publish a page where the templating calls AddBinary on both (using the filename)
- The publish fails because the second binary can't be deployed to the same location as the first
- However... the first binary remains deployed, as does the binarymeta
- Delete the page
From here on, there is no unpublish action available to you which will trigger an undeploy of the binary, so you can't ever publish a binary to that location even if you delete the file: the binarymeta will still prevent it.
I have heard that some level of transactional deployment was introduced in 2011, and that this became better still in 2013, however the details are unclear.
What are the features/capabilities of transactional deployment in 2013, and how do they differ from previous versions?