Skip to content

Releases: Caliburn-Micro/Caliburn.Micro

V4.0.212

06 Sep 11:59
@vb2ae vb2ae
4.0.222+a53dd1fa1b
a53dd1f
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
V4.0.212 Latest
Latest

Bug fix for Navigation Service with .net 5 and .net 6

Assets 2
Loading

Caliburn.Micro 4.0.210

26 Jun 13:21
@vb2ae vb2ae
4.0.210
31c8005
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
Caliburn.Micro 4.0.210

Caliburn.Micro 4.0.210 Released

Included in this maintance release

*.net 6 support

  • moved min version of .net framework to 4.6.2
  • Check for multiple assemblies being added to the cache @HEskandari
  • IOC performance fixes
  • Removed unnecessary nuget packages

@RudolfJan has also improved the tutorials in the documentation

Contributors

HEskandari and RudolfJan
Assets 2
Loading

Caliburn.Micro 4.0.173

23 Dec 13:10
@vb2ae vb2ae
4.0.173
d7fe18a
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
Caliburn.Micro 4.0.173

Additional Platforms supported
.NET Core 3.1 WPF
.NET 5 WPF
Support for the following platforms has been removed.
Silverlight 5
Windows Phone 8 (Silverlight)
Windows Phone 8 (Windows Runtime)
Windows 8.1
We’ll also be discontinued support for .NET 4.0 for WPF. The minimum version of .NET for WPF is now 4.6.1
All of these platforms are still supported in the 3.x releases.

Changes
Below is the changes included in 4.0.0 release.

Assemblies
The platforms targeted have been changed to support the new .NET ecosystem. These include:

Caliburn.Micro.Core targets .NET Standard 2.0.
Caliburn.Micro.Platform.Xamarin.Forms targets .NET Standard 2.0.
Caliburn.Micro.Platform is consistently named across all platforms (previously UWP included the platform name) except for Xamarin.Forms.
Event Aggregator
The Event Aggregator has some major breaking changes, that bring it into an async implementation approach that is the main reason for 4.0.0.

The full changes are available in the event aggregator migration documentation.

Screens and view model lifecycle
All the interfaces that support view model lifecycle such as IActivate and IGuardClose now support an async implementation.

Assets 2
Loading

Caliburn Micro 4.0.136-rc

21 Jun 11:07
@nigel-sampson nigel-sampson
4.0.136-rc
506cae5
Compare
Choose a tag to compare
Caliburn Micro 4.0.136-rc Pre-release
Pre-release

Changes:

See More
Read more
Assets 4
Loading

Caliburn Micro 4.0.105-alpha

13 Feb 02:26
@nigel-sampson nigel-sampson
4.0.105-alpha
650a67c
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
Caliburn Micro 4.0.105-alpha Pre-release
Pre-release

Changes:

  • 650a67c Update README.md
  • f9e743c Merge pull request #651 from imba-tjd/patch-1
  • 0866162 Chore(readme): use https
  • 8eacda6 Merge pull request #646 from davidhenley/patch-2
  • 30fb2f8 Updated Behaviors for netcoreapp3.0 target
  • dd42b37 Remove Setup and Features builds
  • ebb4c12 Merge pull request #644 from davidhenley/patch-1
  • fbbebe6 Update Microsoft.Xaml.Behaviors.Wpf to target .NET Core
  • d633717 Update Resource.designer.cs
  • 8b0512e Merge pull request #641 from gpetrou/MSBuildSdkExtrasWorkaround
See More
Read more
Assets 4
Loading

Caliburn Micro 4.0.62-alpha

15 Apr 00:45
@nigel-sampson nigel-sampson
4.0.62-alpha
c656c51
Compare
Choose a tag to compare
Caliburn Micro 4.0.62-alpha Pre-release
Pre-release

This alpha marks a major milestone. I believe most of the breaking changes required to support an async first model are now in place.

The versioning number system has change a little, but this makes it easier to have packages available from the CI system.

This affects also every type in Calburn.Micro including but not limited to the following:

  • IWindowManager
  • IEventAggregator
  • IActivate
  • IDeactivate
  • IConductor
  • IGuardClose

