Karatteristiċi SharePoint & Soluzzjonijiet ta 'Ġestjoni — Tinsiex il-U fl CRUD (jew il-D għal dik il-kwistjoni)

Aħna flimkien jonfqu ammont kbir ta 'ħin jaħsbu dwar soluzzjonijiet SharePoint — kif toħloq lilhom, li għodda għall-użu, x'jiġri meta dawn jonqsu li tuża, impjiegi timer, ambiti, eċċ. 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, minn perspettiva disinn kunċettwali, than deploying them. Deployment is basically a cookbook affair. Typically, jinstallaw karatteristika, forsi jkunu riċevitur karatteristika tagħbija xi data ġo lista, that sort of thing. Madankollu, retracting huwa potenzjalment aktar kumplessa.

Soluzzjoni mogħti jista 'joħloq artifacts bħal dawn:

  • Kontenut Tip
  • Lista Definizzjoni
  • Site Definizzjoni
  • Data fil-lista
  • Anke riċevituri
  • Forom InfoPath

Il-lista tkompli.

Filwaqt li huwa ovvjament importanti li disinn soluzzjoni li instantiates dawk artifacts korrett, 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, x'jiġri meta s-soluzzjoni tiġi miġbuda lura? 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.

Biex tgħin ma 'dan, create a matrix that lists each artifact your solution deploys to SharePoint. List three columns per artifact, waħda għall joħolqu, update and delete. For each case, jiddeterminaw ir-riżultat korrett għal dik l-operazzjoni.

This sort of analysis is obviously best done before the solution is ever deployed to a SharePoint farm. Madankollu, bħat-tipjip, 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, iżda mill-inqas inti ser ikollok tpoġġi kaxxa madwar il-problema.

</aħħar>

Abbona għall-blog tiegħi.

Follow lili Twitter fi http://www.twitter.com/pagalvin

2 ħsibijiet dwar "Karatteristiċi SharePoint & Soluzzjonijiet ta 'Ġestjoni — Tinsiex il-U fl CRUD (jew il-D għal dik il-kwistjoni)

  1. John Bender

    @ Ebda isem

    Dak hu l-klassi Receiver Karatteristika hija għal. Inti tikteb kodiċi tad-dwana biex jimmaniġġaw dak li qatt trid fil-Mudell Għan fil-metodi ta 'ordni superjuri fi ħdan riċevitur tiegħek Karatteristika custom. Ara l-artikolu MSDN hawn.

    Hope that helps 🙂

    @ Paul

    Jien jgħaqqdu dan l-artikolu f'dan xhur SharePoint preżentazzjoni gruppi ta 'utenti minħabba, kif ġie diskuss fil din xhur SPUG, dan huwa verament kwistjoni ċentrali għall-ħolqien karatteristiċi SharePoint robusta.

    -john Bender

    nickelcode.com (blog)

  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 – neħħi u jissostitwixxi jew sempliċiment jaġġornaw id-definizzjoni u mbagħad ikollhom l-għażla li jagħmlu azzjoni drawwa f'riċevitur karatteristika.

Ħalli Irrispondi

Your email address mhux se jkun ippubblikat. Meħtieġa oqsma huma mmarkati *