Itemupdating properties listitem update
To view the previous state would be slightly messy.Instead of using the out of box revision history, if we built a capability where after every “Publish” the content is converted into a read-only format (like HTML/doc/pdf) and kept in a different location, it would solve our problem.
Once VS finishes processing, you will have a solution structure similar to the below image.So, enough of theory, let’s get hands on and build our own Event Receiver feature for Share Point 2010.Step 2 The Share Point Customization Wizard will come up as shown below.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.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.It gives you two deployment options for your feature, one is Sandboxed and other is Farm deployment.
I selected Sandboxed because I want the feature to be limited to the site collection where I am publishing only.
Custom Content types help us with defining the data-structure while layouts help us define the presentation.
What if these documents were to require review and approval?
You will notice as a part of the Event Receiver you’ve a cs file and an xml file called
The Elements file is a kind of glue that binds your code to SP Event framework. element is a placeholder for the full assembly name.
There is a list of sales regions with the name of the sales representative, sales manager, etc for each region. The code is configurable, so additional child lists can be easily added by updating an item in a Share Point configuration list.