- SharePoint 2010 - 5 Hot Features to Look Forward To
- Selecting a CMS: How to Build a Short List
- Alterian Drops Immediacy, Morello Web CMS Brands
- Installing SharePoint 2010 on Windows 7
- How SharePoint 2010’s Metadata Services Increase Usability
- Gartner’s Top 5 BPM Predictions for 2010 And Beyond
- Open Text Reports Good Q2, Vignette Contributes to YoY Spike
Get the NewsletterHow to Deploy SharePoint WebParts
There are several ways to skin the Webparts deployment cat, each with a few pluses and minuses. Thanks to Mark Harrison we have have a quick and pragmatic list of the options, complete with instructions.
Method 1 - manual
- Copy assembly DLL to either
- /bin directory for a given IIS virtual server (e.g., c:\inetpub\wwwroot\bin)
- Global Assembly Cache (e.g., c:\windows\assembly) - Copy DWP file to C:\Inetpub\wwwroot\wpcatalog
- Copy resources to
- For GAC-registered parts, C:\Program Files\Common Files\Microsoft Shared\web server extensions\wpresources
- For Web Parts in the /bin directory, C:\Inetpub\wwwroot\wpresources - Adjust web.config
- Register as SafeControl
- Select Code Access Security settings
Method 2: CAB File
- CAB file should contain
-Assembly DLL
-DWP file(s)
-Manifest.XML
-Resource files (if needed) - CAB won't contain
- Code Access Security settings - Server-side object model has methods for deploying such a CAB file
- Deploy with STSADM.EXE
Located in C:\Program Files\Common Files\Microsoft Shared\web server extensions\60\BIN
Add it to your path
Stsadm -o addwppack -filename filename [-globalinstall] [-force]
Method 3: MSI File via WPPackager
- All of the features of CAB file deployment, but with
- Code Access Security support
- Ability to uninstall via Control Panel - Get WPPackager.exe
- Add additional files to project for use by WPPackager
- Run WPPackager after project is built
Was this article useful?
Email It
Stumble It
Add RSS4 Reader Comments
Leave a Response
Processing...
From our Job Board View all jobs
| 
Jobs RSS feed
| Post a job right now
Featured Events View all events
| Events RSS feed
| Add your event
- Feb 17, 2010 – Webinar: 4 Essential Strategies for Advancing Your Website's Business Impact
- Feb 26, 2010 – Intelligent Content 2010
- Apr 21, 2010 – Drupalcon San Francisco 2010
- May 5, 2010 – CMS Expo 2010 (Evanston)
- Oct 7, 2010 – HartmanEVENT 2010 - Social Media & Mobile Usability
Hi,
Since my stsadm is showing an error, I thought of deploying webparts using irst method you suggested....but in the third step i cant get the meaning of the word "RESOURCES" that has to be copied. Kindly help me in this regard.
I am having the same questions can't you clarify the word Resources its too broad.
Thanks,
Birdbuster
i thing Resources means any images or any other supporting file for that web part.
I think Rsource file contains key/value pairs. you have to include if it presents in your project. If you are not using it in your project, you need not worry about it. It is used for localization purpose.