You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One expirimental feature has been introduced while we work through the best API both for us and for the community
77
+
One experimental feature has been introduced while we work through the best API both for us and for the community
70
78
of other drivers. As such, it is public and we welcome feedback, but should not be considered stable and we will not make
71
79
a major version bump when/if they are changed.
72
80
@@ -82,7 +90,8 @@ are some that may affect a greater number of people:
82
90
83
91
- .NET 3.5 and .NET 4.0 are no longer supported. If you still must use these platforms, then the 1.x series of the driver will continue to be developed.
84
92
85
-
- The nuget package mongocsharpdriver now includes the legacy driver. It includes 3 new nuget packages, MongoDB.Bson, MongoDB.Driver.Core, and MongoDB.Driver. MongoDB.Driver is the replacement for mongocsharpdriver.
93
+
- The nuget package mongocsharpdriver now includes the legacy driver. It depends on 3 new nuget packages, MongoDB.Bson, MongoDB.Driver.Core,
94
+
and MongoDB.Driver. MongoDB.Driver is the replacement for mongocsharpdriver.
86
95
87
96
- We are no longer strong naming (CSHARP-616) our assemblies. Our previous strong naming was signed with a key in our public repository. This did
88
97
nothing other than satisfy certain tools. If you need MongoDB assemblies to be strongly named, it is relatively straight-forward to build the
@@ -95,10 +104,15 @@ assemblies yourself.
95
104
- MongoServer is a deprecated class. Anyone using MongoClient.GetServer() will encounter a deprecation warning and, depending on how your build is
96
105
setup, may receive an error. It is still safe to use this API until your code is ported to the new API.
97
106
98
-
- Improved the BsonSerializer infrastructure (CSHARP-933). Anyone who has written a custom serializer will be affected by this. The changes are minor, but were necessary to support dynamic serializers as well as offering great speed improvements and memory management.
107
+
- Improved the BsonSerializer infrastructure (CSHARP-933). Anyone who has written a custom serializer will be affected by this. The changes are minor,
108
+
but were necessary to support dynamic serializers as well as offering great speed improvements and improved memory management.
99
109
100
110
- ReadPreference(CSHARP-1043) and WriteConcern(CSHARP-1044) were rewritten. These classes are now immutable. Any current application
101
111
code that sets values on these classes will no longer function. Instead, you should use the With method to alter a ReadPreference or WriteConcern.
102
112
var writeConcern = myCurrentWriteConcern.With(journal: true);
103
113
104
-
- Dynamic DictionaryRepresentation (CSHARP-939) has been removed. Its intent was to store, in some manner, anything in a .NET dictionary. In practice, this leads to the same values getting stored in different ways depending on factors such as a "." inside the key name. We made the decision to eliminate this variability. This means that documents that used to serialize correctly may start throwing a BsonSerializationException with a message indicating the key must be a valid string. CSHARP-1165 has a solution to this problem. It should be noted that we will continue to read these disparate representations without error.
114
+
- Dynamic DictionaryRepresentation (CSHARP-939) has been removed. Its intent was to store, in some manner, anything in a .NET dictionary. In practice,
115
+
this leads to the same values getting stored in different ways depending on factors such as a "." inside the key name. We made the decision to
116
+
eliminate this variability. This means that documents that used to serialize correctly may start throwing a BsonSerializationException with a message
117
+
indicating the key must be a valid string. CSHARP-1165 has a solution to this problem. It should be noted that we will continue to read these disparate
0 commit comments