In a current project, I was tasked to add a WinForms project from an old application into a new WPF application I was building. No real problem, right? Wrong!
In the legacy project's window was a
listview, set up with column sorting and automatic grouping when the user clicks on the column header. In the old project, sorting and grouping worked beautifully! Attached to the new application, neither sorting nor grouping worked.
What went wrong??
The legacy application generated several reports, most of which were no longer considered useful. The decision was made to create a new application which, among other things would generate new, useful reports. Once completed, the legacy application would be discarded.
You can guess what happened — people complained that some of the old reports WERE useful! Fortunately, they were all located in one VisualStudio project.
I added that project to the new WPF application and added the necessary linkages. Voilà! I could access the reports.
The fly in the ointment – grouping and sorting did not work.
I did an Internet search and found several articles which told me what to do, but they were written for C# programmers. In C3, the "
Main" is accessible and can be easily modified by the programmer. Just add
Main routine. Alas! My employer says we use Visual Basic. The Microsoft article said to add:
Public Shared Sub Main()
but this only resulted in an error message complaining about two
The Microsoft article also said that visual styles must be enabled before any windows of the application are opened. This led me to think about the application initialization sequence in Visual Basic. The "
New" subroutine uses the "
InitializeComponent()" to instantiate the components of the window, including the window itself! Therefore, I added the following
New subroutine to MainWindow.xaml.vb:
Public Sub New()
Sorting and grouping now works as expected!
- 2017-12-08: Original version