Antony Male 3c7639bdc8 Turns out it is possible to have a single csproj targetting both core and framework ... <EnableDefaultItems>false</EnableDefaultItems> along with <Compile Include="**\*.cs" Exclude="obj\**" /> and <None Remove="**\*.cs" /> is needed, though.		2019-09-22 17:12:54 +01:00
..
Properties	Split Stylet and IntegrationTests projects into Framework and Core	2019-09-22 17:12:53 +01:00
ShowDialogAndDialogResult	Rename TryClose to RequestClose, and put in IRequestClose	2015-01-14 20:25:01 +00:00
WindowLifecycle	Use MessageBox in the integration tests and samples	2014-05-21 11:32:51 +01:00
App.config	Start on the integration test suite	2014-04-04 13:04:53 +01:00
App.xaml	Fix the integration tests	2014-08-02 17:50:18 +01:00
Bootstrapper.cs	Freeze BitmapSources before returning them	2015-10-08 14:43:09 +01:00
ShellView.xaml	Revert the BindingProxy stuff	2015-10-06 11:54:33 +01:00
ShellViewModel.cs	Implement another mechanism of backup ActionTarget, using IRootObjectProvider	2015-10-06 12:57:08 +01:00
StyletIntegrationTests.csproj	Turns out it is possible to have a single csproj targetting both core and framework	2019-09-22 17:12:54 +01:00