Distribute C# DLL

[Guest]

Using C# Express 2005, I have successfully created a DLL to work with non
..NET clients. On the machine that I have created this DLL, it works fine and
exposes its properties, methods and events and the events fire when expected
(except with Excel 2003 where I cannot create an instance). I want to install
it on another PC with .NET Framework 2.0 installed (no C# Express). I have
tried REGASM, the DLL becomes visible BUT I cannot create an instance of it.

In Express 2005, what is Project | Build and Project | Rebuild acomplishing?
This is what I need to replicate. Or, someone knows better?

In simple terms (i.e C# Express 2005 context), please, what do I need to do
with the DLL for it to work on PCs other than the one it was created on , and
where it works?

Thank you for your help.

 

[Guest]

When you say "to work with non-.Net clients", must assume you mean .NET is
not installed on the client. And that means you want to write Com-Callable
wrapper typelibrary so your .NET assembly can be registered for COM?

Typically the Assembly needs to be installed in the GAC, and the typelibrary
registered for COM. A Setup / Deployment project gives you the tools to do
this, if that's what your intentions are.

Peter

 

[Guest]

Thanks for the response, Peter.
By non .NET client I mean a PC that DOES have .NET Framework 2.0 installed
but using client software that does not understand .NET. I happen to be using
APL but it could easily have been Excel or VBScript etc. With APL, on the Pc
originating/constructing the DLL, all works fine but not with Excel (using
its VBA).
The C# Express 2005 does not mention anything about GAC and the SN is off.
I know how to put the DLL in the GAC. What do I do:

1. put the DLL in the GAC on the originating PC? When? Before or after I
rebuild?
2. Then, what do I do on the target PC? Use REGASM? The put the DLL in the
GAC?

Would the Deploymnent Wizard in VS 2005 take care of everything so far as
the target PC is concerned?

Thank you for your valued assistance.