Difference between revisions of "AppInventor"

From BCX Media Wiki
Jump to navigation Jump to search
(Created page with " The process to deploy MIT AppInventor involves downloading the setup file and deploying via a BCX Custom Package Tasks. =='''Download'''== Download the setup file from: ht...")
 
 
(2 intermediate revisions by the same user not shown)
Line 11: Line 11:
 
Next, you need to copy the file to your packages$ share or distribution point
 
Next, you need to copy the file to your packages$ share or distribution point
  
eg \\servername\packages$\AppInventor
+
eg \\servername\packages$\EXE\AppInventor
  
  
Line 22: Line 22:
  
  
You can now create a custom package task types to deploy AppInventor using the command syntax below:
+
You can now [[BCX Package Tasks#Custom Package Tasks|'''create a custom package task''']] to deploy AppInventor using the command syntax below:
  
  
'''\\servername\packages$\AppInventor\appinventor_setup_installer_v_1_2.exe /S'''
+
'''\\servername\packages$\EXE\AppInventor\appinventor_setup_installer_v_1_2.exe /S'''
  
  

Latest revision as of 13:36, 14 May 2020

The process to deploy MIT AppInventor involves downloading the setup file and deploying via a BCX Custom Package Tasks.

Download

Download the setup file from:

http://appinventor.mit.edu/explore/content/windows.html


Next, you need to copy the file to your packages$ share or distribution point

eg \\servername\packages$\EXE\AppInventor


If the installation file has been downloaded from the Internet it now needs to be unblocked.

How to unblock files downloaded from the Internet for Deployment.


Create Package Task

You can now create a custom package task to deploy AppInventor using the command syntax below:


\\servername\packages$\EXE\AppInventor\appinventor_setup_installer_v_1_2.exe /S


Note: - It must be a capital S for it to install silently


Sometimes it may be necessary to edit the run-emulator.bat in the application folder, and amend %homepath% to be %homeshare% to prevent the application trying to write to the C: drive.

It is also necessary to enable access to the command prompt for the user to be able to run the scripts needed for the emulator.


After adding the task, only assign to a few individual testing stations to test deployment