Event listener behaviour when using send to function

Question

I'm puzzled how sharepoints send-to function works with regards to event listeners - if i send-to a document in library A that already exists in library B (as a record) i'd like to be able to intercept this, undeclare the record, update the versions (or just move out the old record completely), write the new record inplace and redeclare. however the send-to just tells me

"Unable to copy because the destination is checked out by a different user."

this make sense - it is, but i'd like to be able to intervene before this check is made to sort things out so it isn't checked out.

VS2010 doesn't stop at any break points on the receiver end nor if i add some new ones for moving on the sending side. there seems to be a step here that isn't being exposed?

events i've tried are add, adding, update, updateing, move, moving. also tried forcing the whole thing to synchronous (in elements) in a vague hope that stabbing wildly would solve the problem.

any ideas?

Answer 1

Hi toby.davies,

When you send to a document, you’d better ensure the document is checked in . As far as I know, When you debug your event receiver , your visual 2010 is not stop at any break point, in my opinion, your visual studio project may be corrupt. It is also may be your dll file not register into your GAC.

 

Thanks,

Jack

Answer 2

visual studio breaks correctly (and as expected) in other projects and within different parts of this one. i'm concerned that the send-to operation functions differently to other operations in the object model. i know this question is old but between the 3 of you, it has NOT been answered.

i'll look into this further and see if i can replicate elsewhere or find out how the send-to works.