C# in PowerShell: how to add multiple ReferenceAssemblies

Question

1.00/5 (1 vote)

See more:

, +

Hi , I'm trying to execute C# code in Power Shell 2.0 .

My problem is for the references at the beginning of the code:

$referencingassemblies = (
"C:\Windows\Microsoft.NET\Framework\v4.0.30319\System.XML.dll",

"C:\Windows\Microsoft.NET\Framework\v4.0.30319\System.Linq.dll"
)



code= @"
using System;
using System.Collections;
using System.IO;
using System.Linq;
using System.Xml;
using System.Xml.Linq;

   public class Program
    {
        static void Main()
        {  /* the code witch works*/
        }
    }"@

Add-Type -ReferencedAssemblies $referencingassemblies -TypeDefinition $code -Language "CSharpVersion3" -IgnoreWarnings

Powershell gives me an error saying that The type or namespace Linq doesn't exist. I have Visual studio express 2013.

How can add or import correctly both References at the same time?or what I'm doing wrong?

Posted 17-Apr-14 2:30am

Kinna-10626331

Updated 17-Apr-14 20:35pm

v5

Add a Solution

Comments

DamithSL 17-Apr-14 12:39pm

try with Add-Type -TypeDefinition $code -Language CsharpVersion3 -IgnoreWarnings

Sergey Alexandrovich Kryukov 17-Apr-14 13:38pm

No. The problem is simple: the assembly should be loaded. Please see my answer.
—SA

notjustme 17-Apr-14 14:26pm

I actually explained how to solve this to the original poster about a month ago.

Adding "-ReferencedAssemblies "C:\Here\Are\My\dlls\System.Xml.dll" to the Add-Type command will make the code work. This question is a duplicate really.

Kinna-10626331 18-Apr-14 2:32am

I tried but still don't working because I can' add correctly more than one referenecesAssemblies at the same time

notjustme 18-Apr-14 4:02am

I've shown you how to do this in your original post.

2 solutions

Solution 1

I don't know such namespace. Here is the thing: Power Shell is the interpretive system; and you need to loads some additional assembly which is not loaded by default. As everything in interpretive system, it needs to be loaded "during runtime", dynamically. How? I'll demonstrate how to load an assembly from GAC, if the (default) versions automatically matching the .NET versions your version of Power Shell is targeted to. For example, this is how you can load and use Forms:

$null = [System.Reflection.Assembly]::LoadWithPartialName("System.Windows.Forms")

All the code written after this line is executed can use System.Windows.Forms.Forms, System.Windows.Forms.Application and other declaration required to create windows UI working in PowerShell (I do have such application). Same thing about WPF or nearly any other .NET FCL libraries not loaded by default.

The same way you can load the extra assemblies you need for your functionality. If your assembly is not in GAC, you can load it in some other way. Look at all the methods named [System.Reflection.Assembly]::Load:
http://msdn.microsoft.com/en-us/library/System.Reflection.Assembly%28v=vs.110%29.aspx[^].

This mechanism is pretty non-trivial and specific to Power Shell as interpretive system.

—SA

Posted 17-Apr-14 7:38am

Sergey Alexandrovich Kryukov

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

arpoador · Accepted Answer · 2014-08-01T06:22:00

Solution 2

PowerShell gives you the correct error message: namespace System.Xml.Linq does not exist.

PowerShell v2 uses CLR 2.0, and System.Xml.Linq is not part of it yet.

Update to PS v4, it uses CLR v4.0, which has that namespace.

Posted 1-Aug-14 6:22am

arpoador