Spread icons are disabled in the Toolbar

Posted by: sistemas on 11 October 2018, 1:19 pm EST

    • Post Options:
    • Link

    Posted 11 October 2018, 1:19 pm EST

    Buy a spread license, install it and activate it, but when generating a new application the buttons (icons) are deactivated and I can not add control to the page, someone could help me with this please. Thanks in advance

  • Posted 11 October 2018, 2:33 pm EST

    Hello,

    Please make sure that the .Net Framework of your application is set to .Net Framework 4.5.2 or later as this is the product requirement:-

    http://help.grapecity.com/spread/SpreadNet11/ASP2/webframe.html#require20.html

    Hope it helps. Else please share your exact machine configuration and application architecture, we will look into the same thereon.

    Thanks,

    Reeva

  • Posted 12 October 2018, 11:22 pm EST

    I have .net Framework 4.7.2, my machine have windows 7 professional, and visual studio 2012

    Thanks for your answer

  • Posted 12 October 2018, 11:31 pm EST

    another thing, I have an old version of spread the version is 4.3, and if I drag that control to my form draws version 11, but I can not access the fpchart for example

  • Posted 13 October 2018, 12:20 am EST - Updated 30 September 2022, 2:49 am EST

  • Posted 15 October 2018, 1:41 am EST - Updated 30 September 2022, 2:49 am EST

    It does not work, as an attachment in the following images is selected however I can not choose them from the toolbar. I no longer want to use the previous version but the buttons of the new version are disabled.

  • Posted 17 October 2018, 6:30 pm EST

    Hello,

    You can add fpChart control to the toolbox by undertaking following steps as well:-

    1. Open a VB.Net / C# project and create a new “Web application”.
    2. Right click on the toolbar, and choose Add/Remove Items.
    3. In the .NET Components tab, Spread components should be listed, make sure they are checked.
    4. If a control is not in the list, click browse, and go to bin and find dll file for the control and select it.
    5. This should add it to the list, which you can then select and add to the toolbar.

    Hope it should work for you then.

    Further, your Visual Studio shows controls of V11 because V11 is the latest version and you must have installed it. Once a newer version is installed, it overrides controls of older version. And in case you want to use older version in your application then you must replace the dll’s and licenses.licx file in your application to target the older version.

    Thanks,

    Reeva

  • Posted 17 October 2018, 6:37 pm EST

    Hello,

    There aren’t any reported issues so far. We need to investigate your issue by setting up the same environment as that of yours. We will get back to you with our observations and resolutions.

    Thanks,

    Reeva

  • Posted 19 October 2018, 4:34 am EST

    Thank you very much Reeva, I’ll wait for your response

  • Posted 22 October 2018, 10:10 pm EST

    Hello,

    We set up the same environment as that of yours with Windows 7 Update 1 machine having VS 2012 and .Net framework 4.7.2 and we had GrapeCity Spread tab in toolbox with all spread controls enabled.

    Here are the exact steps we followed:

    1. On a Windows 7 Update 1 machine, we installed .Net framework 4.7.2
    2. Then installed Spread ASP.Net latest version V11.
    3. Created a web appliction using .Net framework 4.7.2.
    4. And then in VS toolbox all the Spread controls including fpChart and fpSpread are enabled and we can drag drop them on the webform too.

    Please confirm the exact steps you followed so that we can investigate this issue further.

    Thanks,

    Reeva

  • Posted 10 November 2018, 2:49 am EST

    I finally succeeded, uninstalled the .net framework version 4.7 and reinstalled version 4.5.2 and it worked

  • Posted 11 November 2018, 3:07 pm EST

    Hello,

    We are glad to know that your issue has been resolved but could you please let us know that the steps that we shared with you had anything missing from our end because we were not able to replicate it with .Net framework 4.7.2 as well.

    Please share some insight so that we can try to figure out exact issue for future reference.

    Thanks,

    Reeva

Need extra support?

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

Learn More

Forum Channels