DLL functions that returns value to an ISL script var 1

[vonza]

Hi guys,
Have developed a dll that i want it to return a string(char) value to a var in my isl script,
how do i call this function as an assignment to my var?

DLLLoad h_sql, "MFPD.dll"
DLLCall h_sql,Connect(serverip,line,port)

 

[Moregelen]

You must pass and store information using references within the ISL and within your C++ code.

 

[vonza]

I Like this comment but how do i do it, when i use reference my OPS closes down

 

[Moregelen]

Why does it close down? And are you writing your DLL in unmanaged C++ code?

 

[vonza]

No.
am using C

the method Connect(serverip,line,port) already accepts these three parameters. The methods connects to a socket, sends data to the socket and waits for a reply to determine the next course of action. Since i could not receive the reply in my isl, i writes to a text file then I use my dll to read from the file and determine the action to perform which is working fine but at the expense of time. Can use please explain to me on how to use these references.

Thanx and have a good day

 

[Moregelen]

You are missing out on a fundamental concept that you need to understand when working with C or C++. This doesn't come up in newer, 'higher level' languages like Java and C#/VBA/etc as often, but is very important to understand, especially in this instance.

http://www.embedded.com/electronics-blogs/programming-pointers/4023307/References-vs-Pointers

 

[vonza]

Thanx Alot #Moregelen

I solved my problem this way

[/s]void Connect(char *server,char *msg,short port,char *res)
{

char recieve[65];

strcpy(res, recieve);
}

in the ISL i call it this way
DLLCall h_sql, Connect(servername,line, port,ref res)

Thankyou alot for your guidance

 

[Moregelen]

Out of curiosity, which compiler are you using to write your DLL?

 

[vonza]

Hi

Am using MinGW ----gcc

 

[vonza]

my dll is working fine in win32 but in windows ce 6.0 its telling no function defined, could you be having a clue what this is

 

[Moregelen]

Yes. The issue everyone runs into. You have to compile specifically for the WinCE kernel. I know a few people who know how to do it, but they aren't sharing, so I have no idea.

 

[DJensen999]

From what little I've read on the issue, it takes an older hard-to-find copy of MS Visual Studio (2008?) to compile for CE.NET 6.0.

I've also heard that the CE workstations are "on the way out" due to this issue, but have heard no firm timelines aside from April 2018 when it goes EOL.

 

[Moregelen]

There are no firm time lines - and even after EOL I can't imagine there won't be an extension. The sheer number of devices that are running CE right now.. including the new mTablet they just rolled out...

 

[Moregelen]

I did play with this for a while:

http://geekswithblogs.net/WernerWil...-ce-6-or-7-smart-device-application-with.aspx

But eventually came to the same conclusion pmegan said: very rarely do you actually need to do it using a DLL instead of an interface.

 

[vonza]

HI guys
Thanks for this debate, I solved this problems using embedded visual C++ 4.o and with service pack 4.0 and WINCE STANDARDSDK.

when creating a new dll select the win32(WCE X86) FOR WORKSTATIONS AND win32(WCE ARMV4I) FORmTablet CPUs