AR20 Designed - Properties not setting Focus to most recently selected

AR20 Designed - Properties not setting Focus to most recently selected

Posted by: rick.papke on 22 May 2026, 1:41 pm EST

• 

  rick.papke

  • Post Options:
  • Link
    Copy

  Posted 22 May 2026, 1:41 pm EST

  I recently upgraded my project to AR20 Code Based sectionReport and I am having a problem where the properties panel will not update and reflect the newest object selected. eg. I have a line selected and then select a textbox, but the properties tab still shows the line. I have to click off the designer and back in order for it to update properly.

  Is this a known bug or is there something I can do to resolve.
  
  Thanks, Rick

• 

  akshay.rajput

  

  • Post Options:
  • Link
    Copy

  Posted 25 May 2026, 3:00 am EST

  Hi Rick,

  Thank you for reaching out to MESCIUS support.
  
  The behavior you are observing is uncommon and is not expected behavior in ActiveReports.NET 20. To help us investigate this further, could you please provide the following details:

  • Exact ActiveReports.NET 20 version/build number
  • Visual Studio version and edition
  • From which version of AR it was upgraded to AR v20
  • Whether the issue occurs with all reports or only a specific report
  • Whether the issue occurs with newly created projects or only with the upgraded ones
  • Visual Studio version
  • Please also share a screen recording of you replicating the issue so we can have a better understanding on how we can reproduce it at our end.
    
    In the meantime, we recommend you to try the following steps:

  1. Close Visual Studio and delete the .vs, bin, and obj folders from the solution.

  2. Reopen the solution and rebuild the project.

  3. Reset the Visual Studio window layout using: Window > Reset Window Layout

  4. Test the behavior with a newly created SectionReport project.

  5. Since you recently upgraded, Visual Studio might still be holding onto cached designer components from the previous version. Please clear the Visual Studio Component Cache by following the steps discussed in the attached Microsoft thread.

  6. Perform a “Clean Solution” and manually delete the bin and obj folders to ensure no legacy DLLs are interfering with the designer’s event propagation.

  Please let us know the results after trying these steps, and we will continue investigating further.

  Best regards,

  Akshay