We are currently working with 2013 SP1 version and got a requirement to publish binaries without any TCM URI getting appended to it. I am aware of duplicate binary issue which is fine with the customer rather than TCM URI getting appended.
I have tried using
AddBinary() in c# template passing the the binary filename to it. Publishing seems to be working fine but un-publishing doesn't seem to work as I could see the image still in place even after un-publishing the Component it is linked to or the multimedia Component as well. Am I missing the basic understanding?
Is this approach correct? If yes, do let me know what scenarios we need to take care and how when we are just using the filename as we are manipulating the default process.
As I am "implicitly" publishing multimedia as Frank van Puffelen explains this isn't really publishing in the strict sense in the Binary Event Tracker post. When such a binary is no longer referenced in Content Delivery, it is removed. But in my case it isn't. Does that mean am I missing any configuration on deployer end?