Multiple references breaking License File and various other annoyances

Multiple references breaking License File and various other annoyances

Posted by: dean.bashore on 24 November 2021, 3:12 pm EST

• 

  dean.bashore

  • Post Options:
  • Link
    Copy
  • Jump To Answer

  Posted 24 November 2021, 3:12 pm EST

  This may be more of a VS2019 Question, but it only seems to be an issue with C1 controls so I am going to ask here. I tried searching but I’m not really sure how to word it.

  Often times when I bring a C1 control into a form it adds a reference to to the 2.0 DLL in addition to the 4.52 DLL that I am working with. This causes a flood of intellisense errors and sometimes results in build errors do the the win2.0 components being registered in the license file. Then when I remove the 2.0 Dll from the project the build fails until I remove the 2.0 registrations from the license file.

  How can Is stop the 2.0 DLL from being references in my project? It also clutters up my toolbox with the duplicate 2.0 controls.

  I’m sure this has a simple solution.

  Thanks in advance for the help.

  Dean

• 

  prabhat.sharma

  

  • Post Options:
  • Link
    Copy

  Posted 29 November 2021, 2:04 am EST

  Hello Dean,

  It is really strange. Can you please repair the installed controls using the ComponentOneControlPanel utility?

  Also, remove the 2.0 references from your project if any, and also delete the content of licenses.licx file and generate the new using the GrapeCity utility from the Tools menu of your VS.

  If you still face the issue then please let us know.

  Regards,
  
  Prabhat Sharma.

• 

  dean.bashore

  • Post Options:
  • Link
    Copy

  Posted 29 November 2021, 5:57 pm EST

  Hi Prabhat.

  Yes, it is still happening.

  Re-reading I realize I wasn’t precisely clear.

  I am doing data driven design and so I am using the datasources tool in VS2019. When I drag either an entire input panel or If I select and individual database column, and drag and drop that onto the form is when it is happening. It will add the 2.0 reference to the project causing resolution ambiguity errors. If it is from a new namespace it will add a line to Licence.licx file which then needs to be deleted. The designer tab usually has to be closed and re-opened after the repairs are affected.

  It’s happening pretty consistently.

  Thanks

  Dean

• 

  prabhat.sharma

  

  • Post Options:
  • Link
    Copy

  Posted 30 November 2021, 4:55 am EST

  Hello Dean,

  The issue is too strange and seems specific to your project.
  
  Do you face the same issue when creating a new project if yes then please let us know the steps so that we too can replicate the same at our end and assist you further and if not then we will be needing your stripped-down sample with the steps to reproduce the issue so that we can assist you further accordingly?

  Regards,
  
  Prabhat Sharma.

• 

  dean.bashore

  • Post Options:
  • Link
    Copy

  Posted 30 November 2021, 10:25 am EST

  Hi Prabhat.

  I will try the new project as soon as I get a chance.

  It just happened again so here are some more details:

  I needed to change a databound control on my form from the default numeric Up Down to a text box. So I went into Datasources and selected the column and used the drop down to change the default type the C1TextBox. I then dragged the new control from datasources onto the form.

  That action caused 3 win 2.0 references to be added to the project causing 549 resolution conflicts. C1.WIN.C1Input.2 C1.Win.2 and I think C1.Win.C1command

  I am using a MARIA/MYSQL database FYI (not that I think that has anything to do with it at this level).

• 

  prabhat.sharma

  

  • Post Options:
  • Link
    Copy

  Posted 1 December 2021, 4:59 am EST

  Hello Dean,

  We will wait for the stripped-down sample as it will help us to narrow down the issue and assist you further.
  
  There is no direct dependency of C1 control on any database tool so it might not depend on the DB tool, you are using. You can uninstall the 2.0 builds from your system and install only the 4.5.2 FW controls that you are using in your project. Please follow the steps given below to do the clean installation of ComponentOne products on your system:

  1: Uninstall the existing products (if any) using System’s ControlPanel/ ComponentOneControlPanel. Make sure that after the uninstallation, there is no folder named “ComponentOne” exists at the location: C:\Program Files (x86)

  2: Download the latest version of ComponentOneControlPanel utility from the given link:
  
  https://www.grapecity.com/componentone/download

  3: Select the edition, version, and framework of the controls that you want to install and hit the “Proceed” button.

  Regards,
  
  Prabhat Sharma.

• 

  dean.bashore

  • Post Options:
  • Link
    Copy

  Posted 1 December 2021, 10:01 am EST

  Hello Prabhat.

  Your advice led me to try an experiment. I removed the 2.0 folders from the C1 directory structure on x86. I drug an entire database table (details configuration) onto a form and nothing bad happened.

  It did, however break my print preview control on another form. I can’t find C1.Win.PrintPreview.4.5.2 in reference manager. I commented out this code for now and got a clean build. It also seems to have tidied up my toolbox which was cluttered with duplicate 2.0 and 4.5.2 versions of the same controls.

  I think this is an issue with VS2019 and I just don’t know how to tell it to ignore certain libraries.

  Unless something else crops up I’m going to consider this resolved.

  Thanks for your help.

  Dean