These changes were long overdue and help to better support view model life cycles where async operations are happening and especially in IGuardClose where async dialogs are often used.

I understand this represents a large amount of breaking changes, however the nature of these changes tend be quite simple (returning Task.CompletedTask for instance).

The migration docs will be updated soon.

Assets 4
Loading

Caliburn.Micro 4.0.0-alpha.1

24 Jan 08:27
@nigel-sampson nigel-sampson
4.0.0-alpha.1
5924370
Compare
Choose a tag to compare
Caliburn.Micro 4.0.0-alpha.1 Pre-release
Pre-release

This release is earlier that I'd normally I'd like as it's not yet feature complete, however a lot of people are asking for versions that support .NET Standard. Given this I've pushed out this release early, and after a bit of thought I suspect it will be a good thing in the long run.

The major "theme" for 4.0.0 is "async", moving most major interfaces such as IActivate, IDeactivate, IGuardClose etc to async implementations. Naturally this will involve a lot of breaking changes as I move forward. Potentially rolling out early alpha releases at various steps can lessen the blow for people wanting to be on the bleeding edge. The first interface up for changes is IEventAggregator and is included in this release.

I've started documenting the changes and migration path to 4.0.0 which I encourage you all to read.

If you're interested in what's in the pipeline for 4.0.0 you can view the project on GitHub as well as the associated milestone.

If you do upgrade and run into any issues please log them quickly (with a reproduction if possible) and I'll see what I can do.

Assets 2
Loading

Caliburn.Micro 3.2.0

17 Sep 10:17
@nigel-sampson nigel-sampson
3.2.0
544babd
Compare
Choose a tag to compare
Caliburn.Micro 3.2.0

A small house keeping release in part to get ready for Windows Template Studio work.

Included are the following:

  • #443 Remove a rogue dependency on System.Web that was accidentally included.
  • #462 WPF Window Manager won't override a Window's Title if it's been set. Thanks @tziemek.
  • #466 Add a Set implementation to `PropertyChangedBase.
  • #475 Platform provider methods are now virtual.
Assets 2
Loading

Caliburn.Micro 3.1.0

27 May 10:21
@nigel-sampson nigel-sampson
3.1.0
3facfd8
Compare
Choose a tag to compare
Caliburn.Micro 3.1.0

A small feature and bug fix release to clean out some of the backlog before 4.0.0.

Included are the following

  • #439 Fixes up an issue using commas in constant values cm:Message.Attach="ShowTitle('One, Two, Three')"
  • #432 Stop calling InitializeCompontent on Xamarin.Forms, this was mostly used for a underused feature of .xaml files without a code behind. On the non-XF platforms this method has re-entry protection, the XF version did not.
  • #423 Fixes a null reference in the Setup.WPF sample.
  • #417 Handle a ContentPropertyAttribute that doesn't supply a property name (WPF's Frame does this).
  • #364 Support OnViewLoaded in Xamarin.Forms when the view is a ContentPage.
  • #352 Add an extension point BindingScope.GetVisualParent to help people who use visual "bridge" libraries.
  • #319 Add $clickedItem Special Value for WinRT / UWP based projects.
  • #278 Add a navigation service for WPF and Silverlight with a sample. Note this service may change in 4.0.0 with an effort to align all the navigation services.
  • #247 Add an extension point on PropertyChangedBase and BindableCollection<T> named OnUIThread to allow people to customize how property changed notifications are dispatched to the UI thread.
Assets 2
Loading

Caliburn.Micro 3.0.3

09 Jan 09:05
@nigel-sampson nigel-sampson
3.0.3
287203e
Compare
Choose a tag to compare
Caliburn.Micro 3.0.3

This is a very small release that reverts #339.

This release changed behavior so that views were resolved from the container in the same way as view models. The change in behavior caused problems for applications using containers that threw exceptions on failure to resolve a dependency.

This change should have been considered a breaking change and left to 4.0.0 and considered more seriously. For that I apologize.

It's also contains a typo in documentation fix. #402

Assets 2
Loading