On Sep 21, 2:49 pm, Marco Shaw <marco.shaw@_NO_SPAM_gmail.com> wrote:
Quote:
> I've got some C# code to create a custom cmdlet with these statements:
>
> ...
> using System.Collections;
> using System.Collections.Generic;
> using System.Collections.ObjectModel;
> ...
>
> My compile fails:
> PSH> csc /t:library /r:$ref testweather2.cs
> Microsoft (R) Visual C# 2005 Compiler version 8.00.50727.1378
> for Microsoft (R) Windows (R) 2005 Framework version 2.0.50727
> Copyright (C) Microsoft Corporation 2001-2005. All rights reserved.
>
> testweather2.cs(65,13): error CS0246: The type or namespace name
> 'Collection' could not be found (are you missing a
> using directive or an assembly reference?)
> testweather2.cs(69,13): error CS1579: foreach statement cannot operate
> on variables of type
> 'Collection<System.Management.Automation.PSObject>' because
> 'Collection<System.Management.Automation.PSObject>'
> does not contain a public definition for 'GetEnumerator'
> PSH>
>
> So I'm figuring I need to add a couple of references. I'm assuming I
> need to go and find the DLLs for:
> 1. System.Collections
> 2. System.Collections.Generic
> 3. System.Collections.ObjectModel
>
> Are they normally hidden? I can't seem to find them.
>
> Visual Studio C# Express 2005 doesn't have a problem with them though,
> and can compile my code without errors.
>
> That also brings up another point, if the path has spaces, I've not been
> able to figure out how to add a reference with spaces to csc.exe. Tried
> quotes, casting it to a string... I can't figure it out.
>
> Marco
>
> --
> ----------------
> PowerGadgets MVPhttp://www.powergadgets.com/mvp
>
> Blog:http://marcoshaw.blogspot.com Hi Marco,
What's the value of $ref ?
The reason I ask is that I had some hilarious problems before like
this using codegen whereby I omitted the output name and the compiler
took the last reference argument I provided and generated the output
file using this name (e.g. System.Data.dll) and overwrote the real
system.data.dll in the framework directory. Subsequent compilations
failed even worse then because the compiler was referencing _my_
recently created system.data.dll, not the real one (which was now
deleted from the hd). Let me tell you it took a while to find that
one...
- Oisin
- Oisin