I should also point out that I know the difference between a metaphor and simile in case that was bothering you from the opening sentence.
I am nothing if not a masterful linguist after a beer or two or more.
With that in mind, Share Point 2010 is like a sea of icebergs – there is a lot going on under the surface that you may not notice until it’s too late.
Unfortunately, that makes your project like the Titanic.
I´m using a Details View but when updating, I cannot get the Old Values because the Details View Update Event Args.
I removed the update from the Set Custodian Permissions method and it started working as expected.
Damon gives just one example of a poisoned dagger in the game of Sharepoint Development: The Item Event Receiver.
I’m usually disappointed when writers employ oft-overused metaphors to describe a situation.
Developing a Sharepoint application would have all the fun of a video game, if only you had infinite lives.
Dangers lurk hidden out there which, if you run into them, can be a blow to your project and waste a great deal of time.
If we look at our example of creating a custom Content Type for “Functional Specifications”, we could extrapolate it to many different types of documents typically used in an enterprise, e.g.