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
When I create a method in my ViewModel class - class that inherits from DotvvmViewModelBase, I give it an AllowStaticCommand attribute and call it from View with staticCommand binding, then the dependecies in a constructor are not resolved, they are null instead. When the same method and dependencies are moved to separate class and I register it to the serviceCollection, the dependencies are resolved as expected.
DotVVM version 4.1.0
net7.0
The text was updated successfully, but these errors were encountered:
This is a known problem (#809), we finally have an option to disable the bug: DotvvmConfiguration.ExperimentalFeatures.UseDotvvmSerializationForStaticCommandArguments.Enable()
When I create a method in my ViewModel class - class that inherits from
DotvvmViewModelBase
, I give it anAllowStaticCommand
attribute and call it from View withstaticCommand
binding, then the dependecies in a constructor are not resolved, they arenull
instead. When the same method and dependencies are moved to separate class and I register it to theserviceCollection
, the dependencies are resolved as expected.DotVVM version 4.1.0
net7.0
The text was updated successfully, but these errors were encountered: