d7c2a45ca9
- Existing binding projects embed the native libraries within the assembly as managed resource
- This does not scale well and has performance implications
- This PR creates a new property, NoBindingEmbedding which when true processes the building and consumption of binding projects differently.
- Existing binding projects are not affected, they will continue as is
- I've written a full XM test suite and ported a subset to iOS. Since iOS only supports checked in projects, and I didn't want to make the existing situation worse by adding more, I only wrote tests that could use the existing test projects.
-When we complete some form of msbuild testing reform, we'll revisit these tests.
- Remove two files in MyiOSFrameworkBinding that are not used (we use copies elsewhere)
- Remove unnecessary sleep and fix broken touch command
- Output failing test log to console instead of test output
- VSfM does not handle thousands of lines of test failure message well
- Add ability to generate binding projects with LinkWith
|
||
|---|---|---|
| .. | ||
| mac | ||
| ApiTest.cs | ||
| Assert.cs | ||
| AssertHelpers.cs | ||
| BundlerTest.cs | ||
| BundlerTool.cs | ||
| ConditionalCompilation.cs | ||
| Configuration.cs | ||
| ExecutionHelper.cs | ||
| MachO.cs | ||
| MixedClassLibrary.dll | ||
| PlatformInfo.cs | ||
| ProductTests.cs | ||
| Profile.cs | ||
| TestRuntime.cs | ||