Welcome to MSDN Blogs Sign in | Join | Help

January 2004 - Posts

Microsoft.Net Framework 1.1 setup has ended prematurely

This trick may have shown up somewhere else. But I still see people asking the same question. So I'll post it in my blog. Many people experience failure when installing .Net Framework 1.1 Redist. Usually you see a MSI dialog says “Internal Error
Posted by junfeng | 11 Comments
Filed under:

Name of your-app.exe

MSDN says your assembly's file name should be assembly's simple name, plus .dll/.exe. The reason is those are what we probe. Remember the probing rule? But your-app.exe can be an exception. The exe may have an assembly name of “MyAsm”. But
Posted by junfeng | 4 Comments
Filed under:

Binding Context and LoadFrom

Suzanne has a discussion about binding context here . A binding context is really just a loaded assembly cache. MSDN describes how runtime locates assemblies here . What is missing is that there is a step 5. When we find an assembly, we put it in a binding
Posted by junfeng | 1 Comments
Filed under:

Binding Policy

Alan has a great write-up about assembly binding policy. I'll copy a paragraph to avoid duplicate discussion: <quote> Fusion offers a rich (albeit complex) binding policy system that allows various parties to influence assembly binding behaviour
Posted by junfeng | 0 Comments
Filed under:

Partial name binding

MSDN documents how the runtime locates assemblies here . The probing logic is implemented in fusion. The documentation is correct if the given assembly name is fully specified. A fully specified assembly name is of the following format: “name, Version=xxxx,
Posted by junfeng | 0 Comments
Filed under:

Hello, World

Hi there, My name is Junfeng Zhang and I work in fusion team under AlanShi . Before I joined Microsoft I was a graduate student in University of Wisconsin-Madison . Prior to that I studied in University of Science and Technology of China , in Hefei, Anhui,
Posted by junfeng | 4 Comments
Filed under:
 
Page view tracker