I am developing a winforms app that will use a printing framework for printing reports. The reports use custom classes from the printing framework as return types for methods...
So... now can I create interface assemblies for my clients when there are custom types involved?
For example my interface assembly might look something like this:
VB Code:
public interface EasyPrinting public function PrintLine(byref line as CLine) as boolean end interface
As you can see the CLine type is a custom class(not framework class) and hence I need a reference to my CLine class in the Interface assembly, right??? But that totally defeeat the purpose of using interface assemblies... I don't want to distribute the easyprinting framwork (which includes the CLine class) with the client... I want to call the Easyprinting objects by using Client Activated Objects... The only thing I want to send to the client is the app itself along with an interface assembly to give the client access to all remote methods/classes... all db calls, printing features MQ etc is to be done by .net remoting...
Am I making any sense?
kind regards
Henrik


Reply With Quote