'C1.C1Preview 2.0 to 4.5.2 unresolved references

'C1.C1Preview 2.0 to 4.5.2 unresolved references

Posted by: dean.bashore on 23 December 2021, 11:16 am EST

• 

  dean.bashore

  • Post Options:
  • Link
    Copy
  • Jump To Answer

  Posted 23 December 2021, 11:16 am EST

  I am trying to re-factor some VB code built on C1 2.0 Assemblies. I have had great luck except wi9th some issues around C1.C1Preview.C1PrintDocument and Render table. Below is the error for C1PrintDocument.

  Severity Code Description Project File Line Suppression State
  
  Error BC30002 Type ‘C1.C1Preview.C1PrintDocument’ is not defined. Vnet CircuitPro C:\Users\dbashore\Documents\2021-12-20 Vnet CircuitProSource\Vnet CircuitPro\Vnet CircuitPro\frmInvoicing.Designer.vb 1289 Active

  Also this one for Render
  
  Severity Code Description Project File Line Suppression State
  
  Error BC30002 Type ‘C1.C1Preview.RenderTable’ is not defined. Vnet CircuitPro C:\Users\dbashore\Documents\2021-12-20 Vnet CircuitProSource\Vnet CircuitPro\Vnet CircuitPro\frmInvoicing.vb 4786 Active

  Can someone point me in the right direction to resolving these?

  Thanks

  Dean

• 

  dean.bashore

  • Post Options:
  • Link
    Copy

  Posted 23 December 2021, 2:07 pm EST - Updated 3 October 2022, 10:46 pm EST

  Just got this Playing with your “Sticky Notes” sample. More than possibly related

  

  1904×1008 58.1 KB

• 

  avnish.kumar

  

  • Post Options:
  • Link
    Copy

  Posted 24 December 2021, 12:23 am EST

  Hi Dean,

  This error usually occurs when there is an issue with the references in your project. Could you please try removing and then adding C1 related references? Please make sure that you are using the C1 Dlls of the same version.

  Starting from the 21v2 release C1PrintDocument has been separated from C1Report and reintroduced in C1.PrintDocument.4.5.2 DLL, if you are not using C1Report in your project then we suggest you refer to the new C1.PrintDocument.4.5.2. If you are using C1PrintDocument with C1Report then you should use the C1Report Dlls to avoid issues. Although, Please note C1Report is a legacy control.

  If you still face the issue, then please share a sample replicating the issue and screenshots of references of your project.

  Regards
  
  Avnish

• 

  dean.bashore

  • Post Options:
  • Link
    Copy

  Posted 26 December 2021, 2:12 pm EST - Updated 3 October 2022, 10:46 pm EST

  Hi Avnish

  I think I understand what you are saying. Below is a snapshot from my Object Browser pane. I also re-searched my entire C: Drive (see results window below). Also included the references in solution explorer from WinformsApp6 sample project as requested.

  The problem is not that the reference isn’t included. It’s that I can’t find it to add it.

  

  296×736 9.73 KB

  

  333×679 13.6 KB

  

• 

  avnish.kumar

  

  • Post Options:
  • Link
    Copy

  Posted 27 December 2021, 11:18 pm EST

  Hi,

  As we can see in the images you attached, you have not referenced the C1.C1Report.4.5.2 assembly. Please include a reference to C1.C1Report.4.5.2 DLL and let us know if the issue persists.

  Regards
  
  Avnish

• 

  dean.bashore

  • Post Options:
  • Link
    Copy

  Posted 28 December 2021, 5:19 pm EST

  Hello Avnish.

  I understand your first response now and yes adding C1.C1Report corrected those resolution errors.

  However, I think my misunderstanding come from your advice about “if you are not using C1Report in your project then we suggest you refer to the new C1.PrintDocument.4.5.2.” I would like to do this. I’m eliminating TrueDB grid and Converting to FlexGrid since True DBGrid is not going to be moving forward.

  I would prefer to eliminate “legacy controls” now but I cannot do that since as my screenshots above show the “New” DLL/Assembly which you recommend does not exist in my installation. Where can I get the “New” assembly?

• 

  avnish.kumar

  

  • Post Options:
  • Link
    Copy

  Posted 29 December 2021, 12:30 am EST - Updated 3 October 2022, 10:46 pm EST

  Hi,

  The new C1.PrintDocument assembly was introduced from the 21v2 release. Please make sure you have 21v2 or later release installed. If you have it installed then you should be able to add a reference to the C1.PrintDocument.
  
  If you have not used the C1Reports to create any reports and are just using C1PrintDocument to generate documents then there should not be many changes needed to migrate to the new assembly.
  
  If you face any issues, just let us know.

  Regards
  
  Avnish

  

  1296×483 31.7 KB

• 

  dean.bashore

  • Post Options:
  • Link
    Copy

  Posted 30 December 2021, 12:28 pm EST

  Hi Avnish.

  I think that is my issue. I’m finding it difficult to tell what release is installed but all the Change log files I looked start with 21v1 so I guess I’m back version.

  How do I update and more importantly keep my version current? I’m not getting any notifications or anything and I don’t see sort of update functionality anywhere. Can you point me in the right direction or link me documentation?

  In the meantime I’ll keep looking.

  Thanks for all the help

  Dean

  Update: I have the 2021 V3 update installed now.

• 

  avnish.kumar

  

  • Post Options:
  • Link
    Copy

  Posted 31 December 2021, 2:20 am EST

  Hi,

  • "

  • "You can use the ComponentOneControlPanel utility to update, install, repair your ComponentOne installation. You can download the C1ControlPanel from https://www.grapecity.com/componentone/download.
    
    You can also refer to the blog at https://www.grapecity.com/blogs/welcome-to-componentone-controlpanel for more information on C1ControlPanel.
    
    "

  • "Opening the C1ControlPanel will show you the available updates(if any) for the ComponentOne Edition you have installed.
    
    To get notified about the new releases through email, please make sure that you have checked the Product Release Emails option in the My Account > Update Email Preferences section of your Grapecity account.
    
    You can also refer to our blogs section at https://www.grapecity.com/blogs as a release blog is published after every major release.
    
    "

  • “Please note updating your installed C1 control does not ensure that references in your project will also automatically update. If you have not customized your references and have set the Specific version property for the C1 assembly references to false, the Visual studio should automatically pick the latest version of assemblies installed in your system. Otherwise, you will have to update the references in your projects.”

  "

  If you need any other help, just let us know.
  
  Regards
  
  Avnish