Delphi DLL vs Dot Net DLL

[DanB]

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?

[Herfried K. Wagner [MVP]]

* "DanB" <ag*****@kc.rr.com> scripsit:

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"

This cannot be done in VB.NET/C#.

--
Herfried K. Wagner [MVP]
<URL:http://dotnet.mvps.org/>

[BriamDH]

How about if I create an ASPX page that calls the web service.
Then useing "DataSet.GetXML" Write the return value to the HTML part of the
ASPX page as an Data Island. Then within my ASP page call the ASPX page via
IFrame to access the data island.

Right now I am parsing a DI with my VB Script from an IFrame ASP page.

Maybe? anyone?

B

B
"Herfried K. Wagner [MVP]" <hi***************@gmx.at> wrote in message
news:2n************@uni-berlin.de...

* "DanB" <ag*****@kc.rr.com> scripsit:

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"

This cannot be done in VB.NET/C#.

--
Herfried K. Wagner [MVP]
<URL:http://dotnet.mvps.org/>

[David Williams , VB.NET MVP]

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" <ag*****@kc.rr.com> wrote in message
news:#q*************@TK2MSFTNGP09.phx.gbl:

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?

[Dan Bacon]

Thanks , I'll try that.
Dan

"David Williams , VB.NET MVP" <da********************@earthlink.net> wrote
in message news:Oz**************@TK2MSFTNGP11.phx.gbl...

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" <ag*****@kc.rr.com> wrote in message
news:#q*************@TK2MSFTNGP09.phx.gbl:

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?