Sisi kwa pamoja kutumia mpango mkubwa wa kufikiri kuhusu wakati SharePoint ufumbuzi — jinsi ya kujenga yao, zana ipi ya kutumia, kile kinachotokea wakati wao kushindwa kupeleka, timer ajira, scopes, nk. 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, kutoka katika mtazamo wa dhana kubuni, than deploying them. Deployment is basically a cookbook affair. Typically, kufunga kipengele, labda kuwa receiver kipengele mzigo data baadhi katika orodha, that sort of thing. Hata hivyo, retracting ni uwezekano ngumu zaidi.

ufumbuzi kutokana na inaweza kujenga mabaki kama haya:

• Aina ya maudhui
• Orodha ya Ufafanuzi
• Ufafanuzi tovuti
• Data katika orodha
• Hata kupokea
• InfoPath aina

orodha inaendelea.

Wakati ni wazi muhimu kwa kubuni ufumbuzi kwamba instantiates mabaki ya wale usahihi, 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, kile kinachotokea wakati ufumbuzi ni retracted? 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.

Kwa msaada na hii, create a matrix that lists each artifact your solution deploys to SharePoint. List three columns per artifact, moja kwa ajili ya kujenga, update and delete. For each case, kuamua matokeo sahihi kwa ajili ya operesheni ambayo.

This sort of analysis is obviously best done before the solution is ever deployed to a SharePoint farm. Hata hivyo, kama sigara, 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, lakini angalau wewe utakuwa na kuweka sanduku kuzunguka tatizo.

</mwisho>

Kujiunga na blog yangu.

Kufuata yangu juu ya Twitter kwa http://www.twitter.com/pagalvin