You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
this is just a heads up as been chasing an issue with downstream dll's failing to build against rx ui 17.1.50
CSC : error CS1705: Assembly 'ReactiveUI.Wpf' with identity 'ReactiveUI.Wpf, Version=17.1.0.0, Culture=neutral, PublicKeyToken=null' uses 'PresentationFramework, Version=6.0.2.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' which has a higher version than referenced assembly 'PresentationFramework' with identity 'PresentationFramework, Version=6.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'
i've resolved my issue by updating visual studio, but just in case anyone else turns around and states it's not building for wpf\winforms on older versions of visual studio 2022. it does mean there is a ripple effect on downstream projects until the core issue is resolved.
dpvreony
changed the title
[BUG] dev experience - rxui currently tied to net6.0.2+
[BUG] dev experience - rxui for windows desktop currently tied to net6.0.2+
Feb 21, 2022
this is just a heads up as been chasing an issue with downstream dll's failing to build against rx ui 17.1.50
CSC : error CS1705: Assembly 'ReactiveUI.Wpf' with identity 'ReactiveUI.Wpf, Version=17.1.0.0, Culture=neutral, PublicKeyToken=null' uses 'PresentationFramework, Version=6.0.2.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' which has a higher version than referenced assembly 'PresentationFramework' with identity 'PresentationFramework, Version=6.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'
dotnet/core#7176
i've resolved my issue by updating visual studio, but just in case anyone else turns around and states it's not building for wpf\winforms on older versions of visual studio 2022. it does mean there is a ripple effect on downstream projects until the core issue is resolved.
there is a workaround of
happy to do the PR if wanted
The text was updated successfully, but these errors were encountered: