This adds support for use from FSI, as suggested in #21.
I've added another static parameter to the type provider called XamlFileLocation, which can be specified as an alternative to the default XamlResourceLocation. When XamlFileLocation is specified, the XAML is loaded directly from the filesystem rather than from a resource.
An example script is included. The script displays a window twice, in order to demonstrate that closing the first window doesn't prevent the second from being displayed. (Note that if an instance of System.Windows.Application is created by the script, then only the first window will be displayed).
This adds support for use from FSI, as suggested in #21.
I've added another static parameter to the type provider called
XamlFileLocation
, which can be specified as an alternative to the defaultXamlResourceLocation
. WhenXamlFileLocation
is specified, the XAML is loaded directly from the filesystem rather than from a resource.An example script is included. The script displays a window twice, in order to demonstrate that closing the first window doesn't prevent the second from being displayed. (Note that if an instance of
System.Windows.Application
is created by the script, then only the first window will be displayed).