Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 451925
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 12, 20262026-05-12T22:01:18+00:00 2026-05-12T22:01:18+00:00

While l was looking over some questions about MEF, I stumbled onto this particular

  • 0

While l was looking over some questions about MEF, I stumbled onto this particular answer to a question. It made me wonder about such a bit since I’ve never had to attempt such but can see it being very valid in the scenario of that question.

Scenario:
If you have a directory of various .Net Assemblies all named different, how would you be able to identify ones that may be the same but renamed (i.e. Copy Of MyAssembly.dll vs MyAssembly.dll)?

I can think of the following items:

  1. Check File Size (should be the same)

  2. Check Assembly Version Number

  3. Loop through the assembly using Reflection and attempt to locate any differences.

Is there any other/easier way of addressing this issue? Are there other criteria to look at for determining if 2 differently named DLLs are in fact the same compiled Assembly?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-12T22:01:18+00:00Added an answer on May 12, 2026 at 10:01 pm

    At first I thought you could use the Equals or ReferenceEquals to do this, but this proofs too error prone. If you use Assembly.LoadFile, this will not work, for instance.

    With nUnit, I did the following tests, which are a bit basic, but gives you something to go on. The weird way of loading the types is necessary (see MSDN). I assume you know how to do the “quick tests” in case you want to check for binary equality etc (see PS below).

    Assembly asm1 = Assembly.LoadFile(@"someDebugAssembly.dll");
    Assembly asm2 = Assembly.LoadFile(@"someReleaseAssembly.dll");
    
    // load all the types (the double try/catch is on purpose)
    Type[] types1 = null
    Type[] types2 = null;
    try
    {
        types1 = asm1.GetTypes();
    }
    catch (ReflectionTypeLoadException e)
    {
        types1 = e.Types;
    }
    try 
    {
        types2 = asm1.GetTypes();
    }
    catch (ReflectionTypeLoadException e)
    {
        types2 = e.Types;
    }
    
    // same length
    Assert.AreEqual(types1.Length, types2.Length);
    
    // check each type
    IEnumerator types1Enumerator =  types1.GetEnumerator();
    types1Enumerator.Reset();
    foreach (Type t in types2)
    {
        types1Enumerator.MoveNext();
        Assert.AreEqual(types1Enumerator.Current, t);
    }
    

    A note on the code: this method of comparison will treat two assemblies as equal when they contain the same types. This means that a debug and a release build, or different versions, are not taken into consideration. Use asm1.GetName() and its properties (again: do not use Equals!) to compare the individual strings (version, full name etc).

    PS: it would be intriguing to define what constitutes two equal assemblies, i.e.:

    1. they are binary equal
    2. there versions and fully qualified names are equal
    3. the strong names are equal
    4. all types, deeply compared, have equal signatures

    depending on what you choose, two entirely different assemblies (i.e. debug build vs release build) can come up as equal. It really depends on how you want to compare.

    Update: corrected previous errors and added code sample

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

While looking at some conceptual questions in C,I came across this question in a
I have been looking over the internet for a while about this, but it
While looking up the answer to this question: Why is an out parameter not
Bounty clarification I know it's a subjective question. The ideal answer I'm looking is
I was looking at some code in Python (I know nothing about Python) and
I stumbled over some code that appears to be correct. It is supposed to
While looking for a way to temporarily save the search results when a user
While looking for ways to find the size of a file given a FILE*
I've just saw an unfamiliar syntax while looking for GroupBy return type: public interface
I'm trying to learn Rails better by looking at example applications, and while looking

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.