Trouble adding C1FlexViewer

Trouble adding C1FlexViewer

Posted by: connellyj on 15 January 2018, 3:00 am EST

• 

  connellyj

  • Post Options:
  • Link
    Copy
  • Jump To Answer

  Posted 15 January 2018, 3:00 am EST

  Now… My solution is 11 VB.net projects using .net 4.5 and x86 . The reporting is all done in one of the projects. I am trying to migrate from C1Report to C1FlexReport. I have added all the references listed in the documentation and I have deleted references to C1Reports. My toolbox does include C1FlexReport, C1FlexViewer, C1FlexViewerPane, and C1FlexViewerDialog. I can add the C1FlexReport but none of the others will drop on my form.

  These are my C1 references:

  Did I miss something? is there a step to the process that I missed?
  
  Thanks!

• 

  connellyj

  • Post Options:
  • Link
    Copy

  Posted 15 January 2018, 6:26 am EST

  I have upgraded to the latest version but still cannot drop the C1FlexViewer, C1FlexViewerPane, or C1FlexViewerDialog. I have upgraded my reports and code. I currently have no compile errors.

• 

  esha.dhir

  

  • Post Options:
  • Link
    Copy

  Posted 15 January 2018, 7:20 pm EST

  Hello,

  Thank you for sharing the screenshots. Could you please tell me what exactly happens when you try to drag-drop the C1FlexViewer? A small video showing the same would be helpful.

  Also, in the references with respect to the latest update, some dlls(C1.C1Report.CustomFields.4 and C1.Win.4) are picked from the “ASP.NET Web Forms Edition” folder. This hapens because the Winforms dlls in the “ASP.NET Web Forms Edition” folder and the “WinForms Edition” folder are different and because of the way VS searches for dlls in the registry. Kindly upgrade ASP.NET WebForms on your system to match the version of Winforms installed on your machine.
  
  I would ask you to keep a note of these dlls, manually delete them and then add all of them again from the “WinForms Edition” directory. Then, try dragging and dropping the control on the form again.

  Best Regards,
  
  Esha

• 

  connellyj

  • Post Options:
  • Link
    Copy

  Posted 16 January 2018, 12:45 am EST

  I updated the references:
  
  
  
  It still does nothing. no messages to the output window or error list. See picture sequence:
  
  

• 

  connellyj

  • Post Options:
  • Link
    Copy

  Posted 16 January 2018, 1:55 am EST

  I dowloaded the latest FlexReportViewer sample project. In design mode I can open the form and look at the properties of the C1FlexViewer.

  When I try to run it I get
  
  “The type initializer for ‘C1.Win.FlexViewer.C1FlexViewerPane’ threw an exception.”

  The inner exception is:
  
  “Could not load file or assembly ‘C1.C1Pdf.4, Version=4.0.20173.286, Culture=neutral, PublicKeyToken=79882d576c6336da’ or one of its dependencies. The located assembly’s manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)”:“C1.C1Pdf.4, Version=4.0.20173.286, Culture=neutral, PublicKeyToken=79882d576c6336da”

• 

  esha.dhir

  

  • Post Options:
  • Link
    Copy

  Posted 16 January 2018, 4:49 pm EST

  Hi,

  We have never come across this issue. However, you may want to try the below mentioned ways to get rid of the issue of missing FlexViewer while dragging and dropping:

  1. Close and reopen the Visual Studio.
  2. Do you face the same issue on different machines? Please try doing the same.
  3. Reset the toolbox (Right click in the Toolbox and select “Reset Toolbox”).
  4. Create a fresh sample and check whether you face the issue with that as well.
  5. Check the dropdown of the property grid as to whether it shows the C1FlexViewer control added in the list.
     
     Please share the observations with us. Also, which .NET Framework is used in your application?

  You face the mentioned exception while trying to run FlexReportViewer sample because of a version conflict among the dlls. Please ensure that all the dlls being used in the sample
  
  References belong to a same version. If this is not the case, manually add all the dlls from a common folder, say bin directory of 4.0.20173.287 version. Next, rebuild the application.
  
  Let us know if you now observe the exception while running the sample.

  Best Regards,
  
  Esha

• 

  connellyj

  • Post Options:
  • Link
    Copy

  Posted 17 January 2018, 12:08 am EST

  Resetting to ToolBox did it! Thanks!