This post originated from an RSS feed registered with .NET Buzz
by Sam Gentile.
Original Post: New and Notable 29 - Rotor Whidbey and CLI/CLR GC Changes
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!
Brad points to Joel's announcement of a Rotor (SSCLI) release for Whidbey. Yay! He also asks what people would like to see with it? For my part I am one of those people you talked about that uses it instead of the product docs to know whats going on in the CLR. I would like to see the Rotor folks not only reach out to the academic community as they have done a fine job of but to us as well; the .NET/CLR development community. More information in the form of inviting some of us CLR bloggers to designn previews, presentations, technical articles, beta builds, etc would be a great start.
Brad also talks about design changes in the GC for Whidbey. “Adding pressure“ to teach the GC about letting go of an object holding an expensive unmanaged resource seems to be Chris Brumme was talking some time back in his comments to me on his ReleaseComObject post “So we want to allow the developer to inform the GC of this cost so that we collect more aggressively. We would also like to provide some services that let you control how many of a scarce resource can be in use at one time.“ This is a significant step forward. What I hope this will do is address the issues I have been raising for years about COM Interop and unmanaged resources and pointers not being cleaned up. I would hope that David Mortenson's team (with Sonja and Adam) could now do something futher for the RCW cleanup issue based on these capabilities.
Previous Topic
