Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade to 8.0.2 throws System.ReferenceNullException for Bind #4348

Open
1 of 7 tasks
naveenbuziness opened this issue Dec 18, 2021 · 2 comments
Open
1 of 7 tasks

Upgrade to 8.0.2 throws System.ReferenceNullException for Bind #4348

naveenbuziness opened this issue Dec 18, 2021 · 2 comments

Comments

@naveenbuziness
Copy link

naveenbuziness commented Dec 18, 2021

馃敊 Regression

Upgrade to 8.0.2 throws System.ReferenceNullException on use of CreateBindingSet and call bind
Note:- We have migrated from .Net5 to .Net6

Old (and correct) behavior

App starts up normally

Current behavior

Throws System.ReferenceNullException "Object reference not set to an instance of object" for setting bind after CreatBindingSet()

Reproduction steps

Create binding set and call bind.
Exception

Stack Trace
at MvvmCross.Binding.BindingContext.MvxBaseFluentBindingDescription1.TargetPropertyName(Expression1 targetPropertyPath)
at MvvmCross.Binding.BindingContext.MvxFluentBindingDescription2.For(Expression1 targetPropertyPath)
at DNA.Scheduler.WinUI.Gantt.GanttView..ctor() in D:\Naveen\Source\Repos\DNA.Central\DNA.Scheduler\DNA.Scheduler.WinUI\Gantt\GanttView.xaml.cs:line 31

Configuration

Version: 6.x

Platform:

  • 馃摫 iOS
  • 馃 Android
  • 馃弫 WPF
  • 馃寧 UWP
  • 馃崕 MacOS
  • 馃摵 tvOS
  • 馃悞 Xamarin.Forms
@Cheesebaron
Copy link
Member

I wouldn't call this a regression, just unsupported platform for now.

We do have a WinUI PR open, which might solve your issue. We also have another PR with .NET 6 support, which I need to finish up.

So won't do anything about this binding error you get until those get in. You could instead just use regular XAML bindings or whatever WPF/WinUI provides.

@revred
Copy link

revred commented Dec 20, 2021

This is also the issue that I have run into. Is there a timeframe to merge this into the main trunk or is there a way forward for the interim?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

3 participants