Click here to Skip to main content
13,863,067 members
Click here to Skip to main content
Add your own
alternative version


Posted 8 Dec 2017
Licenced CPOL

Mixing WinForm ListView with WPF

, 8 Dec 2017
Rate this:
Please Sign up or sign in to vote.
Grouping and sorting in a WinForm listview fails in a WPF application unless Visual Styles are enabled.


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 Visual Studio 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 C#, the "Main" is accessible and can be easily modified by the programmer. Just add:


to the Main routine. Alas! My employer says we use Visual Basic. The Microsoft article said to add:

<System.STAThread()> _
Public Shared Sub Main()

but this only resulted in an error message complaining about two Main routines.


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()

     ' This line runs before Windows objects are instantiated.

     ' This call is required by the designer.

     ' Add any initialization after the InitializeComponent() call.

End Sub  ' New

Sorting and grouping now work as expected!


Date Change
2017-12-07 Original version


This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)


About the Author

Jalapeno Bob
Software Developer (Senior) S & D Acres
United States United States
BSEE 1972, Polytechnic Institute of Brooklyn, Brooklyn, NY
MSCS 1978, Stevens Institute, Hoboken, NJ

Now, I live in Texas with my wife and children and raise non-dairy (aka "meat") goats and chickens for fun and (maybe next year) profit.

I also work off the ranch for a non-profit (ie: .org) writing and maintaining PC software.

You may also be interested in...

Comments and Discussions

-- There are no messages in this forum --
Permalink | Advertise | Privacy | Cookies | Terms of Use | Mobile
Web04 | 2.8.190214.1 | Last Updated 8 Dec 2017
Article Copyright 2017 by Jalapeno Bob
Everything else Copyright © CodeProject, 1999-2019
Layout: fixed | fluid