How to add an assembly reference using CodeDOM?

[Mountain Bikn' Guy]

This code (adapted from the examples in the docs) doesn't make complete
sense to me. I have it working, but I'm wondering why I need to declare an
assembly reference in 2 places. TIA.
Dave

CodeCompileUnit compileUnit = new CodeCompileUnit ();
CodeNamespace myNamespace = new CodeNamespace(" MyNamespace");
compileUnit.Nam espaces.Add( myNamespace );
compileUnit.Ref erencedAssembli es.Add(@"MyDLL. dll");//I declare an assembly
reference here first
myNamespace.Imp orts.Add( new CodeNamespaceIm port("System") );
myNamespace.Imp orts.Add( new CodeNamespaceIm port("MyOtherNa mespace") );

[...]

ICodeCompiler compiler = provider.Create Compiler();
CompilerParamet ers cp = new CompilerParamet ers(
new string[] {"System.dll ",

"MyDLL.dll" //Now I still have to declare the assembly reference here too.
Why?

},

filepath.Substr ing(0, filepath.LastIn dexOf(".") + 1)+"dll", false);

[Kalpesh]

I think this is similar to VS.NET IDE does internally

You must be knowing that
1) You can add references to assemblies that you wish to use by "Add
Reference"
2) You can use any of the classes of "References " inside your classes
using "using" statement

So, while compiling, you need to provide, which DLLs you want to add to
current assembly in compilation.

Since, there is a possibility that
Although you have added a ref. to an external assembly, but you dont
want to it to be included as a part of your assembly

Correct me, anyone, if I am conceptually wrong

Kalpesh

Mountain Bikn' Guy wrote:

This code (adapted from the examples in the docs) doesn't make complete
sense to me. I have it working, but I'm wondering why I need to declare an
assembly reference in 2 places. TIA.
Dave

CodeCompileUnit compileUnit = new CodeCompileUnit ();
CodeNamespace myNamespace = new CodeNamespace(" MyNamespace");
compileUnit.Nam espaces.Add( myNamespace );
compileUnit.Ref erencedAssembli es.Add(@"MyDLL. dll");//I declare an assembly
reference here first
myNamespace.Imp orts.Add( new CodeNamespaceIm port("System") );
myNamespace.Imp orts.Add( new CodeNamespaceIm port("MyOtherNa mespace") );

[...]

ICodeCompiler compiler = provider.Create Compiler();
CompilerParamet ers cp = new CompilerParamet ers(
new string[] {"System.dll ",

"MyDLL.dll" //Now I still have to declare the assembly reference here too.
Why?

},

filepath.Substr ing(0, filepath.LastIn dexOf(".") + 1)+"dll", false);

[Mountain Bikn' Guy]

The "using" statements are taken care of by CodeNamespaceIm port. However,
I'm speaking specifically about the need to declare assembly references
twice. I make one call with ReferencedAssem blies.Add. Then I am still
required (or I get errors) to define the assembly reference again as a
CompilerParamet ers parameter. That is the part that doesn't make sense to
me. It seems that ReferencedAssem blies.Add is not fully taking care of of
the task of defining a referenced assembly.
Dave

"Kalpesh" <sh*********@ya hoo.com> wrote in message
news:%2******** ********@tk2msf tngp13.phx.gbl. ..

I think this is similar to VS.NET IDE does internally

You must be knowing that
1) You can add references to assemblies that you wish to use by "Add
Reference"
2) You can use any of the classes of "References " inside your classes
using "using" statement

So, while compiling, you need to provide, which DLLs you want to add to
current assembly in compilation.

Since, there is a possibility that
Although you have added a ref. to an external assembly, but you dont
want to it to be included as a part of your assembly

Correct me, anyone, if I am conceptually wrong

Kalpesh

Mountain Bikn' Guy wrote:

This code (adapted from the examples in the docs) doesn't make complete
sense to me. I have it working, but I'm wondering why I need to declare an assembly reference in 2 places. TIA.
Dave

CodeCompileUnit compileUnit = new CodeCompileUnit ();
CodeNamespace myNamespace = new CodeNamespace(" MyNamespace");
compileUnit.Nam espaces.Add( myNamespace );
compileUnit.Ref erencedAssembli es.Add(@"MyDLL. dll");//I declare an assembly reference here first
myNamespace.Imp orts.Add( new CodeNamespaceIm port("System") );
myNamespace.Imp orts.Add( new CodeNamespaceIm port("MyOtherNa mespace") );

[...]

ICodeCompiler compiler = provider.Create Compiler();
CompilerParamet ers cp = new CompilerParamet ers(
new string[] {"System.dll ",

"MyDLL.dll" //Now I still have to declare the assembly reference here too. Why?

},

filepath.Substr ing(0, filepath.LastIn dexOf(".") + 1)+"dll", false);

[Alan Pretre]

"Mountain Bikn' Guy" <[e-mail] > wrote in message
news:gsdlb.8451 78$uu5.150092@s ccrnsc04...

This code (adapted from the examples in the docs) doesn't make complete
sense to me. I have it working, but I'm wondering why I need to declare an
assembly reference in 2 places.

CodeCompileUnit compileUnit = new CodeCompileUnit ();

Hi. I'm wondering why you are working with CodeCompileUnit at all? Do you
have source code you are trying to compile or what?

If you have source code to work with then you would create the Compiler
object, add your CompilerParamet ers object, add your ReferencedAssem blies
and call CompileAssembly FromSource() to compiler. In this situation there
is only one time you need to add references.

-- Alan