FpChart cannot work with COMM232.dll

Posted by: kukemaster on 8 September 2017, 2:59 pm EST

  • Posted 8 September 2017, 2:59 pm EST

    Run this sample, click "Step 1" then click "Step 2", [Dim YPlotArea1 As FarPoint.Win.Chart.YPlotArea = New FarPoint.Win.Chart.YPlotArea()] throw a exception that is "An unhandled exception of type 'System.StackOverflowException' occurred in FarPoint.Win.Chart.dll"

    What is the reason.

     VS2010 + Spread .NET 6.0.3505 + Win7


    2012/09/test1.zip
  • Replied 8 September 2017, 2:59 pm EST

    Hello,

    I was able to replicate the issue at my end and I went through the code in your sample. I was not able to find COMM232.dll that you are referring in a function anywhere in your project. Could you please let me know what this dll is exactly doing and why do you need this in your project. I would also like to know if you are facing this issue even if you do not refer to this dll in your project. Please provide me with the necessary information so that I can debug the issue further at my end.

    Thanks,

    Manpreet Kaur

  • Replied 8 September 2017, 2:59 pm EST

    Thank you!

     you can find COMM232.dll in "test1\bin\Debug', and you can search comm232.dll in goolge.

  • Replied 8 September 2017, 2:59 pm EST

    Hello,

    Thank you for the information, I was able to find comm232.dll in the bin debug folder but I was not able to gather much information about the same from Google. Could you please provide me some information about why are you exactly referring to this dll in your project and do you even get the exception when you do not refer to this dll in your code. Please guide me with some information on the same so that I can debug the issue further.

    Thanks,

    Manpreet Kaur

  • Replied 8 September 2017, 2:59 pm EST

    Hi, 

    Thank you for your reply. But I can't get you more infomation. Comm232.dll is a third component, so can you debug this issue with spread's source code.

  • Replied 8 September 2017, 2:59 pm EST

    Hello,

    I am not very sure why exactly are you facing this issue. I have reported the issue as a bug to the development team to look into the issue further. The bug number for the same is #99928233. It would be fixed in the next maintenance release.

    Thanks,

    Manpreet Kaur

Need extra support?

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

Learn More

Forum Channels