In the .net7 CollectionViewSource has a different behaviour than in the .net6
See original GitHub issueBasically, in .net7 when you run the attached project and press the button, it will display a list of items. If you run the unit test it will throw an exception on this line
EntityCollectionView = new CollectionViewSource { Source = Entities }.View;
Because the View is null.
If you change the TargetFramework to net6 the test passes because View contains an instance.
Is this a bug?
Regards Daniel Kaczmarek
Issue Analytics
- State:
- Created 10 months ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
.NET 7 Performance Improvements in .NET MAUI - .NET Blog
NET 7, .NET MAUI applications should see an improvement to startup time as well as smoothing scrolling, navigation, and general UI performance.
Read more >Strange behavior of CollectionViewSource code-behind ...
In my program i have custom class for async loading data at startup in Worklist.Result (observablecollection). At this moment i need use custom ......
Read more >WinForms UI Controls - .NET 7 Support, Visual Studio, C#
NET 6 / .NET 7 Support includes 190+ UI Controls and Libraries, including Data Grid, Data Visualization and Reporting, and many more.
Read more >CollectionViewSource updates and SelectedItem looses ...
I am using a radGridView in Master/Detail scenario using MVVM; the selected item is displayed in a custom form that allows editing.
Read more >.NET
This article explains how to enable users to download multiple files as a single zip archive from a .NET Core Web API. It...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Appears to be related or a duplicate of https://github.com/dotnet/wpf/issues/7205
Callstack:
I believe the fix is already in the release/7.0 branch but it was not included in a public release yet. It should be included in the upcoming .Net 7.0.3.