runfaster2000

We shared our design with Miguel for feedback ahead of the release. He gave us a boatload of very high quality and informed feedback. Thanks! We haven't been able to act on most of it yet, since it relates more to what to do next than what we released just now.

We're hoping to see this NuGet package supported on top of Mono, too. As we've done previously, we'll share our tests with Xamarin to ensure consistent behavior between implementations.

If you've got a problem with ReaderWriterLockSlim, email me (check my profile). I'll get it to the right people.

Here is the MSFT announcement: http://blogs.msdn.com/b/dotnet/archive/2013/11/13/pcl-and-ne...

Some teams at Microsoft do have internal documentation. We decided about 10 years ago, before our product got away from us, to start documenting the architecture. This is something that our management completely supported (they may have even suggested it), and we added this effort to our schedule, not as a "slack time" thing. Turns out that forcing yourself to document the architecture also helps keep the architecture sane because it really hurts to document something ugly.

We also have a ton of specs, archived off over the last 15 years. Those can sometimes be quite useful.