Assuming that my first real-world dll will be ready soon for use with a Runrev stack, and that I wanted other users to be able to try a standalone (or a IDE) version my stack too, how could I arrange for my stack to be accompanied by the necessary dll?
Could I put the dll as a file into a custom property of the stack and then have the stack examine the standard documents of the (Windows) system of my imagined user, create an "Externals" folder there should exist none, and then copy the dll from the custom property into that externals folder?
Would I then have to reload the stack standalone, or would the copying be enough for the stack to work (assuming no call to the uninstalled dll had been issued)?
Would my standalone even statup without the dll being in the proper place at all? I heard of issues on Windows XP which (sometimes? always?) refuses to launch programs which lack needed dlls?
Thanks!
Regards
Stack and External installation
Moderators: FourthWorld, heatherlaine, Klaus, kevinmiller, robinmiller
-
- VIP Livecode Opensource Backer
- Posts: 977
- Joined: Sat Apr 08, 2006 7:47 am
- Location: Aalst, Belgium
- Contact:
Re: Stack and External installation
Quartam Reports & PDF Library for LiveCode
www.quartam.com
www.quartam.com
Re: Stack and External installation
Jan,
thanks a lot! This was the info I was looking for.
Regards
thanks a lot! This was the info I was looking for.
Regards