SPSF SharePoint Software Factory

Documentation

Version: 2.4.3
Authors: Torsten Mandelkow, Matthias Einig

1. Overview

Welcome to SPSF SharePoint Software Factory

The SPSF SharePoint Software Factory is provided by the team of SharePoint Consultants of Steria Mummert Consulting AG in Germany.

Our intention is to provide our tools and concepts to the SharePoint community to make it easier to develop custom applications in SharePoint.

SPSF is based on open technology by Microsoft

SPSF SharePoint Software Factory is based on the free Microsoft Guidance Automation Toolkit (GAX). This toolkit is used to create software factories and several software factories are already provided by Microsoft, e.g. SFSF Smart Client Software Factory, WSSF Web Service Software Factory etc.

SPSF is NOT "yet another SharePoint framework"

We want to make sure that SPSF is not a SharePoint framework which needs to be installed in SharePoint or has dependencies to custom assemblies for SharePoint applications.

SPSF helps to generate SharePoint code like a experienced developer would write. The generated code is based on our projects or taken from MSDN.
There is no dependency to SPSF. Projects created with SPSF can be opended and compiled on any other plain computer with Visual Studio 2008.

SPSF is part of SPALM SharePoint Application Lifecycle Management

SPSF SharePoint Software Factory is part of our solution "SPALM - SharePoint Application Lifecycle Management". SPALM provides strategies, methods and tools to provide real Application Lifecycle Management for SharePoint development processes, which include

SharePoint Requirements Management
SharePoint Application Architecture
SharePoint Code Generation (SPSF SharePoint Software Factory)
SharePoint Code Analysis (SPCop)
SharePoint Deployment
SharePoint Testing

How to use the SharePoint recipes

Most SharePoint recipes like "Create new Content Type" are displayed in context menus dependend on the current selection. For instance the recipe "Create new Content Type" is only displayed on projects which will create a .wsp solution.

Alternatively you can use the "New Item" dialog to run the SharePoint recipes.

More help

SPSF SharePoint SoftwareFactory provides an extensive help which is also integrated into the Visual Studio help.
More information can also be found here: www.spalmblogger.de

Further information

For more information on guidance automation, please see the following resources:

1.1. About

The Core Recipes are part of the SPALM (SharePoint Application Lifecycle Management) solution. SPALM was created by the SharePoint Consultants of Steria Mummert Consulting AG to support the implementation of SharePoint Applications with TFS.
To use the core recipes the SharePoint Software Factory (SPSF) Framework has to be installed on the development machine.
The software factory is an "extension" for Visual Studio 2008 to allow easier development of SharePoint applications. It is based on the Microsoft Guidance Automation Toolkit.

This project is intended to show the capabilities of a SharePoint software factory with some examples.
Everybody is invited:

to develop his own SharePoint software factory based on this project (please download the source code)
to support this project with new templates, recipes, code samples and snippets to increase the capabilties of this project
to help us improve the software factory by reporting bugs, feature ideas etc.

Target plattforms are

Windows SharePoint Services (WSS) 3.0
Microsoft Office SharePoint Server (MOSS) 2007
Windows SharePoint Services (WSS) 4.0 (still in development)
Microsoft SharePoint Server (MSS) 2010 (still in development)

We (as Steria Mummert Consulting AG) will further support SPALM with new recipes and templates over time. You can find slides about the software factory at our project blog at http://www.spalmblogger.de.

1.2. System Requirements

The SPSF Software Factory requires the following components:

Supported Operating Systems: Windows Server 2003 Service Pack 2; Windows Vista; Windows Vista Service Pack 1; Windows XP Service Pack 2
Visual Studio 2008 (Team System, Professional Edition or Standard Edition)
Guidance Automation Extensions - February 2008 Release (Download)

1.3. SPSF Editions

Available SPSF Editions

We provide the SharePoint Software Factory mainly to our customers. But to allow others to use the software factory for free we provide 2 editions. The only limitation is that the full version supports develoment in teams e.g. with Team Foundation Server.

