Details

    • Epic Name:
      .NET Core
    • # Replies:
      47
    • Last comment by Customer:
      true
    • Sprint:
      C# Sprint 29, C# Sprint 30, C# Sprint 31, C# Sprint 32, C# Sprint 33, C# Sprint 34, C# Sprint 35, C# Sprint 36, C# Sprint 37, C# Sprint 38, C# Sprint 39, C# Sprint 40, C# Sprint 41

      Description

      Support using the .NET Driver from applications built for .NET Core.

        Issue Links

          Issues in Epic

            Activity

            Hide
            chrishuen Christian Hüning added a comment -

            The timeout message thrown when using a DNS name indicates that you should use the IP address, because the IP behind the DNS resolution could change and therefore a socket could become invalid.

            Show
            chrishuen Christian Hüning added a comment - The timeout message thrown when using a DNS name indicates that you should use the IP address, because the IP behind the DNS resolution could change and therefore a socket could become invalid.
            Hide
            chrishuen Christian Hüning added a comment -

            Some good news besides: I get 50.000 Writes / sec with dotnet and 2.3.0-beta1 on OSX while I get 14.000 Writes / sec with .net 4.5 on Windows 10 (same hardware used). Very nice!

            Show
            chrishuen Christian Hüning added a comment - Some good news besides: I get 50.000 Writes / sec with dotnet and 2.3.0-beta1 on OSX while I get 14.000 Writes / sec with .net 4.5 on Windows 10 (same hardware used). Very nice!
            Hide
            rstam Robert Stam added a comment -

            Thanks to those of you trying out the 2.3.0-beta1 version of the driver.

            Sorry for not announcing the release of beta1 on this ticket. That would have been a good idea. We did announce it on the mongodb-user and mongodb-announce Google Groups.

            We are aware of problems with how the NuGet package was built. The package does not correctly declare the dependencies. See:

            https://jira.mongodb.org/browse/CSHARP-1733

            As a workaround for beta1 you can add the missing dependencies to your own project.json file.

            We are also aware with problems with Sockets and DNS names when running 2.3.0-beta1 on .NET Core on Linux (non-Windows machines). This is due to an issue in .NET Core that we need to work around. See:

            https://jira.mongodb.org/browse/CSHARP-1736

            There is no easy work around for beta1.

            We intend to release beta2 as soon as possible.

            Show
            rstam Robert Stam added a comment - Thanks to those of you trying out the 2.3.0-beta1 version of the driver. Sorry for not announcing the release of beta1 on this ticket. That would have been a good idea. We did announce it on the mongodb-user and mongodb-announce Google Groups. We are aware of problems with how the NuGet package was built. The package does not correctly declare the dependencies. See: https://jira.mongodb.org/browse/CSHARP-1733 As a workaround for beta1 you can add the missing dependencies to your own project.json file. We are also aware with problems with Sockets and DNS names when running 2.3.0-beta1 on .NET Core on Linux (non-Windows machines). This is due to an issue in .NET Core that we need to work around. See: https://jira.mongodb.org/browse/CSHARP-1736 There is no easy work around for beta1. We intend to release beta2 as soon as possible.
            Hide
            chrishuen Christian Hüning added a comment -

            Thanks for the effort! Much appreciated!

            Show
            chrishuen Christian Hüning added a comment - Thanks for the effort! Much appreciated!
            Hide
            henningst Henning Støverud added a comment -

            2.3.0-rc1 was released last monday:
            https://www.nuget.org/packages/MongoDB.Driver/2.3.0-rc1

            Show
            henningst Henning Støverud added a comment - 2.3.0-rc1 was released last monday: https://www.nuget.org/packages/MongoDB.Driver/2.3.0-rc1

              Dates

              • Created:
                Updated:
                Resolved:
                Days since reply:
                41 weeks, 5 days ago
                Date of 1st Reply:

                  Agile