Need the quick ABC's of distributing a Desktop A5 App?

[Fulltimer]

I've been using A5 for a while. Almost exclusively for Web App development. Now that I am using Win 8.1, I need to move away from Visual Foxpro 9. I was thinking of trying A5 to access some local free dbf's.

My question is a simple one. I'm used to creating EXE's with VFP9. I understand that process well. I understand that A5 DOES NOT create an EXE. I would like a quick explanation of how a distribution of a desktop A5 would be handled. I don't need the entire details, I'm just trying to get a "surface" idea of how this works and where do the distributed files come from (i.e. originate) and did I purchase all the needed files when I originally purchased V11 (the whole system).

If you've got a clear understanding of this process, maybe you can share that information or point me in the right direction where a summary is done. Thanks!

[preston2]

Re: Need the quick ABC's of distributing a Desktop A5 App?

This is all I do with Alpha. All desktop distributed as apps.

You are correct. A5 does not create an exe file but uses a runtime to open your .adb database/workspace.

There are ways and processes used to open your A5 db without opening the runtime first and then being asked for the .adb. This is done through command line options in the desktop icon and also a startup file you can create that will then allow the changing of the splash screen and the icon shown on top of the app.

It is not a complex process to do but there are steps you need to do if you wish to make the fact that A5 is what is running the db as hidden from the user as possible.

If you wish for me to get into more detail, just ask.

[DaveM]

Re: Need the quick ABC's of distributing a Desktop A5 App?

I use an installer to do this and it does it consistently with whatever app I need to send.
I happen to still use astrum install wizard which is now free, but no longer maintained. Others are available.

My distributed apps are run from a runtime install so it is easy for me,
astrum "zips" the needed files/folders and even writes to the registry. That way for a single install on one computer, it is a one step process. It installs the runtime, application files/folders and registry entries. Client is the ready to go.

It is a bit more complicated with multiusers across a lan, but very doable.

[Fulltimer]

Re: Need the quick ABC's of distributing a Desktop A5 App?

It is not a complex process to do but there are steps you need to do if you wish to make the fact that A5 is what is running the db as hidden from the user as possible.

If you wish for me to get into more detail, just ask.

Thanks for your input.

-- Is the "runtime" some kind of major EXE file that is located on my development computer?
-- Where is this "runtime" file and what is it called?
-- Does A5 "package up" all project files and database files so that they can be sent somewhere else?
-- Is our critical and private code (i.e. passwords, logins etc) kept secure when distributing an app in this manner? Can the user break it?

Tom

[DaveM]

Re: Need the quick ABC's of distributing a Desktop A5 App?

If you bought the whole package
you should have the installer and another for runtime
one is for your development the other is for unlimited distribution
Alpha dropped their installer/packager for v12, not sure about v11. I could not tell you much about it, since I never used it. Others that did may jump in with information.

My runtime is installed on the root of c:\ as opposed to standard install in program files.
for one user apps the application is installed in a folder beneath that. Makes for a neat install.
for lan setups, I do 2 installs. One for the "server" and a separate one for the runtime. They can all be in the one exe created by the installer if needed.

[DaveM]

Re: Need the quick ABC's of distributing a Desktop A5 App?

You can always send the runtime to the client and let them install it. Then send a zipped copy of the application with instructions on how to start it. Just was not very professional to me and was generally a mess.

My upslogs app is in hundreds of single users hands now. The lan/server is installed in 39 dealerships and they can download the runtime and run it on any new users computers.

Using an installer gives the options of not overwriting dbf, ftp, other files if needed.

[preston2]

Re: Need the quick ABC's of distributing a Desktop A5 App?

Thanks for your input.

-- Is the "runtime" some kind of major EXE file that is located on my development computer?
-- Where is this "runtime" file and what is it called?
-- Does A5 "package up" all project files and database files so that they can be sent somewhere else?
-- Is our critical and private code (i.e. passwords, logins etc) kept secure when distributing an app in this manner? Can the user break it?

Tom

The runtime should have come with the subscription level for V11 that you purchased. It is a separate install file that Alpha should have given you a download link for.

By default when you install the runtime on your development machine it will be installed in C:\Program Files (x86)\a5V11 Runtime on a 64 bit machine.
I always copy that folder out to C:\ just because it is easier for me to find later. The runtime file name is Alpha5.exe, same as the developers file name. Just located in a different directory.

A5 V11 still has the install package creator but I do not think it would include the runtime in the install package. I do not really know because I do not use the A5 install package creator.

As for securing your passwords and log-in stuff, short answer is yes.

Can a user break-in. Depends on how bad they want to break in and how you secured your scripts and functions. If you compile your scripts and functions to an aex file then it is virtually impossible for a user to break into them.

[preston2]

Re: Need the quick ABC's of distributing a Desktop A5 App?

And just an FYI. When the runtime is installed and then run on a computer, the first time it starts up it will ask for a license number. This is "Your License Number that Alpha gave you for the runtime." You would need to provide your users with the license number.

You can get around this by creating a txt file that contains the runtime license number, name the file license.key and save it in the A5 runtime directory. Or you can write the license number to the computer registry.

[DaveM]

Re: Need the quick ABC's of distributing a Desktop A5 App?

I don't give them the number or do the .txt file. I send it to their registry with the installer.

If you go to the registry, you can export the runtime entries and then let astrum installer use that export file and insert the information into the client's registry. Lot easier this way.

I always copy that folder out to C:\ just because it is easier for me to find later. The runtime file name is Alpha5.exe, same as the developers file name. Just located in a different directory.

I install it to a folder on c:\

to send to a user, I copy that folder in total with the installer. Some of the files are not needed, but not that many, so I just get them all.