SharePoint Sifa & Ufumbuzi Usimamizi — Usisahau U katika CRUD (au D kwa jambo hilo)

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

Tags technorati:

2 mawazo juu ya "SharePoint Sifa & Ufumbuzi Usimamizi — Usisahau U katika CRUD (au D kwa jambo hilo)

  1. Yohana Bender

    @ Hakuna jina

    Hiyo ni nini kupokea Makala darasa ni kwa. Unaweza kuandika kanuni desturi ya kushughulikia kile milele unataka ndani ya Model Object katika mbinu override ndani Reciever desturi yako Makala. Angalia makala MSDN hapa.

    Hope that helps 🙂

    @ Paulo

    Mimi kuunganisha makala hii katika hii mada miezi SharePoint mtumiaji kikundi kwa sababu, kama ilijadiliwa katika miezi hii SPUG, hii ni kweli suala la kati na kujenga makala SharePoint imara.

    -john Bender

    nickelcode.com (blog)

    Kujibu
  2. Mike Birtwistle
    When I started developing solutions and features I did look for a setting somewhere in the definition that defines what happens on deletion or update. It left me wondering if there should be a few built in behaviours to a WSP – or a swtich on stsadm – that do some of the common tasks you mentioned above such as on deleting a solution – remove everything or leave everything and on updating – kuondoa na badala au tu update ufafanuzi na kisha kuwa na fursa ya kufanya tendo desturi katika receiver kipengele.
    Kujibu

Kuondoka Reply

Anwani yako si kuchapishwa. Mashamba required ni alama *