Re:Announcing the new Roslyn-powered .NET Framework Referenc...
by shanselman on Tuesday February 25, 2014 @12:28PM
(#7298976)
No, we're NOT intentionally censoring anything. This looks like a bug in the source processing. We'll take a look.
If you see a munged file, report it with the feedback link. Sometimes regex's go bad and we can fix them.
Re:Announcing the new Roslyn-powered .NET Framework Referenc...
by rossy on Tuesday February 25, 2014 @10:30PM
(#7302704)
That's good to hear! I only guessed the missing parts were censored because a lot of them came after comments that implied the following code was security critical, like here: http://referencesource-beta.microsoft.com/#PresentationFrame...
I apologise if this isn't the case, and I'll definitely use the feedback link if this issue comes up again.
One of the first things I had to do for my last job was subclass Window to support custom borders (Zune Player/VS2012/Office 2013 style.) I took a peek at the reference source, and I couldn't help but think the missing bits were the juicy bits, workarounds for window manager bugs or insights into how it does things.