Caliburn.Micro for Win 8.1 should use the new behavior SDK that is part of VS2013 instead of Windows.UI.Interactivity.
Nigel:
> Also because ActionMessage won’t have AssociatedObject from the SDK we need to populate it. With conventions and Message.Attach this isn’t a problem as we can populate it as part of creating the behaviours. However if the developer is using the full behaviour syntax (usually when they want to use a custom trigger). It also means if they are using any custom triggers and the like then they would need to be rebuilt to support the new SDK.
Nigel:
> Also because ActionMessage won’t have AssociatedObject from the SDK we need to populate it. With conventions and Message.Attach this isn’t a problem as we can populate it as part of creating the behaviours. However if the developer is using the full behaviour syntax (usually when they want to use a custom trigger). It also means if they are using any custom triggers and the like then they would need to be rebuilt to support the new SDK.