SPSF Express Edition: Intended to be used by a single SharePoint developer or architect.
SPSF Team Edition: Provides additional functionality for SharePoint team development (TeamBuild with TFS, support for source control with TFS)

Differences between SPSF Editions

Functionality	Express Edition	Team Edition
Usage of recipes	Unlimited	Unlimited
Usage of project templates	Unlimited	Unlimited
Source code available	Yes	Yes
Source Control supported	No	Yes
Team Build	No	Yes

1.4. Contact

SPSF is provided by SharePoint Consultants of Steria Mummert Consulting AG in Germany.

You can reach the authors of SPSF here:

2. Recipes

2.1. Projects

2.1.1. Complex SharePoint 2007 Application

Description

Creates a complex SharePoint application.

Arguments

Name	Description
Company Name	Required String. Specifies the company name of the SharePoint application, used in copyright statements.
Application Name	Required String. Specifies the name of the SharePoint application, given by the name of the VS solution name.
Application Version	Required String. Specifies the version of the SharePoint application.
Local Webapplication for debugging	Optional Url. Name of a SharePoint webapplication for local debugging.
Generate manifest.xml automatically	Optional Boolean. If true the files manifest.xml and makecab.ddf are generated automatically.
Generate .resx files automatically	Optional Boolean. If true .resx files are generated automatically.
Add Customization Project (.wsp)	Optional Boolean. If checked a customation project (.wsp solution) is created.
Final WSP Solution Filename	Optional String. Displays the final name of the wsp solution file
WSP Solution Name	Required String. Specifies the name of the wsp solution. The final wsp solution name will be a combination of the application name (name of the VS.NET solution) and the wsp name.
Deployment Server Type	Optional String. Specifies the type of deployment server.
Deployment Target	Optional String. Specifies the deployment target.
Reset Webserver	Optional Boolean. If checked the option "ResetWebServer" in the solution manifest is set to TRUE.
Add Content Project	Project to add content to SharePoint during deployment.
Add separate project for language resources	It is a best practice to use a separate project for language resources to make new languages easier to integrate. If unchecked resources are added in each WSP solution.
Add STSADM Extensions Project	Project to add custom stsadm task which can be used during deployment.
Add SharePoint Webtest Project	Project to perform webtest after deployment (e.g. for Smoke tests).

Authors

Torsten Mandelkow

Version history

1.0 Initial Recipe

2.1.2. Content Project

Description

Adds a new content project to the solution.

Recipe Description

Content projects are used to deploy content to the ContentDB during deployment. Typically this could be SharePoint Designer Workflows, master pages etc.

Authors

Torsten Mandelkow

Version history

1.0 Initial Recipe

2.1.3. Customization Project (WSP)

Description

Adds a new customization project (wsp) to the solution.

Recipe Description

A customation project is the core wsp solution project type to deploy a .wsp solution to SharePoint.

Arguments

Name	Description
Final WSP Solution Filename	Optional String. Displays the final name of the wsp solution file
Deployment Server Type	Optional String. Specifies the type of deployment server.
Deployment Target	Optional String. Specifies the deployment target.
Reset Webserver	Optional Boolean. If checked the option "ResetWebServer" in the solution manifest is set to TRUE.

Authors

Torsten Mandelkow

Version history

1.0 Initial Recipe

2.1.4. MSBuild Task Project

Description

Authors

Torsten Mandelkow

Version history

1.0 Initial Recipe

2.1.5. MSBuild Task

Description

Adds a custom msbuild task to the project.

Arguments

Name	Description
Task Name

Authors

Torsten Mandelkow

Version history

1.0 Initial Recipe

2.1.6. Resources Project (WSP)

Description

Adds a new resources (wsp) project to the solution.

Recipe Description

A resources project is deployed as a wsp solution and should contain only .resx files to support multiple languages.

Arguments

