Gastatzen dugu, kolektiboki pentsatzeko denbora asko SharePoint irtenbide buruzko — Nola hartu, zein tresna erabili, zer gertatzen den zabaldu badute, tenporizadorea lanpostu, esparru, etc. 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, diseinu kontzeptuala ikuspegitik, than deploying them. Deployment is basically a cookbook affair. Typically, instalatu ezaugarri bat, Agian Ezaugarri hartzailea kargatu datu batzuk zerrenda batean sartu, that sort of thing. Hala eta guztiz ere, atzera botatzea da potentzialki konplexuagoa.

Eman konponbidea horrelako artifacts sor ditzake:

• Eduki mota
• Zerrenda definizioa
• Gune definizioa
• Zerrenda bat datu
• Nahiz eta hargailuak
• InfoPath inprimakiak

Zerrendan doa.

Da, jakina, garrantzitsua irtenbide bat instantiates artifacts horiek behar bezala diseinatzeko, 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, zer gertatzen den irtenbidea da atzera? 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.

Hau laguntzeko, create a matrix that lists each artifact your solution deploys to SharePoint. List three columns per artifact, bat sortu, eguneratu eta ezabatu. For each case, zehazteko, eragiketa horren emaitza zuzena.

This sort of analysis is obviously best done before the solution is ever deployed to a SharePoint farm. Hala eta guztiz ere, erretzea bezalako, 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, baina, gutxienez, jarri beharko duzu kaxa bat arazoaren inguruan.

</amaiera>

Nire blog Harpidetu.

Follow me on Twitter http://www.twitter.com/pagalvin