Component One Upgrade Issues

Component One Upgrade Issues

Posted by: amrose on 28 January 2019, 3:53 pm EST

• 

  amrose

  • Post Options:
  • Link
    Copy
  • Jump To Answer

  Posted 28 January 2019, 3:53 pm EST

  Hello,

  We are having some issues testing out the new version of Component One Winforms. We recently set our developer up with a new computer and are having issues opening up older visual studio projects.

  Attached is a picture of the error they are receiving.

  This new computer’s version of Component One is several versions newer. Attached are pictures of the version numbers for the old computer and the new.

  Any help would be appreciated.

• 

  amrose

  • Post Options:
  • Link
    Copy

  Posted 28 January 2019, 3:54 pm EST - Updated 4 October 2022, 1:35 am EST

  For some reason, the attachments do not appear to be showing. I am attaching them again in this comment.
  
  

  

  855×469 23.5 KB

  

  824×922 69.3 KB

  

• 

  Ruchir.Agarwal

  

  • Post Options:
  • Link
    Copy

  Posted 29 January 2019, 7:50 am EST

  Hello,

  Before we proceed further I would like to inform that since 2014 all the individual components have merged to form ComponentOne Studio. This is why in your new computer, you would be seeing just one entry under WinForms Edition (in C1Live).

  Now, to resolve the issue, here are few things I suggest you to try:

  1. In VS open the References section. Make sure that the Specific Version of C1.Data.2 dll (perhaps all the ComponentOne assemblies) is set to false.
  2. Open the license.licx file in your project and remove all version specific information. That is remove the Version, Culture and PublicKeyToken from every entry in licenses.licx files. Also, you may even delete this file and make the GrapeCity License manager tool generate it VS->Tools->GrapeCity License manager->Update Project-Check all checkboxes]. You may find more information about this utility here: https://www.grapecity.com/en/blogs/how-to-use-the-grapecity-license-manager-add-in
  3. Close the VS project, delete the bin and obj folders. Relaunch the application.
  4. Refer https://www.grapecity.com/en/blogs/a-step-ahead-troubleshooting-common-errors-part-i/ article’s 'Failed to Create Component’ Design Time Exception topic.
     
     Hopefully this should resolve your issue.

  Regards,

• 

  amrose

  • Post Options:
  • Link
    Copy

  Posted 29 January 2019, 3:42 pm EST - Updated 4 October 2022, 1:35 am EST

  Thank you for your assistance. Your steps have gotten us further. We are able to open the project now.

  Now we are running into an error when trying to edit the DataSetDef in a C1DataSet we receive the following error:

  “Object reference not set to an instance of an object”

  

  778×394 17.4 KB

  Any help is appreciated.

• 

  Ruchir.Agarwal

  

  • Post Options:
  • Link
    Copy

  Posted 30 January 2019, 8:38 am EST

  Hello,

  Just to confirm, are you trying to use C1DataObjects with 2018v3 version of ComponentOne?
  
  If that is so, I would suggest you to instead use Entity Framework.
  
  You can find more detailed information here:
  
  https://www.grapecity.com/en/forums/winforms-edition/c1dataobjects-end-of-life-_1
  
  Here is the documentation link for Entity Framework: https://help.grapecity.com/componentone/NetHelp/EFDataSource/webframe.html#ComponentOne_Entity_Framework_DataSource_Overview.html

  Regards,
  
  Ruchir

• 

  amrose

  • Post Options:
  • Link
    Copy

  Posted 30 January 2019, 9:36 am EST

  We are using C1DataObjects. I will look into the Entity Framework.

  Is there a conversion tool for old projects our will this have to be done manually?

  Thank you.

• 

  Ruchir.Agarwal

  

  • Post Options:
  • Link
    Copy

  Posted 31 January 2019, 4:13 am EST

  I am sorry to say but there is no conversion utility for it. This would have to be done manually.

  Thank You,