How to: Install a source control plug-in. 5 minutes to read.In this articleCreating a source-control plug-in involves three steps:.Create a DLL with the functions defined in the Source Control Plug-in API reference section of this documentation.Implement the Source Control Plug-in API-defined functions. When Visual Studio calls for it, make interfaces and dialog boxes available from the plug-in.Register the DLL by making appropriate registry entries.Integration with Visual StudioVisual Studio supports source control plug-ins that conform to the Source Control Plug-in API. Register the source control plug-inBefore a running integrated development environment (IDE) can call into the source control system, it must first find the source control plug-in DLL that exports the API. To register the source control plug-in DLL.Add two entries under the HKEYLOCALMACHINE key in the SOFTWARE subkey that specifies your company name subkey followed by your product name subkey.
Microsoft Visual SourceSafe 2005 cannot be downloaded. The page and product should be removed as there is no download available what so ever. Results 1–2 of 2.
The pattern is HKEYLOCALMACHINESOFTWARE = value. The two entries are always called SCCServerName and SCCServerPath. Each is a regular string.For example, if your company name is Microsoft and your source control product is named SourceSafe, then this registry path would be HKEYLOCALMACHINESOFTWAREMicrosoftSourceSafe.
In this subkey, the first entry, SCCServerName, is a user-readable string naming your product. The second entry, SCCServerPath, is the full path to the source control plug-in DLL that the IDE should connect to. The following provides sample registry entries: Sample Registry entrySample valueHKEYLOCALMACHINESOFTWAREMicrosoftSourceSafeSCCServerNameMicrosoft Visual SourceSafeHKEYLOCALMACHINESOFTWAREMicrosoftSourceSafeSCCServerPathc:vsswin32ssscc.dll. NoteSCCServerPath is the full path to the SourceSafe plug-in. Your source control plug-in will use different company and product names but the same registry entry paths.The following optional registry entries can be used to modify the behavior of your source control plug-in. These entries go in the same subkey as SccServerName and SccServerPath.The HideInVisualStudioregistry entry can be used if you do not want your source control-plug-in to appear in the Plug-in Selection list of Visual Studio. This entry will also affect automatic switching to the source control plug-in.
One possible use for this entry is if you supply a source control package that replaces your source control plug-in but you want to make it easier for the user to migrate from using the source control plug-in to the source control package. When the source control package is installed, it sets this registry entry, which hides the plug-in.HideInVisualStudio is a DWORD value and is set to 1 to hide the plug-in or 0 to show the plug-in. If the registry entry does not appear, the default behavior is to show the plug-in.The DisableSccManager registry entry can be used to disable or hide the Launch menu option that normally appears under the File Source Control submenu.
Selecting this menu option calls the function. Your source control plug-in may not support an external program and therefore you may want to disable or even hide the Launch menu option.DisableSccManager is a DWORD value and is set to 0 to enable the Launch menu option, set to 1 to disable the menu option, and set to 2 to hide the menu option. If this registry entry does not appear, the default behavior is to show the menu option.Sample registry entrySample valueHKEYLOCALMACHINESOFTWAREMicrosoftSourceSafeHideInVisualStudio1HKEYLOCALMACHINESOFTWAREMicrosoftSourceSafeDisableSccManager1.Add the subkey, SourceCodeControlProvider, under the HKEYLOCALMACHINE key in the SOFTWARE subkey.Under this subkey, the registry entry ProviderRegKey is set to a string that represents the subkey that you placed in the registry in step 1. The pattern is HKEYLOCALMACHINESOFTWARESourceCodeControlProviderProviderRegKey = SOFTWARE.The following is sample content for this subkey.
Registry entrySample valueHKEYLOCALMACHINESOFTWARESourceCodeControlProviderProviderRegKeySOFTWAREMicrosoftSourceSafe. NoteYour source control plug-in will use the same subkey and entry names, but the value will be different.Create a subkey named InstalledSCCProviders under the SourceCodeControlProvider subkey, and then place one entry under that subkey.The name of this entry is the user-readable name of the provider (the same as the value specified for the SCCServerName entry), and the value is, once again, the subkey created in step 1. The pattern is HKEYLOCALMACHINESOFTWARESourceCodeControlProviderInstalledSCCProviders = SOFTWARE.For example: Sample registry entrySample valueHKEYLOCALMACHINESOFTWARESourceCodeControlProviderInstalledSCCProvidersMicrosoft Visual SourceSafeSOFTWAREMicrosoftSourceSafe. NoteThere can be multiple source control plug-ins registered in this way.
This is how Visual Studio finds all installed Source Control Plug-in API-based plug-ins.How an IDE locates the DLLThe Visual Studio IDE has two ways of finding the source control plug-in DLL:.Find the default source control plug-in and connect to it silently.Find all registered source control plug-ins, from which the user chooses one.To locate the DLL in the first way, the IDE looks under the HKEYLOCALMACHINESoftwareSourceCodeControlProvider subkey for the entry ProviderRegKey. The value of this entry points to another subkey. The IDE then looks for an entry named SccServerPath in that second subkey under HKEYLOCALMACHINE. The value of this entry points the IDE to the DLL.
NoteThe IDE does not load DLLs from relative paths (for example,.NewProvider.DLL). A full path to the DLL must be specified (for example, c:ProvidersNewProvider.DLL). This strengthens the security of the IDE by preventing the loading of unauthorized or impersonated plug-in DLLs.To locate the DLL in the second way, the IDE looks under the HKEYLOCALMACHINESoftwareSourceCodeControlProviderInstalledSCCProviders subkey for all entries. Each entry has a name and a value.
The IDE displays a list of these names to the user. When the user chooses a name, the IDE finds the value for the selected name that points to a subkey.
The IDE looks for an entry named SccServerPath in that subkey under HKEYLOCALMACHINE. The value of that entry points the IDE to the correct DLL.A source control plug-in needs to support both ways of finding the DLL and, consequently, sets ProviderRegKey, overwriting any previous setting.
More importantly, it must add itself to the list of InstalledSccProviders so the user can have a choice of which source control plug-in to use. NoteBecause the HKEYLOCALMACHINE key is used, only one source control plug-in can be registered as the default source control plug-in on a given machine (however, Visual Studio allows users to determine which source control plug-in they want to actually use for a particular solution). During your installation process, check to see if a source control plug-in is already set; if so, ask the user whether or not to set the new source control plug-in being installed as the default.
During uninstallation, do not remove other registry subkeys that are common to all source control plug-ins in HKEYLOCALMACHINESOFTWARESourceCodeControlProvider; remove only your particular SCC subkey. How the IDE detects version 1.2/1.3 supportHow does Visual Studio detect whether a plug-in supports Source Control Plug-in API version 1.2 and 1.3 functionality? To declare advanced capability, the source control plug-in must implement the corresponding function:First, Visual Studio checks the value returned by calling the. It must be greater than or equal to 1.2.Next, Visual Studio determines whether the particular new capability is supported by examining the lpSccCaps argument on the.If both of these conditions are met, the new functions supported in versions 1.2 and 1.3 can be called. See also.Recommended Content.
Okay, this response is not clear. Are you saying that you can NOT purchase VSS in any manner, unless you purchase VS Team addition?Because this is what you infer with your statements. If this is so, then why do we all see Visual Source Safe.NET for sale all over the place?Why would a company not sell a product unless someone spends a ridiculous 4K+? We don't need or want all those bells and whistles (never mind the fact that it took a good 4 months for us to find someone at Microsoft who actually understand what.was. in each 'edition' of VS.NET-that was a lot of fun).So could you please be clear?
Are you saying that all those ads selling VSS.NET for 4-500 dollars are illegal or something? The question to which I replied asked if there was a way in which it is possible to download Visual Source Safe. I answered that if you have an MSDN subscription at the appropriate level (eg. Universal), it is possible to download the product immediately, before the DVDs ship. I made no inferences about whether or not it is possible to purchase VS.NET separately.In my first post on this thread, I indicated that it VSS comes with an appropriate MSDN subscription.
It is true that VS is also available to purchase separately, as you have indicated. A quick search of Google reveals many links to purchase the product, and anyone who followed the link that I posted in my first reply would also have been able to find this out by reading the other thread. I am lost, I cannot find the Visual Source Save. I have never used it for souce control before i came here a few months ago. I took over a position, and the incumbant is gone. My new work computer started blue screening after the lastest patch, so I rebuilt it.
I have the M$ VS 2005 pro cds (2), the M$ VS 2005 pro MSDN CDs (3), the M$ VS 2005 sql Developer cds (32bit x2, 64 bit x2), all holografic genuine, and i have 16 computers in my building, all with MS Visual Studio 2005, and the source safe client on them. No one has any clue where the Source safe client install is.
Is it on one of these cds, am i missing a CD? Respectfully Requested - Jon.