Thank you for attending my MSDN webcast Project Server Events and Workflows. Don’t forget about next weeks webcast on Project Client programmability. Below is some of the Q&A I got during the webcast. Attached is the demos from the webcast.
Will you chat at all about Project Server 2010? Are there any plans for changes in the new version?
Is the command (i.e save project) already queued, when an event is raised?
Based on your description of pre and post, the "project published" event is raised after save to the db. Would you say its best to eval business rules afterward, log violations, notify user and delete from db? is there an ability to only delete from PDB and leave in DDB so user can correct and attempt re-publish?
Is it microsoft.office.project.schema.dll or microsoft.office.project.server.schema.dll?
microsoft.office.project.schema.dll is the correct DLL.
Is there anything to pay special attention for (i.e. concurrency, locking, etc.) with events on heavy loaded systems or is this solved by "serialized" execution through the project server queue?
Using events to enforce business rules
Yes it’s true I’ve been cheating on my blog and (it’s too embarrassing to say)… posting to another blog.
I was pretty disappointed in the workflow segment. Why create derive a class from SPWorkflowExternalDataExchangeService and so that Sharepoint workflows could respond directly with an event receiver... the hidden list trick is LAME.