Name	Description
Final WSP Solution Filename	Optional String. Displays the final name of the wsp solution file
Deployment Server Type	Optional String. Specifies the type of deployment server.
Deployment Target	Optional String. Specifies the deployment target.
Reset Webserver	Optional Boolean. If checked the option "ResetWebServer" in the solution manifest is set to TRUE.

Authors

Torsten Mandelkow

Version history

1.0 Initial Recipe

2.1.7. Simple SharePoint 2007 Application

Description

Creates a simple SharePoint application.

Arguments

Name	Description
Company Name	Required String. Specifies the company name of the SharePoint application, used in copyright statements.
Application Name	Required String. Specifies the name of the SharePoint application, given by the name of the VS solution name.
Application Version	Required String. Specifies the version of the SharePoint application.
Local Webapplication for debugging	Optional Url. Name of a SharePoint webapplication for local debugging.
Generate manifest.xml automatically	Optional Boolean. If true the files manifest.xml and makecab.ddf are generated automatically.
Generate .resx files automatically	Optional Boolean. If true .resx files are generated automatically.
Final WSP Solution Filename	Optional String. Displays the final name of the wsp solution file
WSP Solution Name	Required String. Specifies the name of the wsp solution. The final wsp solution name will be a combination of the application name (name of the VS.NET solution) and the wsp name.
Deployment Server Type	Optional String. Specifies the type of deployment server.
Deployment Target	Optional String. Specifies the deployment target.
Reset Webserver	Optional Boolean. If checked the option "ResetWebServer" in the solution manifest is set to TRUE.

Authors

Torsten Mandelkow

Version history

1.0 Initial Recipe

2.1.8. SharePoint 2010 Application (experimental)

Description

Creates a experimental SharePoint 2010 application.

Arguments

Name	Description
Company Name	Required String. Specifies the company name of the SharePoint application, used in copyright statements.
Application Name	Required String. Specifies the name of the SharePoint application, given by the name of the VS solution name.
Application Version	Required String. Specifies the version of the SharePoint application.
Local Webapplication for debugging	Optional Url. Name of a SharePoint webapplication for local debugging.
Generate manifest.xml automatically	Optional Boolean. If true the files manifest.xml and makecab.ddf are generated automatically.
Generate .resx files automatically	Optional Boolean. If true .resx files are generated automatically.
Final WSP Solution Filename	Optional String. Displays the final name of the wsp solution file
WSP Solution Name	Required String. Specifies the name of the wsp solution. The final wsp solution name will be a combination of the application name (name of the VS.NET solution) and the wsp name.
Deployment Server Type	Optional String. Specifies the type of deployment server.
Deployment Target	Optional String. Specifies the deployment target.
Reset Webserver	Optional Boolean. If checked the option "ResetWebServer" in the solution manifest is set to TRUE.

Authors

Torsten Mandelkow

Version history

1.0 Initial Recipe

2.1.9. STSADM Command

Description

Adds a stsadm command to the selected project.

Arguments

Name	Description
Name
Class Name

Authors

Torsten Mandelkow

Version history

1.0 Initial Recipe

2.1.10. STSADM Extensions Project

Description

Authors

Torsten Mandelkow

Version history

1.0 Initial Recipe

2.2. Deployment

2.2.1. Configure Project

Description

Configures general settings of the selected project.

Recipe Description

Configures the generell settings of the project.

Arguments

Name	Description
DeploymentTarget

Authors

Torsten Mandelkow

Version history

1.0 Initial Recipe

2.2.2. Deploy Solution(s)

Description

Deploys the selected wsp solution(s) to the local SharePoint farm.

Recipe Description

The recipe deploys the selected project(s) to the local SharePoint farm.

If the wsp solution contains web application resources the solution is deployed to a specific web application. This specific web application can be configured with "Configure Deployment".

Authors

Torsten Mandelkow

Version history

1.0 Initial Recipe

2.2.3. Redeploy Solution(s)

Description

