Timeline for "Thread abort exception" in event receiver after adding a solution?
Current License: CC BY-SA 3.0
2 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 27, 2012 at 16:26 | comment | added | Vroomfundel | Yes, I have clearly indicated that I know that the job is done asynchronously, and I have shown the code I use to poll for the completion. The problem is that the thread gets aborted before this gets a chance to finish. I don't see how this could change if I implement an alterantive polling mechanism that uses job status - I'm polling successfully, it's just that my thread gets killed It actually never gets to finish - the features from the solution don't get activated if it was deployed in the context of the WebProvisioned event receiver, while they get activated if I deploy with PowerShell | |
| Sep 17, 2012 at 20:49 | history | answered | GavinB | CC BY-SA 3.0 |