0

I have an installer that needs to verify the presence of certain assemblies in the GAC. These are 3rd party DLLs out of my control.

Because it's in an installer, I'd rather not have this "checker" be written in .NET as I'm trying to avoid managed custom actions. I'm thinking either InstallScript or raw Win32 APIs.

I'm aware of an approach that uses File IO functions to check for assemblies at various paths, but that seems somewhat fragile given policy files and the potential for redirecting assembly versions.

Is there a way to safely resolve assemblies outside of .NET code?

jglouie
  • 12,523
  • 6
  • 48
  • 65

1 Answers1

0

You can use the Metadata Interfaces from unmanaged code. Take a look in particular at IMetaDataDispenser/IMetaDataDispenserEx and IMetaDataAssemblyImport.

Michael Urman
  • 15,737
  • 2
  • 28
  • 44