Release v4 and v5

[StephenCleary]

v4 is just bug fixes, but requires a major version bump because it's not possible to compile the code for some of the older platforms; therefore, some old platform support must be dropped.

v5 has some API changes and targets netstandard. AsyncEx has been split up into several smaller libraries for the v5 release, which are available today: AsyncEx.Coordination, AsyncEx.Context, AsyncEx.Tasks, AsyncEx.Oop, AsyncEx.Testing, and Mvvm.Async.

Currently, the plan is to release a v5 AsyncEx "parent" library that contains most or all of these (I'm not sure about including AsyncEx.Testing in the main library, and Mvvm.Async will be added in a future version since it's API is too much in flux at the moment).

[dfandler]

Hi,
i tried to upgrade your AsyncEx library to v4 in my PCL and was not able to install it via nuget.
I just need the AsyncLock Class so i removed my v3 AsyncEx and tried to add the AsyncEx.Coordination

Could not install package 'Nito.AsyncEx.Coordination 1.0.2'. You are trying to install this package into a project that targets '.NETPortable,Version=v4.5,Profile=Profile111', but the package does not contain any assembly references or content files that are compatible with that framework. For more information, contact the package author.

Did you drop the compatibility for Xamarin and/or PCLs in general ?

[StephenCleary]

@dfandler I had to drop Windows 8.0 support, since I no longer use VS2012 with the v4 release.

If you change to Profile151 (.NET 4.5.1, Windows Store 8.1, Windows Phone 8.1), you'll be able to install v4.

[artmon]

Hi,
I have same problem:
Could not install package 'Nito.AsyncEx 4.0.1'. You are trying to install this package into a project that targets '.NETPortable,Version=v4.5,Profile=Profile259', but the package does not contain any assembly references or content files that are compatible with that framework. For more information, contact the package author.
It makes me sad

[dfandler]

@artmon StephenClearys answer solved my problem, you have to change your profile to something that does not support Windows 8.0. (e.g. profile 151)
You can set this under your PCL project options.
After this change, under target frameworks, there should only be Windows 8.1

Also you have to retarget your existing nuget packages (rightclick retarget)

[StephenCleary]

More generally, follow the PCL upgrade guide here.

[StephenCleary]

Status update:

AsyncEx v5 prerelease is available. It currently contains AsyncEx.Context (stable), AsyncEx.Coordination (stable), AsyncEx.Interop.WaitHandles (prerelease), AsyncEx.Oop (stable), AsyncEx.Tasks (prerelease), and Cancellation (stable).

There's a couple of prerelease components as well as the collection that hasn't be brought over to v5 yet (#74). Once those are all done baking, then v5 will become stable.

[frabe1579]

any information regarding v5 stable release?

[StephenCleary]

I'm looking into a strong-naming issue with the current prerelease. Once that's resolved, I'll release v5 stable.

[TonyValenti]

Wanted to let you know I'm looking forward to the update RE strong naming.

[StephenCleary]

@TonyValenti I attempted to get public strong naming working with v5 but unfortunately there were too many issues. Strong naming has been cut for v5. v5 is now only waiting on the resolution of #107 before it is released.

Strong naming will be addressed using an alternative mechanism, one that I expect will be better for the NuGet ecosystem as a whole, instead of just AsyncEx.

[TonyValenti]

Thanks! Is there a version that has strong naming? I'm working on a project that requires it.

[StephenCleary]

There is not right now. The alternative mechanism will provide a strong-named version; until then, I recommend using the Strong Naming Toolkit

[CornedBee]

v5 doesn't appear to support upgradeable locks on AsyncReaderWriterLock. Am I overlooking something?

[StephenCleary]

@CornedBee You're not missing anything; v5 doesn't support upgradeable locks.

[DonaldAirey]

You're not missing anything; v5 doesn't support upgradeable locks.
Why not? This is a deal-killer for me.