Looks like version 4 of the CLR has renamed the the 'mscorwks.dll' to 'clr.dll'. I'm assuming that means that code built against version 4 of the CLR will use 'clr.dll' at every point in your book where 'mscorwks.dll' is indicated, as well as using the new version of sos.dll in framework 4.
So far I'm finding that to be the case. Are you aware of any instances where that isn't the case?
Posts
Hello,
ReplyDeleteLooks like version 4 of the CLR has renamed the the 'mscorwks.dll' to 'clr.dll'. I'm assuming that means that code built against version 4 of the CLR will use 'clr.dll' at every point in your book where 'mscorwks.dll' is indicated, as well as using the new version of sos.dll in framework 4.
So far I'm finding that to be the case. Are you aware of any instances where that isn't the case?
Hi,
ReplyDeleteThat's correct - the new module name in CLR 4.0 is clr.dll. I discuss this and other high level changes in Chapter 10 of Advanced .NET Debugging.
Let me know if you have any other questions.