Failure initializing designer

Failure initializing designer

Posted by: Hans on 7 August 2018, 3:19 am EST

• 

  Hans

  • Post Options:
  • Link
    Copy
  • Jump To Answer

  Posted 7 August 2018, 3:19 am EST

  We are two programmers at different locations and we often work on the same program at the same time. We usually send the source back and forth via an email attachment.
  
  We have run into a problem with the C1.WIN.C1SIZER.4 control. When receiving the source and attempting to open a form that contains that control we get “Failure initializing designer…” . The problem seems to be because the control was stripped from the form causing references to the control to be undeclared.
  
  Both of us use the same version of Visual Studio and ComponentOne. Would appreciate any information that helps us resolve this problem.

• 

  esha.dhir

  

  • Post Options:
  • Link
    Copy

  Posted 7 August 2018, 6:05 pm EST

  Hello,

  Can you please check if the form is being referred to, from within the project or not? I hope that the source code is placed along with the complete project file before opening the form designer. If this is done, I would like you to check if the assemblies used under the References are being picked up from the installed directory (default location: C:\Program Files (x86)\ComponentOne\WinForms Edition\bin\v4.0) or not. If the assemblies are referred from this bin folder itself, I would like you to share the following so that I can assist you further:

  1. Screenshot of the designer error observed
  2. Build version being used
  3. Screenshot of the references
  4. Licenses.licx file

  Thanks and Regards,
  
  Esha

• 

  Hans

  • Post Options:
  • Link
    Copy

  Posted 8 August 2018, 2:46 am EST

  Thanks for your reply. The form is being referred to and the source code is with the complete project file. The assemblies are referred to in the bin folder. I’ve attached the requested files or snapshots.

  Thanks

• 

  esha.dhir

  

  • Post Options:
  • Link
    Copy

  Posted 8 August 2018, 3:10 pm EST

  Hello,

  Thanks for the information. However, your files are missing from the response. Please try attaching them again after zipping the folder.

  Regards,
  
  Esha

• 

  Hans

  • Post Options:
  • Link
    Copy

  Posted 9 August 2018, 5:34 am EST

  Sorry, not sure why that happened. Here they are in a ZIP fileDesignerr.zip

• 

  esha.dhir

  

  • Post Options:
  • Link
    Copy

  Posted 9 August 2018, 5:15 pm EST

  Hello,

  Thank you for the files. I could not get to some valid conclusion with the screenshots as the error seems to be generic.
  
  However, as you mentioned that the error is specific to C1Sizer as it was stripped from the form once, you can try a way to resolve the issue. Though we don’t recommend this generally, you can try modifying the designer.cs file just for the C1Sizer code. Remove the C1Sizer related code within this file and after that, check if the designer opens fine. If it does, you can now add the C1Sizer control from the Toolbox and set its properties as usual.
  
  On setting multiple properties related to a control and then deleting it from the form, some code related to the control might be left with the form’s code, that causes this issue. Generally, it is suggested to recreate the form designer in this case, if the issue is not resolved on removing the code related to that control from the designer.cs file.

  Best Regards,
  
  Esha

• 

  Hans

  • Post Options:
  • Link
    Copy

  Posted 10 August 2018, 3:31 am EST

  Thanks for your reply. The application has about 5 forms with Sizer on it and they all have the same problem. To remove the control and then add it again and placing all the other controls inside it, would be very onerous and time consuming every time we want to make a change to the program, which is not viable.

  I have tried to change the references from the bin file to the C:\Program Files (x86)\ComponentOne\WinForms Edition\bin\v4.0 directory which solves the problem with the designer, but gives me a License warning when executing. Do you have a solution for that?

• 

  esha.dhir

  

  • Post Options:
  • Link
    Copy

  Posted 12 August 2018, 3:29 pm EST

  Hello,

  A license nag screen is observed in the following two cases:

  1. Your system does not have a valid license key for the controls.
  2. The entries of the licenses.licx file do not match with the controls used in the application.

  If you are using the builds from your licensed version, this screen will be visible because of the second case mentioned above.
  
  First, try a full rebuild (Rebuild All from the Visual Studio Build menu). This will usually rebuild the correct licensing resources.

  The entry for every C1 control used in the application at design time or run time should be present in the licenses.licx file of the project. If you have added controls at runtime, drag and drop the controls on the form to generate their corresponding entries in the licenses.licx file and then you may delete the controls. You can also use the LicxGenerator to generate a licenses.licx file for your application. You can learn more about the same using the below mentioned blog post:
  
  https://www.grapecity.com/en/blogs/licensing-and-licenses-licx-file-licxgenerator-tool/

  Is the solution with which this project is showing this nag screen, consisting of other projects too? If yes, then we would like to inform you that every project that consists of ComponentOne components should contain a licenses.licx file with valid entries for all the C1 controls used in the project.

  If this does not solve your problem, I request you to share the below mentioned details:

  1. The license key you are using on this machine. It can be obtained by:
     
     Running the C1LicenseDeActivation utility and then on the “?” that appears next to the Serial Number. (This can be shared by creating a ticket on https://supportone.componentone.com, to maintain privacy).
  2. The entries in your licenses.licx file
  3. The screenshot of the evaluation message pop up for any control.

  Also, you may refer to the below blog post that would explain you in detail about ComponentOne Licensing:
  
  http://our.componentone.com/2012/01/13/componentone-licensing/

  Best Regards,
  
  Esha

• 

  esha.dhir

  

  • Post Options:
  • Link
    Copy

  Posted 20 August 2018, 8:48 pm EST

  Hello,

  Please note that an application being run on two developer machines should have a same version at both the ends, to avoid code conflict.
  
  New build comes up in every trimester and hence, the versions being different with the two serial keys is normal.
  
  I would suggest you to use the same version of C1 controls at both the ends. The old license can be updated to the latest one being used by one the two machines.
  
  Also, you can both upgrade to the latest version by purchasing the serial key. Please contact the sales team for the same: https://www.grapecity.com/en/contact

  Best Regards,
  
  Esha

• 

  Hans

  • Post Options:
  • Link
    Copy

  Posted 21 August 2018, 2:35 am EST

  So in other words, to resolve this we have to buy two new versions of C1 controls.

  Thanks

• 

  esha.dhir

  

  • Post Options:
  • Link
    Copy

  Posted 21 August 2018, 8:15 pm EST

  Hello,

  The issue has been answered on the corresponding SupportOne ticket.
  
  Please refer the same.

  Best Regards,
  
  Esha