Skip to content

Releases

Release-4.0.0-for-WPF

Choose a tag to compare

@nuitsjp nuitsjp released this 11 Jul 06:41

KAMISHIBAI 4.0.0 for WPF

KAMISHIBAI 4.0.0 removes the mandatory Windows API Code Pack dependency and makes the file dialog implementation replaceable. This is a major release because the dependency injection graph and the default runtime implementation have changed.

Important compatibility information

Review these points before upgrading from KAMISHIBAI 3.x.

Existing file dialog interfaces remain unchanged

The following public interfaces and contexts retain their existing members:

  • IPresentationService
  • IPresentationServiceBase
  • IWindowService
  • OpenFileDialogContext
  • SaveFileDialogContext

Existing calls such as presentationService.OpenFile(context) and presentationService.SaveFile(context) do not need to be rewritten.

Dependency injection contains a breaking change

WindowService now requires an IFileDialogService. KamishibaiApplicationBuilder.Build() registers the default implementation automatically, but applications that instantiate WindowService directly or assemble the service graph themselves must register and supply IFileDialogService.

The default runtime implementation has changed

KAMISHIBAI 3.x used Microsoft-WindowsAPICodePack-Shell. KAMISHIBAI 4.0 uses the public Windows Common Item Dialog COM API directly. The standard open, multiple-selection, folder-selection, save, cancel, filter, custom-place, and extension behaviors are covered by integration tests, but applications can observe differences in native validation, exception details, or operating-system-dependent presentation.

Known limitations of the new default implementation:

  • AllowPropertyEditing has no corresponding public Common Item Dialog switch and is not applied.
  • IsExpandedMode maps to FOS_DEFAULTNOMINIMODE, which Windows 7 and later do not support.

The Code Pack is no longer transitively referenced by Kamishibai.View

Applications that used Code Pack APIs through KAMISHIBAI's transitive dependency must add an explicit dependency. Applications that require the exact KAMISHIBAI 3.1.0 dialog implementation should use the compatibility package.

Preserving the KAMISHIBAI 3.1.0 implementation

Install the new package:

dotnet add package Kamishibai.FileDialogs.WindowsApiCodePack --version 4.0.0

Register it before Build():

builder.Services.AddWindowsApiCodePackFileDialogs();
var app = builder.Build();

Installing the package alone does not activate it. The registration call is required.

The compatibility package:

  • contains the same OpenFile and SaveFile method bodies as KAMISHIBAI 3.1.0;
  • preserves the existing result and context-update behavior, including existing quirks;
  • pins Microsoft-WindowsAPICodePack-Shell to exactly version 1.1.4;
  • restores Code Pack as a transitive dependency.

The compatibility package therefore carries the Code Pack dependency and its Microsoft license terms. Applications that cannot accept that dependency should use the new default implementation or provide their own IFileDialogService.

See the complete 3.x to 4.0 migration guide.

Packages

  • Kamishibai 4.0.0
  • Kamishibai.View 4.0.0
  • Kamishibai.Hosting 4.0.0
  • Kamishibai.FileDialogs.WindowsApiCodePack 4.0.0

Validation

  • View and dependency-injection tests: 21 passed
  • Source-generator tests: 23 passed
  • Native Open/Save dialog integration tests: 5 passed
  • net462 and net6.0-windows builds passed for all release packages
  • Compatibility OpenFile and SaveFile method bodies matched KAMISHIBAI 3.1.0 exactly after line-ending normalization

Related issue

Full Changelog: Release-3.1.0...Release-4.0.0

Release-3.1.0-for-WPF

Choose a tag to compare

@nuitsjp nuitsjp released this 11 Feb 21:26
da6e076

What's Changed

  • Add IWindow.ViewModel property by @freesia in #32
  • Change auto-generated PresentationService to a subclass by @freesia in #31

Full Changelog: Release-3.0.1-for-WPF...Release-3.1.0

Release-3.0.1-for-WPF

Choose a tag to compare

@nuitsjp nuitsjp released this 20 Sep 21:25

What's Changed

  • Fixed an error that occurs when Windows is closed while NavigationFra… by @nuitsjp in #26

Full Changelog: Release-3.0.0-for-WPF...Release-3.0.1-for-WPF

Release-3.0.0-for-WPF

Choose a tag to compare

@nuitsjp nuitsjp released this 06 Jun 21:00

Changes

  • Change in order of navigation event firing

Until now, event notifications have been processed in the order of asynchronous -> synchronous.
However, there was a problem with asynchronous notifications being invoked in the reverse order of screen transitions when screen transitions occurred within an event.
This was because screen transitions were possible only when asynchronous notifications were available, and as a result, asynchronous notifications were called when returning from the method call tree.
Therefore, the notification order was changed from synchronous to asynchronous.

See the changes in the documentation below for details.

Full Changelog: Release-2.6.0-for-WPF...Release-3.0.0-for-WPF

Release-2.6.0-for-WPF

Choose a tag to compare

@nuitsjp nuitsjp released this 23 Feb 23:46
  • Update Wpf.Extensions.Hosting to 1.2.0

Full Changelog: Release-2.5.0...Release-2.6.0-for-WPF

Release 2.5.0 for WPF

Choose a tag to compare

@nuitsjp nuitsjp released this 18 Jan 02:31
8e5bb49

#24 Supported primary constructor.

Release 2.4.0 for WPF

Choose a tag to compare

@nuitsjp nuitsjp released this 18 Nov 23:25

Add IWindow operations.

Release 2.3.0 for WPF

Choose a tag to compare

@nuitsjp nuitsjp released this 18 Nov 22:00
  • Add IsClosed property to IWindowHandle

Release 2.2.0 for WPF

Choose a tag to compare

@nuitsjp nuitsjp released this 18 Nov 21:35

Added the ability to close an open Window from the side that opened it.

Release 2.1.0 for WPF

Choose a tag to compare

@nuitsjp nuitsjp released this 29 Oct 10:54

Added functionality to call Dispose on the current ViewModel of the NavigationFrame when the window is closed.