dotnet/reactive (Microsoft.Reactive.Testing)
### [`v3.1.1`](https://togithub.com/dotnet/reactive/releases/tag/v3.1.1): Rx and Ix 3.1.1
Minor packaging update that ensures the `NETStandard.Library` meta-package isn't referenced by projects targeting the Desktop .NET Framework (4.5 and 4.6).
### [`v3.1.0`](https://togithub.com/dotnet/reactive/releases/tag/v3.1.0): Rx and Ix 3.1
The Reactive and Interactive Extensions v3.1 is a minor update to the libraries, consisting mostly of bug fixes and small enhancements.
The full list of items fixed/improved is available [here](https://togithub.com/Reactive-Extensions/Rx.NET/milestone/2?closed=1), but below are some key highlights:
- [#205](https://togithub.com/dotnet/reactive/issues/205) Implement an assembly version strategy
- [#237](https://togithub.com/dotnet/reactive/issues/237) Rewrite of Ix Async to reduce memory allocations, make the code easier to read and fix many bugs
- [#273](https://togithub.com/dotnet/reactive/issues/273) Restored access to the `PlatformEnlightenmentProvider.Current` setter
Many thanks to [@aelij](https://togithub.com/aelij) for his excellent work in converting Ix Async to use `async` and `await` in [#170](https://togithub.com/dotnet/reactive/issues/170).
**Note for Desktop .NET Users**: As part of [#205](https://togithub.com/dotnet/reactive/issues/205), we now have a strict assembly versioning scheme in place. This may require binding redirects to work correctly. NuGet will generate these for you, so there's nothing you should have to do. If you're seeing issues, before reporting a bug, please verify you have `AutoGenerateBindingRedirects` enabled as described [here](https://msdn.microsoft.com/en-us/library/2fc472t2%28v=vs.110%29.aspx). You may need to manually add it some older projects.
### [`v3.0.0`](https://togithub.com/dotnet/reactive/releases/tag/v3.0.0): Reactive and Interactive Extensions for .NET 3.0
Major update from [version 2.2.5](https://togithub.com/Reactive-Extensions/Rx.NET/releases/tag/v2.2.5) adding support for .NET Core and the .NET Platform Standard. In addition to .NET Core support, a few bugs were addressed.
This update is the first after [moving to the .NET Foundation](http://www.dotnetfoundation.org/blog/rx-net-welcome). As such, there are a few noteworthy items:
- The strong name key has been changed. The old key was a Microsoft key that could not be fully checked-in. The new key is checked in, allowing anyone to create custom builds easily.
The package names have all changed
- The NuGet package names have changed. The `Rx-*` and `Ix-*` packages have been renamed to match their library names, keeping inline with the rest of .NET Core. As the strong name key had to change, we did update the old packages as the new binaries incompatible due to strong name conflicts. They are fully source-code compatible.
- Use `System.Reactive` instead of `Rx-Main`
- Use `System.Interactive` instead of `Ix-Main`
- Use `System.Interactive.Async` instead of `Ix-Async`
- The supported platforms are .NET Platform Standard 1.0 and higher. This means the following minimum versions:
- .NET Core App 1.0
- .NET 4.5
- Windows 8
- Windows Phone 8 Silverlight
- Windows Phone 8.1
- On Visual Studio 2012 and 2013, NuGet 2.12 is required. On VS 2015, NuGet 3.4 or later is required.
As always, Rx and Ix have enhanced support per-platform, ensuring an optimal experience based on your target runtime.
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
[ ] If you want to rebase/retry this PR, check this box
This PR has been generated by Mend Renovate. View repository job log here.
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
This PR contains the following updates:
0.0.1-alpha-00362
->6.0.0
Release Notes
dotnet/reactive (Microsoft.Reactive.Testing)
### [`v3.1.1`](https://togithub.com/dotnet/reactive/releases/tag/v3.1.1): Rx and Ix 3.1.1 Minor packaging update that ensures the `NETStandard.Library` meta-package isn't referenced by projects targeting the Desktop .NET Framework (4.5 and 4.6). ### [`v3.1.0`](https://togithub.com/dotnet/reactive/releases/tag/v3.1.0): Rx and Ix 3.1 The Reactive and Interactive Extensions v3.1 is a minor update to the libraries, consisting mostly of bug fixes and small enhancements. The full list of items fixed/improved is available [here](https://togithub.com/Reactive-Extensions/Rx.NET/milestone/2?closed=1), but below are some key highlights: - [#205](https://togithub.com/dotnet/reactive/issues/205) Implement an assembly version strategy - [#237](https://togithub.com/dotnet/reactive/issues/237) Rewrite of Ix Async to reduce memory allocations, make the code easier to read and fix many bugs - [#273](https://togithub.com/dotnet/reactive/issues/273) Restored access to the `PlatformEnlightenmentProvider.Current` setter Many thanks to [@aelij](https://togithub.com/aelij) for his excellent work in converting Ix Async to use `async` and `await` in [#170](https://togithub.com/dotnet/reactive/issues/170). **Note for Desktop .NET Users**: As part of [#205](https://togithub.com/dotnet/reactive/issues/205), we now have a strict assembly versioning scheme in place. This may require binding redirects to work correctly. NuGet will generate these for you, so there's nothing you should have to do. If you're seeing issues, before reporting a bug, please verify you have `AutoGenerateBindingRedirects` enabled as described [here](https://msdn.microsoft.com/en-us/library/2fc472t2%28v=vs.110%29.aspx). You may need to manually add it some older projects. ### [`v3.0.0`](https://togithub.com/dotnet/reactive/releases/tag/v3.0.0): Reactive and Interactive Extensions for .NET 3.0 Major update from [version 2.2.5](https://togithub.com/Reactive-Extensions/Rx.NET/releases/tag/v2.2.5) adding support for .NET Core and the .NET Platform Standard. In addition to .NET Core support, a few bugs were addressed. This update is the first after [moving to the .NET Foundation](http://www.dotnetfoundation.org/blog/rx-net-welcome). As such, there are a few noteworthy items: - The strong name key has been changed. The old key was a Microsoft key that could not be fully checked-in. The new key is checked in, allowing anyone to create custom builds easily. The package names have all changed - The NuGet package names have changed. The `Rx-*` and `Ix-*` packages have been renamed to match their library names, keeping inline with the rest of .NET Core. As the strong name key had to change, we did update the old packages as the new binaries incompatible due to strong name conflicts. They are fully source-code compatible. - Use `System.Reactive` instead of `Rx-Main` - Use `System.Interactive` instead of `Ix-Main` - Use `System.Interactive.Async` instead of `Ix-Async` - The supported platforms are .NET Platform Standard 1.0 and higher. This means the following minimum versions: - .NET Core App 1.0 - .NET 4.5 - Windows 8 - Windows Phone 8 Silverlight - Windows Phone 8.1 - On Visual Studio 2012 and 2013, NuGet 2.12 is required. On VS 2015, NuGet 3.4 or later is required. As always, Rx and Ix have enhanced support per-platform, ensuring an optimal experience based on your target runtime.Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.