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 7895299
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 3, 20262026-06-03T07:36:34+00:00 2026-06-03T07:36:34+00:00

When you load an assembly, one should use the assembly.FullName instead of assembly.Name, in

  • 0

When you load an assembly, one should use the assembly.FullName instead of assembly.Name, in order to avoid conflicts, which has the following format:

“SampleAssembly, Version=1.0.2004.0, Culture=neutral, PublicKeyToken=8744b20f8da049e3”

From MSDN documentation this string can also include “ProcessorArchitecture=????” where ???? can be MSIL, X86, etc. but is optional.

When ProcessorArchitecture property is not defined in the assemblyName string, what rule does Assembly.Load use to query the GAC in order to load an assembly that is compiled for multiple Processor Architectures (x86, Amd64, MSIL)?

Thank you in advance for your help.

  • 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-06-03T07:36:35+00:00Added an answer on June 3, 2026 at 7:36 am

    It is implicit. By the time your Assembly.Load() statement runs, the loader shim has already decided whether the process runs in 32-bit or 64-bit mode. So when it, say, decided for 64-bit mode then only an assembly that targets msil or amd64 can work.

    The GAC is divided in 3 parts, the sub-directory names are GAC_MSIL, GAC_32 and GAC_64. The fusion loader is going to look first in GAC_MSIL to see if a matching assembly can be found. Then looks in one of the two other ones for a match. There is no ambiguity.

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

Sidebar

Related Questions

How should one use Images that must not be embedded in the Assembly (e.g.
Could not load file or assembly 'EntityFramework, Version=4.3.1.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' or one of its
System.Reflection.Assembly.Load(System.IO.File.ReadAllBytes(path)) So this is a work around to not being able to use T4
I use this code to load a .Net assembly to PowerShell: [System.Reflection.Assembly]::Load(System.Windows.Forms, Version=2.0.0.0, Culture=neutral,
I got the following error when executing an unmanaged assembly: Could not load file
If one calls Assembly.Load multiple times does it cause any side effects? e.g. for
I'm having another of these "Could not load file or assembly or one of
Exception message: Could not load file or assembly System.DirectoryServices or one of its dependencies.
Here is the error message: Could not load file or assembly 'file:///myFile.dll' or one
I have this error message could not load assembly 'system.data.entity, version 4.2.0.0, culture=neutral,publickeytoken=b77a5c561934e089' or

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.