6 results found

1. Support for Xamarin.iOS Hot Restart

   One of the coolest Xamarin.iOS features is that you can hook your iOS device to the Windows and debug the application very quickly without having to connect it to the Mac and wait ages until the debugger starts up. Unfortunately, an app containing Realm .NET SDKs won't run with this mechanism and will raise an exception.
   I would really love to see this working. Considering most of the Xamarin apps I do are using Realm, it's a major productivity killer.

   8 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Realm .NET SDK  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

2. .NET MAUI Support

   .NET Maui is evolution of Xamarin.Forms. The former will replace later in second quarter of 2022, probably in April, 2022. The developer experience is going to be much better with Maui. Lots of the developers have already started experimenting with maui.
   Lack of support from Realm is a blocker for those who have already started to migrate their apps from Xamarin.Forms to Maui and for those who want to develop there new apps with Maui.

   4 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Realm .NET SDK  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

3. dateonly and timeonly support

   The .NET now have two new types DateOnly and TimeOnly to represent date and time respectively. The SQL Server already support these types. Having them in Realm .NET SDK will make the development with these data types possible.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Realm .NET SDK  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

4. Event Library Support for .NET CORE for Event Sourcing

   As you can see this https://www.mongodb.com/docs/realm/sdk/swift/sync/event-library/ is only supported on the SWIFT SDK and would be amazing to bring its support in the .NET CORE SDK so that we can have our apps utilise Event Sourcing with mongodb and wouldn't need to go to cosmos or eventstore for this.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Realm .NET SDK  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

5. Allow (optional) read-only access to Realm objects after deletion

   Using Realm with reactive extensions, 3rd party libraries like DynamicData, and UI binding allows one to create beautifully dynamic, responsive apps with very few lines of clean code. This works fantastically for us in all scenarios except for when an item is deleted.

   As we all know, currently any attempt to access an item's properties after deletion throws an exception. This throws a huge spanner in the works for various reactive operations and UI bindings, which may (for implementation detail purposes of object equality checks, UI redraws queued in the event loop queue, or a bunch of other possibilities) still briefly try to read the properties of an object after deletion. Even sometimes just to remove it from an internal cache somewhere along the reactive processing chain when processing the deletion itself.

   As a result we have to constantly walk on eggshells in our code, put in lots of additional checks and filters and ugly hacks like flagging objects as deleted but not actually deleting them, or copying Realm object properties to keep them available, etc., just to try to avoid random app crashes that otherwise occur (since you can't catch these exceptions in any meaningful way when they occur in the middle of a reactive processing pipeline on the UI thread). And to date we have been far from totally successful.

   All this code ugliness and app brittleness could be avoided if Realm object properties could still be read after detaching. It could be opt-in, either on a per-object basis (e.g. there could be an overridable 'AllowDetachedRead' property or similar) or at the Realm level as part of config.

   Another way to offer this would be an optional 'AutoFreezeOnDetach' feature that automatically freezes the object in place when it is removed from the Realm. I tried doing this using existing functionality by calling FreezeInPlace() when the object becomes invalid, but that threw a native exception deep within the bowels of Realm. Not entirely surprised since by that point the object has already been deleted.

   So, can we have an option like this please? It would make life so much simpler and cleaner.

   Using Realm with reactive extensions, 3rd party libraries like DynamicData, and UI binding allows one to create beautifully dynamic, responsive apps with very few lines of clean code. This works fantastically for us in all scenarios except for when an item is deleted.

   As we all know, currently any attempt to access an item's properties after deletion throws an exception. This throws a huge spanner in the works for various reactive operations and UI bindings, which may (for implementation detail purposes of object equality checks, UI redraws queued in the event loop queue, or a bunch of other possibilities)… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Realm .NET SDK  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

6. syncfusion.com support

   Work with the Syncfusion.com Blazor UI components.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Realm .NET SDK  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close