Thanks , I'll try that.
Dan
"David Williams , VB.NET MVP" <(E-Mail Removed)> wrote
in message news:(E-Mail Removed)...
> It sounds like the Delphi DLL that you are creating is using COM to
> communicate. If this is so, then you can accomplish the same
> functionality via COM Interop. To do so, you need to mark the
> "AfterSession" function with the <COMAccessible> attribute.
>
> HTH
>
> David
>
> "DanB" <(E-Mail Removed)> wrote in message
> news:#q#(E-Mail Removed):
> > I need to write a DLL that has a function in it named "AfterSession".
> > (A
> > commercial packages calls this DLL and fills a Structured Type with
> > data.)
> >
> > The example the company shows is written in Delphi. The syntax of
> > Delphi
> > has you identify the procedures etc that are to be exported in the
> > EXPORT
> > section of your program. The resultant DLL when built has entry points
> > defined with offsets etc. One of those entry points is "AfterSession"
> >
> > I am trying to write a VB Dot Net DLL to do the same thing. I started
> > with
> > a component class and added:
> > Public Function AfterSession() etc.
> > I put this in the only class in the program.
> >
> > When I build the DLL it does not work. When comparing the two DLL's I
> > see
> > that mine does not have any Entry Points defined, so I think somehow I
> > need
> > to get this to occur.
> >
> > BTW If I use my DLL as a reference within another VB.NET application it
> > runs
> > as expected.
> >
> > Any ideas?
>
|