Redeploys the selected wsp solution(s) to the local SharePoint farm (complete undeploy before a deploy).

Authors

Torsten Mandelkow

Version history

1.0 Initial Recipe

2.2.4. Undeploy Solution(s)

Description

Undeploys the selected wsp solution from the local SharePoint farm (retract and delete solution).

Authors

Torsten Mandelkow

Version history

1.0 Initial Recipe

2.2.5. Upgrade Solution(s)

Description

Upgrades the selected wsp solution in the local SharePoint farm.

Authors

Torsten Mandelkow

Version history

1.0 Initial Recipe

2.3. Quick Deploy

2.3.1. Copy Assembly

Description

Copies the assembly of the selected project to GAC.

Authors

Torsten Mandelkow

Version history

1.0 Initial Recipe

2.3.2. Copy Both

Description

Copies the assembly of the selected project to GAC and all files in folder "12".

Authors

Torsten Mandelkow

Version history

1.0 Initial Recipe

2.3.3. Copy to SharePoint Hive

Description

Copies all files in project folder "12" or "14" to the SharePoint hive on the local machine.

Authors

Torsten Mandelkow

Version history

1.0 Initial Recipe

2.4. Debugging

2.4.1. Attach to Worker Process

Description

Starts the debugging of the selected project and attaches the debugger to the selected w3wp worker process (IIS).

Arguments

Name	Description
Worker Process	Select the worker process.

Authors

Torsten Mandelkow

Version history

1.0 Initial Recipe

2.4.2. Recycle App Pool

Description

Recycles the selected application pool in IIS.

Arguments

Name	Description
Application Pool	Select the application pool.

Authors

Torsten Mandelkow

Version history

1.0 Initial Recipe

2.4.3. IIS Reset

Description

Performs an iisreset on the local maschine.

Authors

Torsten Mandelkow

Version history

1.0 Initial Recipe

2.4.4. Attach to owstimer.exe

Description

Starts the debugging of the selected project and attaches the debugger to the ows timer process (OWSTIMER.EXE).

Authors

Torsten Mandelkow

Version history

1.0 Initial Recipe

2.4.5. Restart owstimer.exe

Description

Restarts the owstimer service.

Authors

Torsten Mandelkow

Version history

1.0 Initial Recipe

2.5. STSADM

2.5.1. stsadm activatefeature

Description

Activates the selected feature in the selected site or web.

Recipe Description

This recipe is helpfull if hidden features are deployed and a feature needs to be activated via stsadm -o activatefeature.

Arguments

Name	Description
Feature Id	Select the feature to activate.
Url

Authors

Torsten Mandelkow

Version history

1.0 Initial Recipe

2.5.2. stsadm deactivatefeature

Description

Deactivates the selected feature in the selected site or web.

Recipe Description

This recipe is helpfull if hidden features are deployed and a feature needs to be deactivated via stsadm -o activatefeature.

Arguments

Name	Description
Feature Id	Select the feature to activate.
Url

Authors

Torsten Mandelkow

Version history

1.0 Initial Recipe

2.5.3. stsadm uninstallfeature

Description

Uninstalls the selected feature.

Recipe Description

Uninstalls the selected feature. This is useful if e.g. by corrupt solution deployments some features are still registered in the database, but the feature folder is already removed.

Arguments

Name	Description
Feature Id	Select the feature to activate.

Authors

Torsten Mandelkow

Version history

1.0 Initial Recipe

2.5.4. stsadm copyappbincontent

Description

Runs stsadm -o copyappbincontent.

Authors

Torsten Mandelkow

Version history

1.0 Initial Recipe

2.5.5. stsadm execadmsvcjobs

Description

Runs stsadm -o execadmsvcjobs to run all pending deployment jobs.

Authors

Torsten Mandelkow

Version history

1.0 Initial Recipe

2.5.6. Open stsadm Prompt

Description

Opens a prompt to enter stsadm commands manually.

Authors

Torsten Mandelkow

Version history

1.0 Initial Recipe

