xamarin-macios/docs/website
Rolf Bjarne Kvinge 5a45a3c3aa
[src] Remove the ModelAttribute.AutoGeneratedName property in .NET. (#13619)
AutoGeneratedName was a toggle to implement a certain (correct) behavior,
while at the same time not cause breaking changes.

Now that we can do breaking changes in .NET, we can remove the toggle (i.e.
the property), and just always do the right thing (that is: automatically
generate a _unique_ Objective-C name for Model classes, unless a name is
specified manually).

Ref: https://github.com/xamarin/xamarin-macios/issues/5107
2021-12-22 21:28:19 +01:00
..
xamarin-analysis-doc-tool Fix some whitespace issues in various files. (#12399) 2021-08-11 10:06:46 +02: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 Rename master to main. (#8851) 2020-06-16 15:51:44 +02:00
binding_types_reference_guide.md [src] Remove the ModelAttribute.AutoGeneratedName property in .NET. (#13619) 2021-12-22 21:28:19 +01:00
generator-errors.md Rename master to main. (#8851) 2020-06-16 15:51:44 +02: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 Rename master to main. (#8851) 2020-06-16 15:51:44 +02:00
optimizations.md Rename master to main. (#8851) 2020-06-16 15:51:44 +02: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.