This post originated from an RSS feed registered with .NET Buzz
by Sam Gentile.
Original Post: Customizing the Microsoft .NET Framework Common Language Runtime
Feed Title: Sam Gentile's Blog
Feed URL: http://samgentile.com/blog/Rss.aspx
Feed Description: .NET and Software Development from an experienced perspective - .NET/CLR, Rotor, Interop, MC+/C++, COM+, ES, Mac OS X, Extreme Programming and More!
Having started in 1999, by the year 2002 I already felt old with the CLR/.NET. The exciting discovery phases were over by then. The dozen starting people of the DM CLR list had morphed intro thousands. Consequently, the year 2002, IMHO, saw the publication of the CLR/.NET books that defined the landscape and nothing really since then has really said anything that hadn't been said by then. 2002 saw the defining books of .NET such as Jeff Richter's Applied Microsoft .NET Framework Programming (I still insist it is the 1st book every .NET developer should read), Don's Essential .NET, The Shared Source CLI Essentials, and for the tortured souls stuck doing Interop, Adam's masterpiece, .NET and COM: The Complete Interoperability Guide. There were great books covering all of the areas of .NET. I had written most of my .NET info pages in 2001 and 2002. There was very little left to say and I felt that very little spoke to me after 2002. Phil Stanhope and I contemplated writing a book called “Non-Trivial .NET” because there was nothing coming out that was deep. Today, I got real excited like 2002 again as I stumbled across Steven Pratschner's Customizing the Microsoft .NET Framework Common Language Runtime. CLR wonks drool over this: A Tour of the CLR Hosting API, Controlling CLR Startup and Shutdown, Using the Default CLR Host, Using Application Domains Effectively, Configuring Application Domains, Loading Assemblies in Extensible Applications, Customizing How Assemblies Are Loaded, Domain-Neutral Assemblies, Extending the CLR Security System, Writing Highly Available Microsoft .NET Framework Applications, Enforcing Application-Specific Programming Model Constraints, Managing How the CLR Uses Memory, Integrating the CLR with Custom Schedulers and Thread Pools. In other words, the real stuff, the nitty gritty. This happens to be the kind of issues I now face with the CLR: hosting the CLR in “strange” containers and dealing with CLR shutdown and startup. Steve is in a unique position, having been on the original CLR team and now a PM for the .NET CF. If you want to go beyond VS.NET and do custom things with the CLR, this is the book for you. For example, the chapter Loading Assemblies in Extensible Applications is worth the price of admission alone. This is the kind of stuff that we do in our job and there is nothing out there about this. Highly Recommended!
Previous Topic
