Your first step is to load the desired Assembly using the utility.
On my Windows 7 machine, IL DASM is found at Once loaded, you will see a screen like the one below. Double-click on MANIFEST which load the following screen of manifest-specific data: Find the section for the Assembly you’ve loaded – in this case, System.
NET project; the screen shot below was done on a non-production version of that DLL.) Public Key Token=null " data-medium-file="https://codingoutloud.files.wordpress.com/2010/03/reflector-missing-strong-name.png? w=300" data-large-file="https://codingoutloud.files.wordpress.com/2010/03/reflector-missing-strong-name.png? w=150 150w, https://codingoutloud.files.wordpress.com/2010/03/reflector-missing-strong-name.png? w=300 300w" sizes="(max-width: 557px) 100vw, 557px" / While you are at it…
make Reflector the default program for “launching” assemblies (actually would need to be for all files ending in the . NET Assembly has a strong name – but here is a bonus 4th way.
DLL extension, but Reflector is smart enough to not choke on non-. Windows Explorer will not show you the strong name characteristics of an assembly, with one exception – for assemblies in the Global Assembly Cache (GAC), strong name data is included in the Properties dialog. on XAP files, created by signtool.exe, which are validated by the Silverlight runtime for out-of-browser (OOB) applications running with elevated trust.) Strongly Naming and Digitally Signing are largely orthogonal concerns.
If an assembly is not strongly named, the Public key will be missing from the manifest and will not be displayed by sn -Tp command.
Since IL DASM comes with both Visual Studio and with the . NET Developers, and is therefore sometimes the handiest tool. NET Reflector, is a third-party tool, though one adopted by many . Reflector conveniently shows more details about the strong name.