http://ayende.comAyende @ RahienCopyright (C) Ayende Rahien 2004 - 2021 (c) 202660It could be interesting seeing some of the internals of the FCL :P, but actually is only a matter of not using reflector, I hope that the code will have some comment to make it clearer. Alk. http://ayende.com/2823/the-clr-sources#comment10http://ayende.com/2823/the-clr-sources#comment10Thu, 04 Oct 2007 06:12:17 GMTpete, They already do. I have a calendar control that does REALLY nasty things to System.Web.UI.Calendar. Nasty as in this.GetType().GetField("_cantRecall").SetValue(5, this); http://ayende.com/2823/the-clr-sources#comment9http://ayende.com/2823/the-clr-sources#comment9Wed, 03 Oct 2007 20:11:12 GMTSo basically you can now see the code that is causing the bugs in the framework but you still can't do anything about it. They're clearly taunting me. . . http://ayende.com/2823/the-clr-sources#comment8http://ayende.com/2823/the-clr-sources#comment8Wed, 03 Oct 2007 20:07:28 GMTIt seems like not everyone sees this as a good thing. While I am certainly not a conspiracy theorist, this would appear to be a good way for MS to get their claws into existing about source projects. To read more about that, check out what Steven Vaughn-Nichols has to say about it here: http://www.eweek.com/article2/0,1895,2191754,00.asp http://ayende.com/2823/the-clr-sources#comment7http://ayende.com/2823/the-clr-sources#comment7Wed, 03 Oct 2007 20:04:36 GMTI wonder if people will start to tailor their code more around the internals of a given CLR version and less around the exposed interfaces... the result? Higher dependency on a specific version of the runtime. http://ayende.com/2823/the-clr-sources#comment6http://ayende.com/2823/the-clr-sources#comment6Wed, 03 Oct 2007 19:47:25 GMTI think its great news, but the implications are yet to be seen. Even more curious is the motivation for this. http://ayende.com/2823/the-clr-sources#comment5http://ayende.com/2823/the-clr-sources#comment5Wed, 03 Oct 2007 19:11:15 GMTDan: the license restricts you to debugging and not recompiling... http://ayende.com/2823/the-clr-sources#comment4http://ayende.com/2823/the-clr-sources#comment4Wed, 03 Oct 2007 19:06:35 GMTI am not sure there are many implications beyond a lot less reflector debugging, since the license is for reference and not for someone to make and distribute custom versions of the .net Framwork thankfully. http://ayende.com/2823/the-clr-sources#comment3http://ayende.com/2823/the-clr-sources#comment3Wed, 03 Oct 2007 19:00:46 GMTMmm... you can compile a special version of System.Web assembly with an additional constructor for HttpContext where you can inject a mock for HttpContext.Current property. Doesn't it sound lovely ? :-) TypeMock, be afraid... very afraid http://ayende.com/2823/the-clr-sources#comment2http://ayende.com/2823/the-clr-sources#comment2Wed, 03 Oct 2007 18:55:13 GMTOren, it's NOT the CLR sources (meaning the source to the CLR itself), but the Framework Class Library sources that are being MS-RL'ed, and even at that only a subset are being made available. (I've posted a complete Q&A document Microsoft sent me over on my blog.) Still, for those who are interested in the CLR sources, remember Rotor. :-) http://ayende.com/2823/the-clr-sources#comment1http://ayende.com/2823/the-clr-sources#comment1Wed, 03 Oct 2007 17:50:15 GMT