By default, when a project is bound to source control, the provider (Git, Perforce Helix Core, Subversion, or Team Foundation Server) is enabled. This means that the source control interface elements in Flare are visible, and you can use them to perform various tasks (e.g., commits, synchronize changes).
Disabling a provider means that the source control interface elements are no longer shown. This does not mean you cannot use source control. As long as the provider is still bound to the project, you can perform source control tasks in a third-party tool outside of Flare.
How to Disable a Provider
Use this method if you want to disable a provider in just one project, rather than many projects.
- Do one of the following, depending on the part of the user interface you are using:
Project Properties Select Project > Project Properties.
- Source Control Explorer Select View > Source Control Explorer. Then, in the window pane, click Settings.
-
Click Enabled to remove the check mark.
-
If you used the Project Properties dialog, click OK.
Note If you disable a Git provider, the local repository will continue to track your changes in case you later decide to enable the provider once again.
If you disable one of the other providers (Perforce Helix Core, Subversion, Team Foundation Server), your changes after that point will not be tracked. Therefore, if you later enable the provider again, it will not have recorded any changes made since the time that you disabled it.
Note When you disable a provider, that information is written to the registry on your computer.
Note If you disable a provider, but then perform one of the following actions in the Flare interface, the provider will automatically become enabled once again.
-
Bind an existing project
-
Bind a new project
-
Bind a project to Central (either as secondary or primary provider)
-
Import a project from source control
-
Import a project from Central
Note Having a provider enabled in Flare does not interfere with your workflow if you are performing source control actions exclusively outside of Flare. Even if a provider is enabled in the project and the source control user interface elements are visible, this does not mean Flare is automatically performing any source control actions with your files. It simply means Flare is recognizing the binding, so it reflects your activities (e.g., the Pending Changes window is populated when you make edits in topics). However, if you prefer not to see any of this in Flare, you can disable the provider.
