DotVVM 4.3.9 bugfix release

• Fixed Button.Enabled when it contains null value
• Fixed bug when returning to SPA with back button (#1955)

Full Changelog: v4.3.8...v4.3.9

DotVVM 4.3.8 security patch

• Fix GHSA-6q65-j4jw-9cg8: path traversal in resources when deployed in Debug mode

Full Changelog: v4.3.7...v4.3.8

DotVVM 4.3.7 bugfix release

• Fixed race condition in markup control @property directive compilation
• DefaultOutputRenderrer.SetCacheHeaders is now protected virtual, allow for cache header customization

Full Changelog: v4.3.6...v4.3.7

DotVVM 5.0.0-preview01 release

Major changes

• Migration to System.Text.Json
• More extensible GridViewDataSet
  • the refactoring should be mostly compatible, if you didn't write your own DataPager and encounter issues, please get in touch with us
  • it is now possible to use GridView and DataPager which load data using staticCommands
  • it is now possible to use token-based paging instead of just page index
  • it is now possible to use custom sorting options which limit what columns can be used for sorting
• DataContext and DataSource properties support resource binding
  • it makes it possible to show server-rendered collections without also sending all of the data in JSON, and without including any knockout data-bind attributes in the HTML

We'll have more polished release notes with the 5.0.0 stable version

List of merged PRs

• Data pager extensibility improvements in #1819
• Refactoring of GridViewDataSet in #1548
• Fix near page indexes crashing on invalid page number in #1847
• Initialized service provider in validation context. in #1869
• Binding translation issue in PostBackHandler properties in #1878
• Fix resource bindings in GridViewColumn.FormatString in #1879
• Fixed ambiguous namespace resolution and matching non-public types in #1877
• Fix ko.observable handling in Linq translations in #1870
• Use System.Text.Json as a backend for view model serialization in #1799
• Fix leaking of original object from ko.observableArray in #1893
• Export the JS StateManager instance in #1894
• Fix excessive allocations in EmbeddedResourceFileLoader in #1888
• Remove the obsolete context.IsPostback setter in #1899
• Enable UseDotvvmSerializationForStaticCommandArguments by default in #1898
• Fix control prefixes in error page "Control Hierarchy" section in #1901
• Bug in JS translator when using Where and using lambda in commands in #1903
• MultiSelect issue with updating observable array fixed in #1910
• Basic support for DataContext={resource: ...} in #1392
• Special-case parsing of <script> and <style> elements, similarly to HTML in #1900
• Bump .NET Core dependency to net8.0 (and net9.0 in aspnetcorelatest) in #1917
• Add option to disable DotVVM serialization for specific types in #1916
• Disallow assigning to init-only properties in bindings in #1909

Full Changelog: v4.3.0...v5.0.0-preview01

DotVVM 4.3.6 bugfix release

• Fixed markup control properties not working properly when an array created in binding (i.e. with LINQ) - #1903
• Fixed MultiSelect when the array content updated without changing length - #1910
• Fixed a cosmetic bug in error page "markup stack trace" - #1901

DotVVM 4.3.5 bugfix release

• Fix leaking of original object from ko.observableArray when using methods like .push, ... (see #1893 for more details)
• Expose dotvvm.rootStateManager API, most importantly making it possible to force immediate refresh knockout observable values (this allows us to fix some bugs in BusinessPack)

DotVVM 4.3.4 bugfix release

• Fixed memory leak in Repeater memoization (#1886).
• Removed accidental Obsolete attribute from RegisterScriptModule method (#1889)

DotVVM 4.3.3 bugfix release

• PostBack Handlers
  • Fix references to _parent (and higher) view models in the postback handler properties
• GridView Columns
  • Fix resource binding in the FormatString property
• Sec-Fetch-Dest validation
  • Include info about issues with site prefetching

DotVVM 4.3.2 bugfix release

• JS Translations
  • Fix knockout observable handling in LastOrDefault, FirstOrDefault and other LINQ translations (#1871)
    • This bug was a regression in 4.3.0
• DotvvmCapabilityProperty
  • Fix assignment of default value in overridden DotvvmProperties (#1863)

DotVVM 4.3.1 bugfix release

• Validation
  • ValidationContext (used in IValidatableObject) has an initialized IServiceProvider (#1869)
• Analyzers
  • DotVVM04 warning is supressed in Linq.Expressions, such as in ValueOrBinding.Select (#1859)
  • DotVVM02 warning works correctly with overriden properties (#1858)
• DotvvmCapabilityProperty
  • NullReferenceException is not thrown when a property of type ValueOrBinding<int>? is set to null in the control (#1864)
  • Fix assignment of default value in overridden DotvvmProperties (#1863)
  • Fix reading of inherited DotvvmProperty (#1862)