Mi kolektivno provode mnogo vremena razmišljajući o SharePoint rješenja — kako ih stvoriti, koji alat koristiti, što se događa kada se oni ne uspiju rasporediti, timer radnih mjesta, opsega, itd.. 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, od idejnog rješenja perspektive, than deploying them. Deployment is basically a cookbook affair. Typically, instalirajte značajku, možda su prijemnik značajka učitati neke podatke u popisu, that sort of thing. Međutim, Uvlačenje je potencijalno složeniji.

Dati rješenje može stvoriti artefakte poput ovih:

• Vrsta sadržaja
• Popis Definicija
• Site Definicija
• Podaci u popisu
• Čak prijemnici
• InfoPath obrasci

Popis ide na.

Iako je očito važno dizajnirati rješenje da instantiates one artefakte ispravno, 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, što se događa kada se povukao rješenje? 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.

Za pomoć s ovim, create a matrix that lists each artifact your solution deploys to SharePoint. List three columns per artifact, jedan za stvaranje, ažuriranje i brisanje. For each case, odrediti točan ishod za tu operaciju.

This sort of analysis is obviously best done before the solution is ever deployed to a SharePoint farm. Međutim, kao što su pušenje, 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, ali barem ćete stavili okvir oko problema.

</kraj>

Pretplatite se na moj blog.

Slijedite me na Twitter-u http://www.twitter.com/pagalvin