SourceSafe and References to COM Objects
-
When managing our .NET projects with Visual SourceSafe, we encounter this problem: DeveloperA works on a .NET project. This project has a reference to a COM object. DeveloperA checks in his files into SourceSafe. Next day, DeveloperB works on the same .NET project. Although he has the same COM oject installed on his computer, the reference is invalid (indicated by a yellow triangle with an exception mark inside). DeveloperB has to delete the reference, and set a new reference to the same COM object. Is there any way to avoid this deleting and re-creating of references?
-
When managing our .NET projects with Visual SourceSafe, we encounter this problem: DeveloperA works on a .NET project. This project has a reference to a COM object. DeveloperA checks in his files into SourceSafe. Next day, DeveloperB works on the same .NET project. Although he has the same COM oject installed on his computer, the reference is invalid (indicated by a yellow triangle with an exception mark inside). DeveloperB has to delete the reference, and set a new reference to the same COM object. Is there any way to avoid this deleting and re-creating of references?
DeveloperB doesn't seem to be getting the interop assemblies created by DeveloperA. We put our interop assemblies used throughout our application in SourceSafe as well, which SourceSafe does not do by default (it doesn't add assembly references, only project files). The project still thinks it's there, however, since the .csproj file has a reference to that assembly.
Microsoft MVP, Visual C# My Articles