Added Multilingual App Toolkit to prerequisites for building XamlBehaviors.
Fixed some formatting.
Added note about version override for NuGet package creation scripts.
As it currently stands, the InvokeCommandAction.CommandParamenter can
never have a null value as it will make it fallback to the other
approaches, which can raise an InvalidCastException.
A null value should be allowed for the CommandParameter, so instead of
doing a null check, I've replaced it with a property unset check
instead.
This change cleans up the .Design assemblies. Changes include:
- Tweak build configurations so the project now builds successfully for
all configurations.
- Remove unused WinRT references from the design assemblies.
- Removes some dead code.
- Use nameof() instead of string literals when setting extensible
attributes.
For x:Bind to work with EventTriggerbehavior, we need to ensure that no
exception gets raised for not finding the request event on the source
object, as this will might (will) get evaluate at a later phase.
So instead of raising an exception, we just gracefully return from the
method.
Developers can reuse the Windows Runtime event handlers in their custom
controls, but for those cases, the EventTriggerBerhavior shouldn't use
the WindowsRuntimeMarshal class.
This change ensures that not only the EventInfo.EventHandler is checked
for Windows Runtime type, but also that the EventInfo.DeclaringType is
also checked.
This ensures that a custom button extendind the Button Windows Runtime
class will still consider the Click event as a Windows Runtime event,
but a custom MyClick event in it, wouldn't.
It seems the designer projects were not referencing their respective
projects in the solution, but instead a relative folder path. This was
causing the design assemblies to be build prior to the dependent
assemblies causing the build to fail. Hopefully this will fix the
automated build issue :)
the build configuration for the native solution did not include
Microsoft.Xaml.Interactions or Microsoft.Xaml.Interactivity in the
build. This cause the AppVeyor automated build to fail. I modified the
build configuration to see if that would fix the automated build issue.