Dyalog Forums

Hi Michael,

I think I now know what's going on. The NativeExe that is mentioned as an argument to bindexe only specifies a Bound executable that uses dyalog121_unicode[rt].dll.

I have logged an issue 005521 that we should add an option to allow you to specify a standalone .exe to this method.

Until then, you will need to use the session menu, File->Export to create your standalone .exe.

Regards,

Vince

Thanks Vince, that's good to know, but the question I intended to ask was more why my standalone .exe still required the dyalog121[rt]_unicode.dll - seems a bit contra-productive for a standalone-thing...?

MBaas wrote:Thanks Vince, that's good to know, but the question I intended to ask was more why my standalone .exe still required the dyalog121[rt]_unicode.dll - seems a bit contra-productive for a standalone-thing...?

How did you create this standalone .exe? Are you sure it is a standalone .exe? Could you send it to support, along with the workspace used to create it please?

Thanks Vince, your reply from Monday looks different now, did you edit that instead of your latest one?
The difference of BoundNative vs. Standalone probably explains it, so I will continue using File/Export, also because I cannot get the i-beam to work...

Thanks

Michael

Yes, I edited my post to remove some of my questions because I think my later post made the picture more clearer, and made the questions unnecessary.