Using Farpoint with a team of developers

Posted by: ginacresse on 8 September 2017, 12:54 pm EST

  • 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.



  • Replied 8 September 2017, 12:54 pm EST

    I would think that if you set a reference path for the project that it would always bring in the correct version of the dll's.
  • Replied 8 September 2017, 12:54 pm EST

    We would think so, too, but that's not what's happening.  We noticed differences in the directorys for the Farpoint dlls.

    Vista path: <FONT size=2>C:\Program Files\FarPoint Technologies\Spread.WinForms.3.VS2005\v3.0.2005\Bin</FONT>

    <FONT size=2>XP path: C:\Program Files\FarPoint Technologies\Spread.WinForms.3.VS2005\v3.0.2004\Bin</FONT>

    <FONT size=2>We were under the impression that since the Farpoint dlls are in the GAC, the path discrepancy would force the system to use the GAC reference, but that's not happening.  We will get the machines on the same version and hopefully that will solve.</FONT>

    <FONT size=2>Thanks

Need extra support?

Upgrade your support plan and get personal unlimited phone support with our customer engagement team

Learn More

Forum Channels