Soon. Kinda of.
The underlying problem lies within some asp.net controls using url encoding incorrectly. The ASP.NET folks have been trying to track them all down and that's still ongoing.
The fix actually syncs the url encode with the .NET framework version, and as such uses code from the .NET framework. However that code is not open source, and we've been working with the legal folks to address this. What with the VS2012 beta releases this
hasn't been at the top of everyone's mind, but now that has shipped we're pushing forward again and hope to get signoff within a few weeks.
Once I have that you'll see a new version of the encoders up which will address the issue.
Sorry it's taken so long.