@@ -12,15 +12,31 @@ platforms to access data stored in local {+realms+} and
12
12
interact with {+backend+} services like Functions, MongoDB Data Access,
13
13
and authentication.
14
14
15
- For more information about specific version support for .NET, UWP, and
16
- Xamarin, see our :ref:`compatibility chart <dotnet-compatibility>`.
15
+ .. _dotnet_supported-platforms:
17
16
18
- .. note::
17
+ Supported Platforms
18
+ -------------------
19
+ Realm supports the following platforms for developing Realm apps for iOS and
20
+ Android devices:
19
21
20
- When building
21
- for platforms with Xamarin, you can use either native UI or
22
- `Xamarin Forms
23
- <https://docs.microsoft.com/en-us/xamarin/xamarin-forms/>`__.
22
+ - Xamarin.iOS for iOS 9 or later, using native UI or Xamarin Forms
23
+ - Xamarin.Android for API level 16 or later, using native UI or Xamarin Forms
24
+ - Xamarin.Mac for macOS 10.11 or later, using nativeUI or Xamarin Forms
25
+ - .NET Framework 4.6.1 or later for Windows 8.1 or later
26
+ - Universal Windows Platform applications using .NET Standard 2.0 or later (Fall Creators Update)
27
+ - .NET Core 2.0 or later on the following:
28
+
29
+ - Ubuntu 16.04 or later
30
+ - Debian 8 or later
31
+ - RHEL 7.1 or later
32
+ - macOS 10.11 or later
33
+ - Windows 8.1 or later
34
+
35
+ You can use the following development environments to build Realm apps with
36
+ the .NET SDK:
37
+
38
+ - Visual Studio 2015 Update 2 or higher for Windows
39
+ - Visual Studio for Mac 7.0 or higher
24
40
25
41
Installation
26
42
------------
@@ -29,38 +45,36 @@ To learn how to add the {+service+} .NET SDK library as a dependency
29
45
to your application, see :ref:`Install Realm for .NET
30
46
<dotnet-install>`.
31
47
32
- The Realm Data Model
33
- --------------------
48
+ Realm Data Models
49
+ -----------------
34
50
35
51
You can store a wide variety of data within {+realms+} stored on your
36
- device. With :term:`{+sync+}`, you can share updates to that data across
37
- client devices and {+atlas+}.
52
+ device, and if you enable :term:`{+sync+}`, updates to that data are available
53
+ across multiple client devices. Data models are classes defined in your
54
+ code and in {+realm+} schemas.
38
55
39
56
For information about the structure of data you can store in {+realms+},
40
57
see :ref:`Realms <dotnet-realms>`, :ref:`Objects
41
58
<dotnet-realm-objects>`, and :ref:`Relationships
42
59
<dotnet-client-relationships>`.
43
60
44
- To learn about the results returned from {+realm+} queries, see
45
- :ref:`Collections <android-client-collections>`.
46
-
47
- Work with Realm Database
48
- ------------------------
61
+ Work with a Realm Database
62
+ --------------------------
49
63
50
- Once you have defined a data model for your application, you
51
- need to be able to :ref:`write <dotnet-realm-database-writes>` and
52
- :ref:`read <dotnet-realm-database-reads>` pieces of data to and from
64
+ Once you have defined the data model(s) for your application, you
65
+ can :ref:`write <dotnet-realm-database-writes>` and
66
+ :ref:`read <dotnet-realm-database-reads>` data to and from
53
67
your {+realm+}s.
54
68
55
69
To learn how to query for data in local {+realms+}, see
56
70
:ref:`Query Engine <dotnet-client-query-engine>`.
57
71
58
- For advice on how to safely interact with {+client-database+} across
59
- threads in an application, see :ref:`Threading
60
- <dotnet-client-threading>`.
72
+ To learn about the results returned from {+realm+} queries, see
73
+ :ref:`Collections <dotnet-client-collections>`.
61
74
62
- For information about how to react to changes in {+realm+} data, see
63
- :ref:`Notifications <dotnet-client-notifications>`.
75
+ Mobile application development can be complicated by threading. To learn
76
+ how to work with {+backend-short+} across threads in your application,
77
+ see :ref:`Threading <dotnet-client-threading>`.
64
78
65
79
Work with MongoDB Realm
66
80
-----------------------
0 commit comments