Ons het gesamentlik spandeer 'n groot deel van die tyd te dink oor SharePoint oplossings — hoe om hulle te skep, instrument te gebruik, wat gebeur wanneer hulle nie aan te wend, timer werksgeleenthede, bestekke, ens.. We spend so much time thinking about the up-front bits that it’s easy to forget that we need to retract them as well. Retracting solutions is probably more difficult, van 'n konseptuele ontwerp perspektief, than deploying them. Deployment is basically a cookbook affair. Typically, installering van 'n funksie, Miskien het 'n funksie ontvanger laai 'n paar data in 'n lys, that sort of thing. Egter, terugtrek, is potensieel meer komplekse.
'N gegewe oplossing kan skep artefakte soos hierdie:
- Inhoud Tipe
- Lys Definisie
- Site Definisie
- Data in 'n lys
- Selfs ontvangers
- Path vorms
Die lys gaan aan.
Terwyl dit is natuurlik belangrik om 'n oplossing te vind wat Instansieer die artefakte korrek te ontwerp, it’s just as important to consider the update and delete cases. If your solution creates a new list and populates that list with data, wat gebeur wanneer die oplossing is teruggetrek? In some cases, the list should be deleted. In other cases, it should be left intact for historical purposes. Your business requirements will guide you to the right decision.
Om te help met hierdie, create a matrix that lists each artifact your solution deploys to SharePoint. List three columns per artifact, een vir skep, werk en te verwyder. For each case, bepaal die korrekte uitslag van die operasie.
This sort of analysis is obviously best done before the solution is ever deployed to a SharePoint farm. Egter, soos rook, it’s never too late to start doing things correctly. Create that matrix and develop a plan to address the missing update/delete scenarios. It may be a hard problem to solve, maar ten minste sal jy gestel het om 'n boks rondom die probleem.
</einde>
Volg my op Twitter http://www.twitter.com/pagalvin
@no name
That’s what the Feature Receiver class is for. You write custom code to handle what ever you want within the Object Model in override methods within your custom Feature Reciever. See the MSDN article hier.
Hope that helps 🙂
@ Paul
I’m linking this article in this months SharePoint user group presentation because, as was discussed at this months SPUG, this is really a central issue to creating robust SharePoint features.
-john bender
nickelcode.com (blog)