Alan discussed Unification Policy in detail in his blog. Unification Policy http://blogs.msdn.com/alanshi/archive/2004/02/15/73244.aspx Unification Policy is first introduced in v1.1. The unification policy's behavior is to move every assembly reference...

Channel9 team did a two part interview for CLR team. The video is online at channel9.msdn.com. Jason Zander - Tour of the .NET CLR team http://channel9.msdn.com/ShowPost.aspx?PostID=29506 The .NET CLR Team Tour, Part II http://channel9.msdn.com/ShowPost...

MSDN documented how to create a publisher policy http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpguide/html/cpconcreatingpublisherpolicyfile.asp Basically you run al.exe with the "/link" option. The generated publisher policy assembly...

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...

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...

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 http://msdn...

If you are using Whidbey, you may notice a dll named mscorlib.ni.dll 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...

** This is not a .Net blog ** According to C-FAQs, global variables are guaranteed to start out as zero. http://www.faqs.org/faqs/C-faq/faq/index.html 1.30: What am I allowed to assume about the initial values of variables which are not explicitly initialized...

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...

Interesting read from eweek.com Programming Legends Debate .Net, J2EE http://www.eweek.com/article2/0,1759,1699480,00.asp Source: http://www.theserverside.net http://www.theserverside.net/news/thread.tss?thread_id=29747

Starting in Whidbey beta2, for Assembly.LoadFrom/LoadFile/Load(byte[]) , if there is an assembly in GAC with exactly the same assembly identity, we will return the one in GAC. ReflectionOnlyLoad and ReflectionOnlyLoadFrom APIs are not affected. C:\>more...

Windows XP has a new Common Controls library comctl32.dll version 6, which implements XP's look & feel. comctl32.dll version 6 is a side by side assembly deployed to %windir%\WinSxs (the equavalent of GAC in Fusion/Win32). For compatibility reason...