In this post I want you to show the SharePoint Installer projects from CodePlex for 2007 and from Andri Yadi for SharePoint 2010.
These guys are doing a great job!
Solution Installer SharePoint 2007:
Luckily the guys from codeplex provide an excellent basis for deploying custom solutions.
Go to http://sharepointinstaller.codeplex.com/ and download the package. After extraction you should have a folder structure as below:
The only thing which must be changed is the Config file.
Accepts a path to your own banner image. The image is automatically stretched to fit the title bar. Remove or specify empty value to omit banner image.
Accepts a path to your own logo image. Remove or specify empty value to omit banner image.
Accepts a path to your own EULA file. Remove or specify empty value if you do not want to present an EULA to the user.
Specify the GUID of your solution as indicated in the manifest.xml file within your WSP. The installer will need this to detect any existing solution in the SharePoint solution store.
Specify the filename of the solution file, e.g. mysolution.wsp. Creating the solution file is of course your job entirely - but I can highly recommend you to take a look at the Visual Studio 2005 Extensions for WSS 3.0
The title of your solution. This is displayed on various screens within the installer.
Specify the version of your solution. The upgrade option will only show if this version number is different from the previously installed solution.
Set to "Farm" if the feature in your WSP is scoped to the farm. Set to "Site" if your feature is scoped to a site collection.
This value should be identical to the Scope value specified within your feature XML file within your WSP. Features scoped to the WebApplication or Web are not currently supported.
The installer only supports installing a single feature within your WSP.
Specify the semicolon delimited list of GUIDs of the features as indicated in the feature XML files within your WSP.
The installer will automatically activate these features at the end of the installation process. Specify empty value if the installer should not activate any feature.
Text to display during an upgrade.
Set to true if you want to force deployment of your solution to all central administration web applications.
Set to true if you want to force deployment of your solution to all content web applications.
Set to true if you want the user deployment to default to all Shared Resource Providers (e.g., SSP, My Sites). The user can change this default in the deployment screen.
Set to true if your solution requires Microsoft Office SharePoint Server 2007 to install and run. Leave out or set to false if your solution will settle for a WSS only farm.
Optionally provide a relative link to a configuration page for your feature that is accessible after your farm feature is activated.
This link should be relative to the site where your feature is available (e.g., the SSP URL). This applies only to features scoped to the Farm.
Optionally provide a relative link to a configuration page for your feature that is accessible after your Site (site collection) feature is activated.
This link should be relative to any site collection where your feature is available. This applies only to features scoped to the Site (site collection).
Optionally provide a complete link to where documentation is available for your feature. This is displayed at the end of installation.
Solution Installer for SharePoint 2010:
Go to the following page http://netindonesia.net/blogs/andriyadi/archive/2010/02/27/sharepoint-2010-solution-installer.aspx and download the packages.
After extraction you should have a folder structure like below:
It's the same like the codePlex project you only need to edit the setup config file.
here is a sample configuration for a Site Feature:
There are only one new Config Key, all others has been used from the old codeplex project, so see the documentation for more infos on this.
if this is set to true the installer checks if sharePoint is really installed on the machine.
Note: This setting is currently corrupt because it will check the registry if 2010 is installed with build version 12. So please don't use it!
Dec 27 2011, 04:11 PM