2.6. CodeAnalysis

2.6.1. Run SPCop

Description

Checks to SharePoint project for violations of best practices and recommendations

Authors

Torsten Mandelkow

Version history

1.0 Initial Recipe

2.6.2. Run SPDisposeChecker

Description

Runs SPDisposeChecker for selected project.

Authors

Torsten Mandelkow

Version history

1.0 Initial Recipe

2.7. Shortcuts

2.7.1. Debugging Webapp

Description

Opens the debugging webapplication of the project in the browser.

Recipe Description

This recipe provides a shortcut to the debugging webapplication of the current selected project.

Authors

Torsten Mandelkow

Version history

1.0 Initial Recipe

2.7.2. Central Administration

Description

Displays the Central Administration.

Recipe Description

This recipe provides a shortcut to the local Central Administration in SharePoint, e.g. create a new site collection or check farm features.

Authors

Torsten Mandelkow

Version history

1.0 Initial Recipe

2.7.3. Central Administration Solution Management

Description

Displays the web page "Solution Management" in SharePoint Central Administration.

Recipe Description

This recipe provides a shortcut to the Solution Management in SharePoint, e.g. to check which solutions are deployed or undeployed.

Authors

Torsten Mandelkow

Version history

1.0 Initial Recipe

2.8. Helpers

2.8.1. Check Broken Fields

Description

Checks a site collection for fields which are not properly installed.

Recipe Description

