Posted 8 September 2017, 12:54 pm EST
Our company has multiple developers working on the same VB.Net project, which uses the Farpoint Spread control extensively. We are having a major problem with broken references every time one of us checks the project into Visual Source Safe. As soon as a team member Gets Latest Version of the project, all Farpoint references are "broken" and must be re-referenced. We tried copying the Farpoint dlls into the C:\Program Files\Microsoft.NET\Primary Interop Assemblies directory and referencing them there, but the problem still exists. How do other developer teams handle this problem?
BTW, we have developers using XP Pro and Vista, so there seems to be an issue with the GAC working properly between the two OS.