xamarin-macios/docs/website
monojenkins 725aedec3d
[mtouch] Always enable experimental-xforms-product-type (#8427)
Not an experiment anymore - it works as expected.

This half-remove the optimization option (it must remain there to avoid
breaking all projects that have it defined) but it will always be `true`
so `Xamarin.Forms.Platform.iOS.dll` will **always** be considered as SDK
code by the linker.

Fix https://github.com/xamarin/xamarin-macios/issues/8407
2020-04-18 10:47:01 -04:00
..
xamarin-analysis-doc-tool [xamarin-analysis] Add rule #6 and updated md file (#3088) 2017-12-12 12:43:36 -05:00
Makefile Synchronize back docs moved to https://docs.microsoft.com (#3771) 2018-04-17 09:02:42 -04:00
README.md [docs] Ease tracking updates to code that requires change to the web site documentation (#573) 2016-08-08 17:07:59 -04:00
binding_objc_libs.md [docs] Make our documentation gender neutral (#6810) 2019-08-21 03:52:52 +02:00
binding_types_reference_guide.md Merge remote-tracking branch 'origin/xcode11' into master-xcode11 2019-09-13 18:35:18 +02:00
generator-errors.md Use relative paths in scripts. (#7545) 2019-12-10 12:47:30 +01:00
mmp-errors.md [mmp] Don't ignore failures to execute pkg-config and simplify/improve logic. (#7969) 2020-02-26 00:38:20 +01:00
mtouch-errors.md [mmp] Don't ignore failures to execute pkg-config and simplify/improve logic. (#7969) 2020-02-26 00:38:20 +01:00
optimizations.md [mtouch] Always enable experimental-xforms-product-type (#8427) 2020-04-18 10:47:01 -04:00
xamarin-ios-analysis.md Synchronize back docs moved to https://docs.microsoft.com (#3771) 2018-04-17 09:02:42 -04:00

README.md

This directory contains documentation files in markdown format.

They are included here to ensure any changes to

  • Tools error codes;
  • Binding attributes;
  • Binding usage

are documented immediately, i.e. in the same commit that the change was introduced.

This also allows any contributor from the community to enhance the documentation with a pull-request.

The Makefile can be used to copy the files into the documentation repo. Once reviewed locally it can be merged just before the release.