2019-08-13 15:23:28 +02:00
<?xml version="1.0" encoding="utf-8"?>
<Package xmlns:rescap= "http://schemas.microsoft.com/appx/manifest/foundation/windows10/restrictedcapabilities" xmlns= "http://schemas.microsoft.com/appx/manifest/foundation/windows10" xmlns:uap= "http://schemas.microsoft.com/appx/manifest/uap/windows10" IgnorableNamespaces= "uap" >
<!-- This file is used as the Appxmanifest for tests that _need_ to run in a
packaged environment. It will be copied to the test's OutDir as part of the
2019-12-03 20:29:48 +01:00
PostBuid step. It's highly similar to the "SUA" manifest that
2019-08-13 15:23:28 +02:00
TAEF ships with, with the following modifications:
1. All of our winrt types are included in this manifest, including types from
2019-12-03 20:29:48 +01:00
MUX.dll. This is done in a custom build step that automatically adds each
of our types to this manifest.
2019-08-13 15:23:28 +02:00
2. We also _NEED_ the two vclibs listed under the `PackageDependency` block.
2019-12-03 20:29:48 +01:00
-->
2019-08-13 15:23:28 +02:00
<Identity Name= "TerminalApp.LocalTests.Package"
ProcessorArchitecture="neutral"
Publisher="CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US"
Version="1.0.0.0"
ResourceId="en-us" />
2019-12-03 20:29:48 +01:00
2019-08-13 15:23:28 +02:00
<Properties >
<DisplayName > TerminalApp.LocalTests.Package Host Process</DisplayName>
<PublisherDisplayName > Microsoft Corp.</PublisherDisplayName>
<Logo > taef.png</Logo>
2019-12-03 20:29:48 +01:00
<Description > TAEF Packaged UWP Application Host Process</Description>
2019-08-13 15:23:28 +02:00
</Properties>
2019-12-03 20:29:48 +01:00
2019-08-13 15:23:28 +02:00
<Dependencies >
Fix the TabTests! (#3833)
## Summary of the Pull Request
Fix the `TabTests`, and enable testing of types with XAML content. The `TabTests` were written many, many moons ago. they were intended to be our tests of XAML-like content within the Terminal app, so we could have unittests of Tabs, Panes, etc. Between their initial authoring and the day they were checked in, we had a bunch of build changes come in and break them irreperably.
We've gotten them fixed now with _one weird trick_ <sup>doctors hate me</sup>. As long as there isn't an `App.xbf` in the test's output directory, then the tests will deploy just fine.
We also needed a bit of magic, cribbed straight from TAEF, to enable running test code synchronously on the UI thread. Hence, `CppwinrtTailored.h`.
## References
## PR Checklist
* [x] Closes #2472
* [x] I work here
* [x] Tests added/passed - you better believe it
* [n/a] Requires documentation to be updated
## Validation Steps Performed
![image](https://user-images.githubusercontent.com/18356694/70185192-ef1d0b00-16ae-11ea-8799-b77061e3cdb0.png)
2019-12-06 21:45:08 +01:00
<TargetDeviceFamily Name= "Windows.Universal" MinVersion= "10.0.17763.0" MaxVersionTested= "10.0.18362.0" />
2019-08-13 15:23:28 +02:00
<PackageDependency Name= "Microsoft.VCLibs.140.00.Debug" MinVersion= "14.0.27023.1" Publisher= "CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US" />
<PackageDependency Name= "Microsoft.VCLibs.140.00.Debug.UWPDesktop" MinVersion= "14.0.27027.1" Publisher= "CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US" />
</Dependencies>
2019-12-03 20:29:48 +01:00
2019-08-13 15:23:28 +02:00
<Resources >
<Resource Language= "en-us" />
</Resources>
2019-12-03 20:29:48 +01:00
2019-08-13 15:23:28 +02:00
<Applications >
2019-12-03 20:29:48 +01:00
<Application Id= "TE.ProcessHost" Executable= "TE.ProcessHost.UAP.exe" EntryPoint= "ProcessHostApplication" >
<uap:VisualElements DisplayName= "TAEF UWA Host Process" Square150x150Logo= "taef.png" Square44x44Logo= "taef.png" Description= "TAEF UWA Host Process" BackgroundColor= "#222222" >
2019-08-13 15:23:28 +02:00
<uap:SplashScreen Image= "taef.png" />
</uap:VisualElements>
</Application>
</Applications>
2019-12-03 20:29:48 +01:00
2019-08-13 15:23:28 +02:00
</Package>