Framework Unification Policy Change in .Net framework 2.0

Alan discussed Unification Policy in detail in his blog. Unification Policy Unification Policy is first introduced in v1.1. The unification policy’s behavior is to move every assembly reference in the unification policy up (or down, depending on the reference) to the one shipped in .Net framework 1.1. This has some side effect. If you try to load v2.0…


CLR in Channel 9

Channel9 team did a two part interview for CLR team. The video is online at Jason Zander – Tour of the .NET CLR team The .NET CLR Team Tour, Part II The .NET CLR Team Tour, Part III The first developer in the first video is Michael Station. He has a blog at….


Creating a publisher policy

MSDN documented how to create a publisher policy Basically you run al.exe with the “/link” option. The generated publisher policy assembly is a multimodule assembly. The publisher policy config file is the non manifest module. At runtime, fusion finds the publisher policy assembly, and opens its first non manifest module as the publisher policy…


Less is more

Brad Abrams reports four less dlls loaded in Whidbey than in Everett for his helloworld application. *VERY* poor man’s profiler The four dlls are: D:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\fusion.dll D:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\mscorsn.dll D:\windows\\framework\v1.1.4322\mscorlib.dll D:\windows\assembly\gac\system\1.0.5000.0__b77a5c561934e089\system.dll   The first two dlls are not really “not loaded”. In Whidbey they are merged into mscorwks.dll. fusion.dll and mscorsn.dll still exist for backward compatibility reason, but…



If you are brave enough to look at Whidbey’s native image cache, you will see some odd directories ended with ‘#’. C:\WINDOWS\assembly\NativeImages_v2.0.40607_32>dir *# Volume in drive C has no label. Volume Serial Number is 685B-4400  Directory of C:\WINDOWS\assembly\NativeImages_v2.0.40607_32 07/08/2004  01:59 AM    <DIR>          Microsoft.Build.Eng#07/08/2004  01:59 AM    <DIR>          Microsoft.Build.Fra#07/08/2004  01:59 AM    <DIR>          Microsoft.Build.Tas#07/08/2004  01:59 AM    <DIR>          Microsoft.Build.Uti#07/08/2004  02:08 AM   …


Codebase hint in config files

If your assemblies cannot be found by the standard fusion probing logic, you have two options:   1. Hook up AssemblyResolve event. 2. Specify a codebase hint in config files.   The syntax for specifying codebase hint in a config file is in MSDN   An example is given in the link above:…


If you are using Whidbey, you may notice a dll named is loaded in every managed application. It is the native image of mscorlib.dll. Makes perfect sense, right? Except in v1.0/v1.1, mscorlib’s native image is still mscorlib.dll. So why are we making this change? You guess……Surprise! It is because of .local. Remember the .local…


You don’t want to initialize global variables

** This is not a .Net blog ** According to C-FAQs, global variables are guaranteed to start out as zero. 1.30: What am I allowed to assume about the initial values of variables which are not explicitly initialized? If global variables start out as “zero”, is that good enough for null pointers and floating-point zeroes? A:…


Single Servicing

What is Single Servicing? Single Servicing is that when you fix a bug in your component, you drop a single binary with the fix into customer’s machine, everyone using your component automatically get the fix. Sounds easy. But in reality it is much harder. 1. Applications may statically link to your component. Those applications will have to…


Programming Legends Debate .Net, J2EE

Interesting read from Programming Legends Debate .Net, J2EE,1759,1699480,00.asp Source: