CODEWITHSUNDEEP
c#.netpowershell.net-assemblyautofac
Dan
Dan

Reputation: 1243

Why does Powershell error importing a module by demanding a specific assembly version?

I have a PowerShell module (.NET assembly) that references the Autofac v3.5.2 and Autofac Configuration v3.3.0 libraries. When I load this module in PowerShell:

PowerShell.exe -NoExit -Command "& {Import-Module -Name .\MyModule.dll }

PowerShell opens, but displays the error:

"Could not load file or assembly 'Autofac, Version=3.3.0.0, Culture=neutral, PublicKeyToken=17863af14b0044da' or one of its dependencies. The system cannot find the file specified."

However, making the same Autofac references from within a Forms or WPF app does not result in an error - everything loads correctly. Note that both the module and UI apps invoke AutoFac Configuration code - they aren't just making reference to those two libraries.

I double checked all the assembly references and they're all set to "Specific Version=False". What then about PowerShell is telling it to require a specific version of the assembly?

Upvotes: 0

Views: 902

Answers (1)

ScheuNZ
ScheuNZ

Reputation: 911

Based on your most recent comment, you might also have some luck handling AppDomain.CurrentDomain.AssemblyResolve as per the article linked below. I've only ever used this when creating proxies that load an appropriate x86 or x64 assembly at runtime, but it does appear you can use it for version forwarding too.

http://blog.slaks.net/2013-12-25/redirecting-assembly-loads-at-runtime/

Upvotes: 1

Related Questions