Two quick points: AppDomain.Load loads an assembly in the current AppDomain and not on myDomain (weird, I know). AppDomain.Load loads an assembly in the Load context, which resolves assemblies from the apps base-dir, the private-bin-paths and the GAC. Most probably, the assembly you try to load is not located in any of these locations which … Read more
Have you tried using the fully qualified assembly name? (e.g. “ycomp.myassembly.dll, Version=1.0.2004.0, Culture=neutral, PublicKeyToken=8744b20f8da049e3”)
Convert the assembly to IL, do a textual search and replace, recompile the IL to an assembly again. Use the standard tools from the .NET SDK.
The tool NDepend offers many features to handle .NET code diff. The panel Search by Change is dedicated to browse assemblies code diff: Many code rules that constraint diff and evolution are proposed. They can be a good start to write your own ones or adapt them to your needs. For example look at the … Read more
It’s not too painful to use command-line tools to filter out MVID and date-time stamps from a text representation of the IL. Suppose file1.exe and file2.exe are built from the same sources: c:\temp> ildasm /all /text file1.exe | find /v “Time-date stamp:” | find /v “MVID” > file1.txt c:\temp> ildasm /all /text file2.exe | find … Read more
I looked through the ASP.NET MVC 2.0 source code and looked up how AreaRegistration.RegisterAllAreas(); is implemented. This line is usually put into the Global.asax Application_Start() method and internally it scans all Assemblies for types that implement the AreaRegistration abstract type. This is kinda the behaviour I’m after. It appears RegisterAllAreas() makes a call to BuildManager.GetReferencedAssemblies(), … Read more
In my case it was a project defined using Target Framework: “.NET Framework 4.0 Client Profile ” that tried to reference dll projects defined using Target Framework: “.NET Framework 4.0”. Once I changed the project settings to use Target Framework: “.NET Framework 4.0” everything was built nicely. Right Click the project->Properties->Application->Target Framework
If both assemblies are strong-named (signed), the CLR will always load from the GAC. Here are the steps the runtime uses to resolve assembly references (from How the Runtime Locates Assemblies): Determines the correct assembly version by examining applicable configuration files, including the application configuration file, publisher policy file, and machine configuration file. If the … Read more
There was a very recent release to solve x64 problems. Get in touch with Mike Barnett directly if you still have problems (mbarnett at microsoft dot com) Addendum. There’s something very, very wrong about your /lib:”C:\Windows\Microsoft.NET\Framework64\v4.0.30319″ option. This has been getting lots of programmers in trouble lately, after .NET 4.5 was released. That directory is … Read more
This is reasonably easy. You have to use reflection. You need an instance of Assembly that represents the assembly with the attributes you want to read. An easy way of getting this is to do: typeof(MyTypeInAssembly).Assembly Then you can do this, for example: object[] attributes = assembly.GetCustomAttributes(typeof(AssemblyProductAttribute), false); AssemblyProductAttribute attribute = null; if (attributes.Length > … Read more