54f2dae935
This optimization can be enabled when it's not possible to use the managed linker (e.g. **Don't link**) or when the managed linker cannot remove references to deprecated types that would cause an application to be rejected by Apple. References to the existing types will be renamed, e.g. `UIWebView` to `DeprecatedWebView`, in every assemblies. The type definition is also renamed (for validity) and all custom attributes on the types and their members will be removed. Code inside the members will be replaced with a `throw new NotSupportedException ();`. The msbuild test app `MyReleaseBuild` has been updated to test that the optimization is working as expected (device builds are slow so reusing this test has little impact in test time). Basically the test ensure that `UIWebView` is used and cannot be removed by the compiler (optimization) or the managed linker (since it's referenced). Since the optimization is enabled then we can `grep` then final `.app` directory to ensure there's no mention of `UIWebView` inside any of the files that would be submitted. The application can be run, by itself, and will turn green if OK, red if `DeprecatedWebView` can't be found (skeleton replacement for `UIWebView`) or orange if a `NotSupportedException` is thrown. Finally introspection tests have been updated to skip over the deprecated (and renamed) types. It should not be an issue right now, since this optimization is not enabled by default, but it made testing easier. |
||
|---|---|---|
| .. | ||
| MonoTouch.Tuner | ||
| ApplyPreserveAttribute.cs | ||
| BaseProfile.cs | ||
| ChangeLog | ||
| CoreHttpMessageHandler.cs | ||
| CoreMarkStep.cs | ||
| CoreOptimizeGeneratedCode.cs | ||
| CorePreserveCode.cs | ||
| CoreRemoveAttributes.cs | ||
| CoreRemoveSecurity.cs | ||
| CoreSweepStep.cs | ||
| CoreTypeMapStep.cs | ||
| CustomSymbolWriter.cs | ||
| ExceptionalSubStep.cs | ||
| MarkNSObjects.cs | ||
| MobileExtensions.cs | ||
| MobileMarkStep.cs | ||
| MobileProfile.cs | ||
| MobileRemoveAttributes.cs | ||
| MobileResolveMainAssemblyStep.cs | ||
| MobileSweepStep.cs | ||
| ObjCExtensions.cs | ||
| README.linker | ||
| RemoveRejectedTypesStep.cs | ||
| RemoveSelectors.cs | ||
| RemoveUserResourcesSubStep.cs | ||
| ScanTypeReferenceStep.cs | ||
README.linker
README.linker Q: Why some stuff is not linked out ? A: In most case this is because: a) the BCL uses it internally b) the mono runtime depends on the type, methods, class layout = mscorlib.dll = System.Security.PermissionSet * Assembly has (3) fields of that type * mscorlib.xml preserve all fields from Assembly (object-internals.h) * code is "stubified" by the linker System.Security.Policy.ApplicationTrust: * Used as a field in AppDomainSetup; * Field also exists in unmanaged code (domain-internals.h); * mscorlib.xml preserve all fields from AppDomainSetup * only the default .ctor remains and is stubified by the linker System.Security.Policy.Evidence * Used by AppDomain.Load[Assembly] * Used by Assembly.LoadWithPartialName overloads * code is "stubified" by the linker = System.dll = System.Text.RegularExpressions.* * Included because there is 2 regex in UriParser