I don’t mean that it’s largest and most luxurious application every written, but rather that you may be cruising headlong into a nasty rendezvous with an iceberg that could deal a severe blow to your project.
During the transition, the documentation and the UI of some Share Point products and Visual Studio tools might still use the term "apps for Share Point".
Current inside such methods as Item Added, Item Updated and so on as they are usually asynchronous and might be executed on any machine of Share Point farm. Current is null within synchronous Item Adding, Item Updating, etc. On the other hand, within the constructor of SPItem Event Receiver the Http Context. So, the possible workaround here is to get current Http Context inside the constructor, save it in a variable and then use in synchronous methods.
An advantage of using Item Updating to set field values is that the values will be visible to the user after they submit their changes in a non-datasheet view.
it fires on several different events with some fairly in-depth functionality.
Everything else in the feature works fine except the above Item Updating and Item Deleting methods. To test your event receiver, try creating a new Custom List and check if the event fires when you update an item.