I am trying to sequence an application in V5.1 that currently works fine in v4.6. I have tried to do the conversion and also do a brand new sequence but on both occasions, when the sequenced app is run it errors with "The program can't start because Vcl50.bpl is missing from your computer. Try reinstalling the program to fix the problem".
This file is installed to 'C:\Windows\System32' when I install the client along with a load of other .bpl files. These files are related to the BDE Administrator that it installs.
If I open the bubble for amendment the application works fine and I can see all the .bpl files in the 'C:\Windows\System32' folder.
I'm building an application which is made of four .app packages: a launcher, a client, a server manager and a runtime.
The launcher's .app is distributed in a .pkg file generated by MonoMac's packaging option. The other .app files are downloaded/auto-updated as ZIP by the launcher.
Bundling a copy of Mono within every single one of those .app files would be a waste of bandwidth / diskspace, but even more than that, I have a Mono server .exe file which is cross-platform and as such doesn't come in an .app bundle nor should pack any platform-specific DLLs. So bundling a private copy of Mono isn't an option.
Is there a way for me to create a .pkg file which has a dependency/requirement on a globally-installed Mono?
I see PackageMaker has a Requirements pane which can run scripts but I have no idea how to properly check whether Mono has been installed without relying on some hardcoded paths and stuff like that.
I'd like to have the installer check whether Mono is installed and if it isn't, install it (or, failing that, display a message with a link to the Mono website for instance).
I ended up switching to Packages which is a pretty neat tool.
I added a pre-install requirement of type "Shell script returns true". My shell script just checks for the "mono" executable using the "which" command:
#!/bin/bash
which mono
$(exit $?)
When the script returns false, I configured Packages to spit out an informative error message with a link to download Mono (for lack of a way to trigger download / installation of Mono).
I have an Adobe AIR application that I package in a native installer for Windows. I just got a new certificate to sign it with and signing it with the new certificate works fine. However if I try to install it on a computer that has a previous version I get an error that the installer has been misconfigured.
If I uninstall the previous version, the installation works fine.
I've looked at the ADT tool and there is a -migrate (Adobe docs) option where you first package and sign an air file with the new certificate and then use the adt -migrate command to sign the air file with the migration (old) certificate. But this won't work because I'm not able to package my app to a .air file since it uses NativeProcess.
I was finally able to use the adt -migrate command. I had to remove the tag from my program-app.xml file. After I did that, I was able to package to an air file without getting an error about the supported profiles. I followed the Adobe docs for the rest of the packaging process and this time installing over the old version didn't result in any errors.
I have aptana studio and install the air adobe 2.0 beta version. I have export a sample program with the extension of air.. But i dont know how to instal it to show as a windows application..
My requirement is :: I want to show up a html page as a windows application. Am i going in the right path. Please help me how to proceed it.
And also i am having some sample air file downloaded from websites.. How to work on it.
intall AIR runtime
then clicking the "*.air" file will install it (system will invoke AIR runtime)
the AIR runtime will also create short-cuts for you, which will be shown as windows application
As Francis mentions and the devnet guide as well, make sure you have AIR installed.
I haven't used Aptana for AIR, but their run guide looks pretty straight forward.
Install Adobe Air SDK and Update the path accordingly.
Install Adobe Air.
Build the application and package it.
Run the *.air file by double clicking on it.
Follow this tutorial to run a Hello World.http://code.tutsplus.com/tutorials/introduction-to-adobe-air--net-986
Adobe Air brings following exception:
The application could not be installed because the AIR file is
damaged. Try obtaining a new AIR file from the application author.
Please add the different reasons which may lead to this error.
We had the same error as this guy:
The file ~/.airappinstall contains the following error:
failed while unpackaging: [ErrorEvent type="error" bubbles=false
cancelable=false eventPhase=2 text="invalid package signature"
errorID=5022]
The actual reason was not a damaged file or something like this, but our machine had a date from the past, which was not valid for the given certificate. After correcting the date/time on the computer, the installation worked just fine.
Even I faced the same error=5022, after thinking a lot on this issue, I finally got the
solution for this problem. It is simple, before installing the air app set the correct Date & Time for the system, WALLA it installs smoothly.
No need of changing the png name or anything else.
I faced this problem yesterday because my antivirus (avast pro/silent mode) was blocking access to file until finishing scanning, looks like installer don't like to wait, so when I switched off silent mode I made antivirus ignore scanning the file and installation completed successfully.
I have a virtual drive mapped to S: so that paths are the same between my home computer and work computer. I was trying to install the AIR app from an S: path. I guess it did it like it. Moving app to my desktop and launching there, worked.
Make sure you are signing the Application distributable and distributing the certificate along with the .air file.
I ran into same problems and solved it this way.
I had this issue when using Flash Builder 4, but building a Flex 3 application.
Basically, the installed AIR SDK in the Flex 3 SDK folder was AIR 1.5.3 (if I remember correctly), but the Flex 4 SDK folder had the AIR 2.0 SDK files (I'm not completely what the problem was).
My solution was to download the AIR 2.0 SDK, and unzip it over the Flex 3 SDK folder. Once I did that, the installation file worked fine. There is actually an article on Adobe about overwriting the AIR SDK files this way, although it didn't mention anything about installations or Flash Builder 4.
Mine was failing because I had another app on my system with the same name. Not a version of the app, a completely different app--native, not AIR.
Once I removed that app it worked fine.
For odd installation errors, keep in mind that Chrome uses a version of Flash that does not support AIR badge installation.
I encountered this error when trying to install an AIR file from an external / network drive. Copied the file locally, and installation proceeded normally.