My understanding of this is that you can check anyfile into sourcesafe and for applications developed for Unix everything is held in a file (there is no concept of a registry in Unix land). So all the Apache files both content and configuartion files can be checked in, after all, they are only files.
However, don't expect any high productivity integration from Microsoft between these two products as Apache is obviously a rival product to IIS. Also, Apache fans in the open source movement would recommend using an open-source source control package (what a mouthful!) such as CVS.
If you are asking if the HTTP plug-in for SourceSafe will work with Apache instead of IIS as the web server my guess would be the answer is 'no'.
Does Apache support ASP.NET Web Services If not then I don't see how things would work since the HTTP plug-in calls various ASP.NET Web Services to do the actual work of accessing the SourceSafe database.
IIS with Source Safe and Apache
onurkocoglu
My understanding of this is that you can check anyfile into sourcesafe and for applications developed for Unix everything is held in a file (there is no concept of a registry in Unix land). So all the Apache files both content and configuartion files can be checked in, after all, they are only files.
However, don't expect any high productivity integration from Microsoft between these two products as Apache is obviously a rival product to IIS. Also, Apache fans in the open source movement would recommend using an open-source source control package (what a mouthful!) such as CVS.
SteveTri
Does Apache support ASP.NET Web Services If not then I don't see how things would work since the HTTP plug-in calls various ASP.NET Web Services to do the actual work of accessing the SourceSafe database.
Arvid
The SourceSafe Web Service requires IIS and the ASP .NET 2.0 runtime.