re: Dynamic binary modules

Nigel Sharples — Fri, 24 Jul 2009 01:18:34 GMT

Try this to get mycode.cs as a string to preserve the newlines:

[string]$code = gc mycode.cs | out-string

Bob Landau — Thu, 23 Jul 2009 03:26:56 GMT

Invoke-Command $s { dir c:\ } # works

I've tried the code snippet for "dynamic modules" using this code as a test

while it compiles fine and loads into my session if I do the following by hand

csc /target:library ./mycode.cs /reference:'C:\Program Files\Reference Assemblies\Microsoft\WindowsPowerShell\v1.0\System.Management.Automation.dll'

Import-Module -Name .\mycode.dll

Send-Greeting -Name bob

The same code fails when I execute the following command

Invoke-Command $s { (Add-Type -TypeDefinition $args[0] -PassThru).Assembly `

| Import-Module } -ArgumentList $code

I've tried both

[string]$code = gc mycode.cs

and

[string]$code = gc mycode.cs -encoding ascii

but get the same error

WARNING: The generated type is not public.

Cannot bind argument to parameter 'Name' because it is null.

+ CategoryInfo : InvalidData: (:) [Import-Module], ParameterBindingValidationException

+ FullyQualifiedErrorId : ParameterArgumentValidationErrorNullNotAllowed,Microsoft.PowerShell.Commands.ImportModul

eCommand

does this make any sense to you?