Deployment providers provide a light weight mechanism for associating a provider with a folder and persisting the mapping state. By implementing a deployment provider there are no explicit workflows implied that you must adhere to. Deployment providers can be associated within a project that is already associated with a repository provider, but the deployment provider doesn't have control over the project's resources. You can image a deployment provider co-existing with the repository to provide say an easy mechanism for deploying part of a project to a test server.
The following sections will explain how to implement a deployment provider.
Create a concrete instance of Deployment provider and decide what information must be persisted between sessions.