c1SplitContainer

c1SplitContainer

Posted by: philippe.berhin on 2 March 2024, 1:39 am EST

• 

  philippe.berhin

  • Post Options:
  • Link
    Copy

  Posted 2 March 2024, 1:39 am EST

  Hi

  I plan to port one of my application from .Net Framework 4.8 to .Net Core .
  
  But I see that the c1SplitContainer is not supported for .Net Core and I used this one a lot.
  
  Any plan to make this control available for .Net Core in the near future ?

  Thanks

• 

  kartik.dua

  

  • Post Options:
  • Link
    Copy

  Posted 3 March 2024, 3:33 pm EST

  Hi Philippe,

  Apologies for the delay in response.

  The C1SplitContainer control is already ported to .NET6 and the latest 2023v3 release also introduced a .NET8 compatible version of C1 controls. Below is the NuGet link for the latest version of SplitContainer that is compatible with .NET6+. You can port your application to .NET6+ and we are always here to assist if you face any issues.

  https://www.nuget.org/packages/C1.Win.SplitContainer/8.0.20233.636

  Best Regards,
  
  Kartik

• 

  philippe.berhin

  • Post Options:
  • Link
    Copy

  Posted 5 March 2024, 11:56 pm EST

  Thanks Kartik

  I started the conversion of a large app (.Net 4.8)
  
  I currently change the references directly in the designer.cs, then it the .cs file.
  
  Once done, I can open the form ni the designer
  
  What I noticed that sometimes the designer get frozen and I have to close VS and restart

  I also noticed that If I open the original project (.Net 4.8), the designer doesn’t open and get the following message for all form

  *" The designer could not be shown for this file because none of the classes within it can be designed. The designer inspected the following classes in the file: ShowFilter — The base class ‘System.Void’ cannot be designed."

  Any way to avoid this ?

• 

  kartik.dua

  

  • Post Options:
  • Link
    Copy

  Posted 6 March 2024, 3:02 pm EST

  Hi Philippe,

  1. An issue with the C1SplitContainer designer (v6.0) was reported earlier when using the nested C1SplitContainers. This issue was fixed in the latest 2023v3(636) hotfix release. Therefore, please make sure you are using the latest version.

  If the issue persists, we request you provide a sample project containing a stripped-down Form from your application that shows the issue. It will help us investigate the issue further and assist you in the best way possible.

  Note: Since this is a public forum, if you are hesitant to share your confidential application info here (like application’s forms), then please create a new support ticket on our private support portal and continue this thread there. You can go to the “My Support” section in your Mescius for the same.

  2. The other error you mentioned is new and we have never had any such reports before. It also does not seem to be related to C1 controls. We did a general search and found a StackOverflow thread that might be useful - https://stackoverflow.com/questions/6683255/the-designer-could-not-be-shown-for-this-file-because-none-of-the-classes-within

  Thanks, and Best Regards,
  
  Kartik

• 

  philippe.berhin

  • Post Options:
  • Link
    Copy

  Posted 7 March 2024, 6:56 pm EST

  HI Kartik

  I use the latest build (336)
  
  Apparently, the lock up only appear after conversion. If I restart VS, it seems to be working as expected.

  But I will not be able to convert everything, apparently, the FlexGrid.SearchPanel is not yet available.
  
  Any expected date for the availability?

  thanks

  Philippe

• 

  kartik.dua

  

  • Post Options:
  • Link
    Copy

  Posted 7 March 2024, 7:18 pm EST

  Hi Philippe,

  We are glad to hear that the issue with C1SplitContainer is resolved on your end.

  ---

  Regarding the C1FlexGridSearchPanel, it is not yet available in .NET 6+ versions of C1 WinForms controls. However, since the SearchPanel uses the ApplySearch method of the C1FlexGrid, you can implement the SearchPanel as a UserControl and use it with the C1FlexGrid.

  Please see the attached sample project in which we have implemented the SearchPanel with a similar object model as before. You can also customize it as per your requirements.

  Attachment: CustomSearchPanelDemo.zip

  Best Regards,
  
  Kartik