During development of custom fields or custom field types sometimes the list of available fields in a site collection cannot be loaded because of a "broken" field. In the SharePoint you will get the error message on page "Site Columns".
The given key was not present in the dictionary. at System.ThrowHelper.ThrowKeyNotFoundException()
at System.Collections.Generic.Dictionary`2.get_Item(TKey key)
at Microsoft.SharePoint.SPFieldCollection.CreateSPField(Int32 index)
at Microsoft.SharePoint.SPFieldCollection.EnsureSPField(Int32 index)
at Microsoft.SharePoint.SPFieldCollection.get_Item(Int32 iIndex)
at Microsoft.SharePoint.SPFieldCollection.ItemAtIndex(Int32 iIndex)
at Microsoft.SharePoint.SPBaseCollection.SPEnumerator.System.Collections.IEnumerator.get_Current()
at Microsoft.SharePoint.ApplicationPages.FieldListRenderer.OnPreRender(EventArgs e)
at System.Web.UI.Control.PreRenderRecursiveInternal()
at System.Web.UI.Control.PreRenderRecursiveInternal()
at System.Web.UI.Control.PreRenderRecursiveInternal()
at System.Web.UI.Control.PreRenderRecursiveInternal()
at System.Web.UI.Control.PreRenderRecursiveInternal()
at System.Web.UI.Control.PreRenderRecursiveInternal()
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

This recipe helps to find the fields which are not installed properly.

Arguments

Name	Description
Site Collection Url	Enter the url of a local site collection to check for broken fields.

Authors

Torsten Mandelkow

Version history

1.0 Initial Recipe

2.8.2. Delete Failed Deployment Jobs

Description

Deletes failed deployment jobs in the local SharePoint farm.

Recipe Description

This handy recipe helps if deployments of wsp solutions failed, e.g. during clean up. If these failed jobs are not deleted new solutions with the same name can not be deployed. The recipe searches for failed jobs and deletes them.

Authors

Torsten Mandelkow

Version history

1.0 Initial Recipe

2.8.3. Exclude item from SourceControl

Description

Removes the item from source control, e.g. import for manifest.xml and makecab.ddf to enable automatic generation of these files.

Recipe Description

The recipe removes a file from source control to avoid conflicts during build.

Authors

Torsten Mandelkow

Version history

1.0 Initial Recipe

2.8.4. Run MSBuild Target

Description

Runs a target from an msbuild file.

Arguments

Name	Description
Build Target	Name of the target to be executed.

Authors

Torsten Mandelkow

Version history

1.0 Initial Recipe

2.8.5. Run Batch

Description

Execute the selected batch file (.bat).

Recipe Description

The recipe open a new process to run the selected batch file. The recipe is useful to start the execution of a batch file directly from within Visual Studio.

Authors

Torsten Mandelkow

Version history

1.0 Initial Recipe

2.8.6. Get AssemblyName

Description

Displays the full assembly name of the current selected project.

Recipe Description

The assembly name of often needed during development, e.g. to specify the assembly of a feature receiver in the feature.xml.

Arguments

Name	Description
Assembly Name

Authors

Torsten Mandelkow

Version history

1.0 Initial Recipe

2.8.7. Get SharePoint Version

Description

Displays the version of SharePoint on the local machine.

Arguments

Name	Description
SharePoint Version

Authors

Torsten Mandelkow

Version history

1.0 Initial Recipe

2.8.8. Remove TextTemplating Transformation

Description

Makes a .tt-file static to enable direct editing of the file.

Recipe Description

Recipe changes a .tt file to a static file. This is usefull e.g. for transforming manifest.tt to manifest.xml to enable editing of manifest.xml.

Authors

Torsten Mandelkow

Version history

1.0 Initial Recipe

2.8.9. Open in Browser

Description

Opens the selected item in browser.

Recipe Description

The recipe opens the selected file in browser. The recipe is useful to open deployed file in SharePoint directly from within Visual Studio.

Authors

Torsten Mandelkow

Version history

1.0 Initial Recipe

2.8.10. Show Properties

Description

Shows the properties of the item.

Recipe Description

Recipe displays the properties in visual studio of the current item. This is used for debugging purposes within Visual Studio.

Authors

Torsten Mandelkow

Version history

1.0 Initial Recipe

2.9. Help

2.9.1. Load SharePoint Configuration

Description

Reloads the file SharePointConfiguration.xml with the contents of the local SharePoint farm (features, listtemplates, content types etc.).

Recipe Description

In several dialogs within the wizards a list of SharePoint elements is provided to the user (e.g. list of available features, content types etc.). The values for this list are taken from the file SharePointConfiguration.xml, which should be located in the current solution.

This recipe recreates the file SharePointConfiguration.xml with the data from the local computer.

Authors

Torsten Mandelkow

Version history

1.0 Initial Recipe

2.9.2. Recipe Index

Description

Displays a list of all recipes in the current Guidance Package.

Authors

Torsten Mandelkow

Version history

1.0 Initial Recipe

3. License

GNU General Public License version 2 (GPLv2)

Copyright (C) 1989, 1991 Free Software Foundation, Inc. 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA

Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.

Preamble

The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change free software--to make sure the software is free for all its users. This General Public License applies to most of the Free Software Foundation's software and to any other program whose authors commit to using it. (Some other Free Software Foundation software is covered by the GNU Library General Public License instead.) You can apply it to your programs, too.

When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs; and that you know you can do these things.

To protect your rights, we need to make restrictions that forbid anyone to deny you these rights or to ask you to surrender the rights. These restrictions translate to certain responsibilities for you if you distribute copies of the software, or if you modify it.

For example, if you distribute copies of such a program, whether gratis or for a fee, you must give the recipients all the rights that you have. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights.

We protect your rights with two steps: (1) copyright the software, and (2) offer you this license which gives you legal permission to copy, distribute and/or modify the software.

Also, for each author's protection and ours, we want to make certain that everyone understands that there is no warranty for this free software. If the software is modified by someone else and passed on, we want its recipients to know that what they have is not the original, so that any problems introduced by others will not reflect on the original authors' reputations.

Finally, any free program is threatened constantly by software patents. We wish to avoid the danger that redistributors of a free program will individually obtain patent licenses, in effect making the program proprietary. To prevent this, we have made it clear that any patent must be licensed for everyone's free use or not licensed at all.

The precise terms and conditions for copying, distribution and modification follow.

TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION

0. This License applies to any program or other work which contains a notice placed by the copyright holder saying it may be distributed under the terms of this General Public License. The "Program", below, refers to any such program or work, and a "work based on the Program" means either the Program or any derivative work under copyright law: that is to say, a work containing the Program or a portion of it, either verbatim or with modifications and/or translated into another language. (Hereinafter, translation is included without limitation in the term "modification".) Each licensee is addressed as "you".

Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running the Program is not restricted, and the output from the Program is covered only if its contents constitute a work based on the Program (independent of having been made by running the Program). Whether that is true depends on what the Program does.

1. You may copy and distribute verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any warranty; and give any other recipients of the Program a copy of this License along with the Program.

You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee.

2. You may modify your copy or copies of the Program or any portion of it, thus forming a work based on the Program, and copy and distribute such modifications or work under the terms of Section 1 above, provided that you also meet all of these conditions:

a) You must cause the modified files to carry prominent notices stating that you changed the files and the date of any change.

b) You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the Program or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this License.

c) If the modified program normally reads commands interactively when run, you must cause it, when started running for such interactive use in the most ordinary way, to print or display an announcement including an appropriate copyright notice and a notice that there is no warranty (or else, saying that you provide a warranty) and that users may redistribute the program under these conditions, and telling the user how to view a copy of this License. (Exception: if the Program itself is interactive but does not normally print such an announcement, your work based on the Program is not required to print an announcement.)

These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Program, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Program, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it.

Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the intent is to exercise the right to control the distribution of derivative or collective works based on the Program.

In addition, mere aggregation of another work not based on the Program with the Program (or with a work based on the Program) on a volume of a storage or distribution medium does not bring the other work under the scope of this License.

3. You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you also do one of the following:

a) Accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,

b) Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,

c) Accompany it with the information you received as to the offer to distribute corresponding source code. (This alternative is allowed only for noncommercial distribution and only if you received the program in object code or executable form with such an offer, in accord with Subsection b above.)

The source code for a work means the preferred form of the work for making modifications to it. For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable. However, as a special exception, the source code distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable.

If distribution of executable or object code is made by offering access to copy from a designated place, then offering equivalent access to copy the source code from the same place counts as distribution of the source code, even though third parties are not compelled to copy the source along with the object code.

4. You may not copy, modify, sublicense, or distribute the Program except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense or distribute the Program is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance.

5. You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Program or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Program (or any work based on the Program), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Program or works based on it.

6. Each time you redistribute the Program (or any work based on the Program), the recipient automatically receives a license from the original licensor to copy, distribute or modify the Program subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties to this License.

7. If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not limited to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not distribute the Program at all. For example, if a patent license would not permit royalty-free redistribution of the Program by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Program.

If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance of the section is intended to apply and the section as a whole is intended to apply in other circumstances.

It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest validity of any such claims; this section has the sole purpose of protecting the integrity of the free software distribution system, which is implemented by public license practices. Many people have made generous contributions to the wide range of software distributed through that system in reliance on consistent application of that system; it is up to the author/donor to decide if he or she is willing to distribute software through any other system and a licensee cannot impose that choice.

This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License.

8. If the distribution and/or use of the Program is restricted in certain countries either by patents or by copyrighted interfaces, the original copyright holder who places the Program under this License may add an explicit geographical distribution limitation excluding those countries, so that distribution is permitted only in or among countries not thus excluded. In such case, this License incorporates the limitation as if written in the body of this License.

9. The Free Software Foundation may publish revised and/or new versions of the General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns.

Each version is given a distinguishing version number. If the Program specifies a version number of this License which applies to it and "any later version", you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of this License, you may choose any version ever published by the Free Software Foundation.

10. If you wish to incorporate parts of the Program into other free programs whose distribution conditions are different, write to the author to ask for permission. For software which is copyrighted by the Free Software Foundation, write to the Free Software Foundation; we sometimes make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally.

NO WARRANTY

11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.

12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.