Yeah, I know this is a very dumb question but I would very much like to find
a way to pass data back and forth between a wintegrate v3 session and a .net
app and I know .net doesn't support DDE although googling around I was able
to find some mentions of DDE and C# so that might be one possible solution.

Other things I've thought of:
Writing to shared drive on a windows server
Writing to D3 file and using odbc on other end to read it ....

The problem with both of those is the other app won't see any sort of event
to trigger a read of the data.

Everything is to run on one machine which makes me think dde might be the
only way to go if I can make the .net side work

On May 7, 7:26 am, "Terry Pennington" <terrypen_at_terrypen.com>
wrote:

If you don't mind some programming, write yourself a little ActiveX
that you can activate from Wintegrate via script --> give it some
methods to Start your C# application, get/receive data and also close
the .NET app (or whatever is appropriate) ==> communication  can then
be through "whatever" you like (eg: mail slots, named pipes) between
the ActiveX control and the .NET app  --> heck, even a message queue
if you want.

Heck, maybe your C# project BECOMES the ActiveX control --> pretty
straight forward IF you have access to the skill set

Have D3 write data to a directory type file.  The .net app can easily
monitor the directory for changes using the
System.IO.FileSystemWatcher object.  Inexpensive and easy.

--
Kevin Powick

I think Ross has the right approach but I believe the Object commands
for activating external components weren't introduced until
wintegrate4.  If you can use the Object commands, you'll need a COM
wrapper for the .NET code.  See articles like this for examples of how
to use COM Interop to create such a wrapper.
http://www.codeproject.com/KB/vb-interop/csCom.aspx

You could use the Run script command but I don't know when that was
introduced either:
  Run "dotnetproggie.exe", "param,list,here"

If you need a response back from the proggie, have the C# code write
the the file system and get w3 to read it.  If w3 doesn't block on the
Run you may need to go into a loop to wait for a response.

Of course we can make if happen here if you wish...

HTH

Tony Gravagno
Nebula Research and Development
TG@ remove.pleaseNebula-RnD.com