Eventhandler itemupdating

Okay fine, workflows are still out of box, what are we doing new in that? Imagine what would happen after a document (like our Functional Spec) is approved? Until the document is approved again it would no longer be in ‘Published’ state.To view the previous state would be slightly messy.

It needs to have the fully qualified assembly name.

Note you have a file so your dll is going to be a signed DLL.

The event of interest to us is the Item Updated event fired by any SPList.

This event is fired every time you make a change and save your list item.

If you want to see what VS 2010 is doing behind the scenes you can peek into the ‘Output’ window. Essentially VS is taking care of all the plumbing work needed to deploy and register your feature with Share Point.

All this was possible through the excellent WSP builder tool in VS 2008 too, but you still needed to attach the debugger to the process manually. VS will start an IE instance and load the required site up and attach the debugger to the process for you. Step 7: Setup another breakpoint inside the if(…) condition. Don’t be surprised when this breakpoint is not hit. Level property value you would notice it’s still Draft hence the ‘if’ condition is not satisfied and no publish happened.

In SP 2010, workflows have been made pretty obvious.

In fact our custom Pages will not be visible to everyone if we don’t actually publish them and the only way to do that is to start the approval workflow. Ten days into development new requirements would come in and the spec would have to be re-visited and re-routed for approval.

I mentioned earlier also how easy it is to develop for SP 2010 using VS 2010.

Tags: , ,