🚀 go-pugleaf

"C# dll so that I can use the functionality in a
> Delphi (win32) app."

Your problem lies within the AssemblyInfo.cs file of your C# dll. .NET 
Assemblies does not register under COM until you explicitly make .NET 
assmeblies visiable to COM.

Open your AssemblyInfo.cs file in C# IDE. Scroll to the very bottom of the 
file. You'll see 3 clauses:

[assembly: ComVisible(false)]
//[assembly: Guid("")]
//[assembly: TypeLibVersion(1, 0)]

Set the [assembly: ComVisible(true)]
If you find the other 2 clauses usefull, by al means

I think this would sort you out.
ps: i don't think is nesseary to use the command line params to compile.


"Mark Heschl" <mark@no.spam.com> wrote in message 
news:44625449$1@newsgroups.borland.com...
> Hi,
>
> I am trying to compile a C# dll so that I can use the functionality in a
> Delphi (win32) app.  The reason for this is because Crystal Reports XI 
> does
> not work 100% in Delphi or Delphi.NET.
>
> The steps I take when it doesn't work are:
> 1) Compile through BDS2006 and compile as an assembly (application type)
> 2)  From the command line, run "regasm name.dll /tlb" to generate the tlb
> file
> 3)  From the Win32 environment, go to Component | Import Component and 
> then
> select Import .NET Assembly.
>
> When I get to the last screen, no classes are listed and no class
> declarations are evident in the generated name_tlb.pas file
>
> However, in order to get it to work:
> 1)  From the command line, compile  using "csc /t:library name.cs"
> 2)  From the command line, run "regasm name.dll /tlb" to generate the tlb
> file
> 3)  From the Win32 environment, go to Component | Import Component and 
> then
> select Import .NET Assembly.
>
> When I get to the last screen, the classes are present and the generated
> name_tlb.pas file has the class declarations and I can access the 
> procedures
> that I want.
>
> My question is, how do I get the BDS2006 C# flavor IDE to compile the
> project as if it were compiling witt the "/t:library" switch?
>
> Thanks
>
> Mark
>
>