Create Device Installer - Revision history

Anw: Update for new network folder structures.

2019-10-04T16:31:30Z

Update for new network folder structures.

← Older revision		Revision as of 18:31, 4 October 2019
Line 99:		Line 99:
	* Click ''Titanium Android App Store Configuration''.		* Click ''Titanium Android App Store Configuration''.
	* Click '''Add''' and add a new configuration for the project, specifying:		* Click '''Add''' and add a new configuration for the project, specifying:
	** Distribution Location - P:\EPOD\~~_Development\ePOD Release to Google Play~~\Distro		** Distribution Location - P:\Releases\EPOD\Android\Distro
	** Keystore Location - P:\EPOD\_Development\Development Tools\AndroidKeyStore\KeyStore		** Keystore Location - P:\Product\EPOD\_Development\Development Tools\AndroidKeyStore\KeyStore
	** Password - as provided.		** Password - as provided.
	{{Note}} For testing purposes, you may want to add another packager configuration, to create a package locally. Copy the same configuration as above, but specify a different name and distribution location. ALWAYS use this local location for alpha builds, never the project folder.		{{Note}} For testing purposes, you may want to add another packager configuration, to create a package locally. Copy the same configuration as above, but specify a different name and distribution location. ALWAYS use this local location for alpha builds, never the project folder.

Anw: /* Create an APK file */

2013-07-15T13:50:08Z

Create an APK file

← Older revision		Revision as of 15:50, 15 July 2013
Line 105:		Line 105:

	The APK will be built when you choose your distribution configuration from the '''Publish''' button, called "CALIDUS ePOD.apk". Once complete, this should be compressed in this folder as "CALIDUS ePOD.v<versionText>.<ext>".		The APK will be built when you choose your distribution configuration from the '''Publish''' button, called "CALIDUS ePOD.apk". Once complete, this should be compressed in this folder as "CALIDUS ePOD.v<versionText>.<ext>".

			{{Note}} For completeness of documentation, keystores can be created as follows:
			* Click New next to the Keystore Location field to display the Create Keystore window.
			* Next to the Location field, click Browse to display the Save window.
			* Browse to select a folder where the keystore file will be saved.
			* In the Save As field, enter a name for the keystore.
			* Click Save.
			* (Optional) In the Alias field, enter an alias for the private key. If you enter an alias for the key, it will use the same password as the keystore.
			* In the Password field, enter a password for the keystore.
			* In the Confirm Password field, re-enter the password to confirm it.
			* In the Validity (years) field, enter the number of years for which the key will be valid. After the specified time period, the key will expire and the app will need to be resigned. Google recommends a validity period that will exceed the expected lifespan of the Android app (25 years or more).
			* From the Type menu, select the key length for the key - use 2048-RSA.
			* In the First and Last Name field, enter your name.
			* In the Organization Name field, enter the name of the organization, OBS Logistics.
			* In the Organization Unit field, enter the section or division of the organization, for example, EPOD, WCS, etc.
			* In the City or Locality, enter the city or locale where the organization is located, i.e. Liverpool, London, Solihull.
			* In the State or Province field, enter the state or province where your organization is located, e.g. Merseyside.
			* In the Country Code (XX) field, enter the two-letter ISO code i.e. GB
			* Click OK to create the keystore.

	[[Category:WI 287575 EPOD Development and Release Process\|300]]		[[Category:WI 287575 EPOD Development and Release Process\|300]]

Anw: /* Create an APK file */

2013-06-06T12:23:37Z

Create an APK file

← Older revision		Revision as of 14:23, 6 June 2013
Line 95:		Line 95:
	===Create an APK file===		===Create an APK file===
	The Android Client builds to an APK package file, and is created through Titanium Studio.		The Android Client builds to an APK package file, and is created through Titanium Studio.
	Configure the packager from ''Run/Configurations''.
			Configure the packager from ''Run/Configurations''.
	* Click ''Titanium Android App Store Configuration''.		* Click ''Titanium Android App Store Configuration''.
	* Click '''Add''' and add a new configuration for the project, specifying:		* Click '''Add''' and add a new configuration for the project, specifying:

Anw at 12:23, 6 June 2013

2013-06-06T12:23:10Z

← Older revision		Revision as of 14:23, 6 June 2013
Line 84:		Line 84:

	== {{PDAType\|Android=Y}} Android ==		== {{PDAType\|Android=Y}} Android ==
			===Source Preparation===
			* Synchronise with SVN source control.
			* Update Tiapp.xml (if distributing to market) or build for testing
			* Update CHANGELOG.txt (get a list of changes from SVN since the last build and update those.
			* Update Source in SVN - if building for market, check in Tiapp.xml and CHANGELOG.txt with the full details of the latest build from CHANGELOG.txt, example:
			Version 1.2.20:
			* 309133 - Fixed bug whereby loss of data connectivity could affect pending messages being sent.
			* Clean the project

	===Create an APK file===		===Create an APK file===
	The Android Client builds to an APK package file, and is created through Titanium Studio.		The Android Client builds to an APK package file, and is created through Titanium Studio.
Line 94:		Line 103:
	{{Note}} For testing purposes, you may want to add another packager configuration, to create a package locally. Copy the same configuration as above, but specify a different name and distribution location. ALWAYS use this local location for alpha builds, never the project folder.		{{Note}} For testing purposes, you may want to add another packager configuration, to create a package locally. Copy the same configuration as above, but specify a different name and distribution location. ALWAYS use this local location for alpha builds, never the project folder.

	The APK will be built when you choose your distribution configuration from the '''Publish''' button, called "~~Calidus~~ ePOD.apk". Once complete, this should be compressed in this folder as "~~Calidus~~ ePOD.v<versionText>.<ext>".		The APK will be built when you choose your distribution configuration from the '''Publish''' button, called "CALIDUS ePOD.apk". Once complete, this should be compressed in this folder as "CALIDUS ePOD.v<versionText>.<ext>".

	[[Category:WI 287575 EPOD Development and Release Process\|300]]		[[Category:WI 287575 EPOD Development and Release Process\|300]]

Anw: Added Android APK building details

2013-06-06T12:12:14Z

Added Android APK building details

← Older revision		Revision as of 14:12, 6 June 2013
Line 84:		Line 84:

	== {{PDAType\|Android=Y}} Android ==		== {{PDAType\|Android=Y}} Android ==
	~~{{warning}} Whole section needs writing~~		===Create an APK file===
	===~~Building~~===		The Android Client builds to an APK package file, and is created through Titanium Studio.
	* ~~Description - keyfile~~, ~~configurations, etc.~~		Configure the packager from ''Run/Configurations''.
	* ~~What process~~ to ~~follow~~:		* Click ''Titanium Android App Store Configuration''.
	* ~~Where~~ to ~~put~~ the ~~build files~~		* Click '''Add''' and add a new configuration for the project, specifying:
			** Distribution Location - P:\EPOD\_Development\ePOD Release to Google Play\Distro
			** Keystore Location - P:\EPOD\_Development\Development Tools\AndroidKeyStore\KeyStore
			** Password - as provided.
			{{Note}} For testing purposes, you may want to add another packager configuration, to create a package locally. Copy the same configuration as above, but specify a different name and distribution location. ALWAYS use this local location for alpha builds, never the project folder.

			The APK will be built when you choose your distribution configuration from the '''Publish''' button, called "Calidus ePOD.apk". Once complete, this should be compressed in this folder as "Calidus ePOD.v<versionText>.<ext>".

	[[Category:WI 287575 EPOD Development and Release Process\|300]]		[[Category:WI 287575 EPOD Development and Release Process\|300]]

Anw at 11:20, 6 June 2013

2013-06-06T11:20:27Z

← Older revision		Revision as of 13:20, 6 June 2013
Line 1:		Line 1:
	== Windows Mobile ==		== {{PDAType\|WinMo=Y}} Windows Mobile ==
	===Create a CAB file===		===Create a CAB file===
	Assume we have the following solution:		Assume we have the following solution:
Line 83:		Line 83:
	We are ready to ship our application and distributing it. If you want to test it (highly recommendable), you can copy it to the emulator (or share de folder to make it visible from the emulator as a Storage Card) or to the device and install it. You can also uninstall it through the Remove Programs option.		We are ready to ship our application and distributing it. If you want to test it (highly recommendable), you can copy it to the emulator (or share de folder to make it visible from the emulator as a Storage Card) or to the device and install it. You can also uninstall it through the Remove Programs option.

	== Android ==		== {{PDAType\|Android=Y}} Android ==
	{{warning}} Whole section needs writing		{{warning}} Whole section needs writing
	===Building===		===Building===
Line 89:		Line 89:
	* What process to follow:		* What process to follow:
	* Where to put the build files		* Where to put the build files
	~~===Releasing===~~
	* Document how the Google Play Developer website works
	* No passwords!
	* How to upload
	* When to change the description
	* Possible future use: different apk files per client possibly?

	~~Then through market, or sideloading - show how sideloading can be enabled on a device.~~

	[[Category:WI 287575 EPOD Development and Release Process\|300]]		[[Category:WI 287575 EPOD Development and Release Process\|300]]

Anw at 10:28, 4 June 2013

2013-06-04T10:28:59Z

@@ Line 1: / Line 1: @@
-==Create a CAB file==
+== Windows Mobile ==
+===Create a CAB file===
 Assume we have the following solution:
@@ Line 82: / Line 82: @@
 We are ready to ship our application and distributing it. If you want to test it (highly recommendable), you can copy it to the emulator (or share de folder to make it visible from the emulator as a Storage Card) or to the device and install it. You can also uninstall it through the Remove Programs option.
 [[Category:WI 287575 EPOD Development and Release Process|300]]

Anw at 11:33, 9 September 2011

2011-09-09T11:33:10Z

← Older revision		Revision as of 13:33, 9 September 2011
Line 83:		Line 83:
	We are ready to ship our application and distributing it. If you want to test it (highly recommendable), you can copy it to the emulator (or share de folder to make it visible from the emulator as a Storage Card) or to the device and install it. You can also uninstall it through the Remove Programs option.		We are ready to ship our application and distributing it. If you want to test it (highly recommendable), you can copy it to the emulator (or share de folder to make it visible from the emulator as a Storage Card) or to the device and install it. You can also uninstall it through the Remove Programs option.

	[[Category:WI 287575 EPOD Development and Release Process]]		[[Category:WI 287575 EPOD Development and Release Process\|300]]

Anw at 09:53, 9 September 2011

2011-09-09T09:53:18Z

← Older revision		Revision as of 11:53, 9 September 2011
Line 81:		Line 81:
	[[Image:CAB (18).png]]		[[Image:CAB (18).png]]

	We are ready to ship our application and distributing it. If you want to test it (highly recommendable), you can copy it to the emulator (or share de folder to make it visible from the emulator as a Storage Card) or to the device and install it. You can also uninstall it ~~thru~~ the Remove Programs option.		We are ready to ship our application and distributing it. If you want to test it (highly recommendable), you can copy it to the emulator (or share de folder to make it visible from the emulator as a Storage Card) or to the device and install it. You can also uninstall it through the Remove Programs option.

			[[Category:WI 287575 EPOD Development and Release Process]]

Anw: Created page with "==Create a CAB file== Assume we have the following solution: Image:CAB(2).PNG and we want to include a project to create the cab installer for our application, which shou..."

2011-09-09T09:52:20Z

Created page with "==Create a CAB file== Assume we have the following solution: Image:CAB(2).PNG and we want to include a project to create the cab installer for our application, which shou..."

New page

==Create a CAB file==

Assume we have the following solution:

[[Image:CAB(2).PNG]]

and we want to include a project to create the cab installer for our application, which should:1) '''Copy '''''DeviceCoolApp.exe'', the referenced assembly ''MyDeviceLibrary.dll'' and the '''resource file '''called ''SampleKindOfResourceFile.xml'' to the application folder.2) Additionally, it should create a '''shortcut''' in the ''Programs folder ''on the device and3) Set the ''string'' value ''HKLM\Software\Mobile Practices\DeviceCoolApp\Version'' to "1.0".

First of all, we need to add a new Smart Device CAB Project to the solution: '''Right click '''on the solution, '''Add '''- '''New Project...'''

[[Image:CAB (3).png]]

Call it ''DeviceCoolAppInstaller'' and press OK. The new project will appear at the bottom in the Solution Explorer window.

Now, I recommend we change the project properties to get a *nice* product installation. Set the Manufacturer (Mobile Practices) and Product Name (DeviceCoolApp) as follows:

[[Image:CAB (4).png]]

It's time to add DeviceCoolApp.exe (the DeviceCoolApp project output) to the CAB Project. '''Right click '''on DeviceCoolAppInstaller - '''Add '''- '''Project Output...'''

[[Image:CAB (5).png]]

Select DeviceCoolApp on the Project selector, and Primary Output as follows, and press OK.

[[Image:CAB (6).png]]

Visual Studio will detect automatically the DeviceCoolApp dependencies. In this case it will detect MyLibrary.dll

[[Image:CAB (7).png]]

<nowiki>**If the dependencies are not detected, you can rebuild the solution and then </nowiki>'''Right Click '''on Detected Dependencies - '''Refresh Dependencies'''.

As you can see, due to the automatic dependencies detection, we don't need to add ''MyDeviceLibrary ''as Project Output on ''DeviceCoolAppInstaller''.

Now it's time to add the resource file ''SampleKindOfResourceFile.xml ''which should be installed on the Installation folder. Let's use the '''File System Editor''', having the ''DeviceCoolAppInstaller ''project selected press the File System Editor button (btw, it's probably already open).

[[Image:CAB (8).png]]

Now, '''right click''' on Application Folder - '''Add''' - '''File....'''

[[Image:CAB (9).png]]

Browse and find ''SampleKindOfResourceFile.xml'' and press '''OK'''.

[[Image:CAB (10).png]]

Congrats!, now we have all the necessary files ready to be installed. The next step is to add the shortcut.

Unfortunately, the ''Programs Folder'' is not already included on the '''File System Editor''', and we need to include it manually: '''Right click''' on ''File System on Target Machine - '''''Add Special Folder '''''- '''''Programs Folder.'''

[[Image:CAB (11).png]]

And now, select ''Programs Folder'' on the File System tree, and right click on the empty panel at right and select '''Create New Shortcut'''

[[Image:CAB (12).png]]

And select Application Folder - ''Primary output from DeviceCoolApp (Active)'' and press '''OK'''.

[[Image:CAB (13).png]]

And rename it to "Device Cool App"

[[Image:CAB (14).png]]

This will be the application shortcut on the Programs group on the smart device after installation. Now we just have to add the registry entry. Press the '''Registry Editor '''button:

[[Image:CAB (15).png]]

And add the ''string'' value "''HKLM\Software\Mobile Practices\DeviceCoolApp\Version"''. You need to create the path key by key, and the add the string value on the right panel.

[[Image:CAB (16).png]]

Name it "Version" and then, select it, and enter "1.0" into the Value field on the Properties Window

[[Image:CAB (17).PNG]]

And *voila* the ''Smart Device CAB Project ''is done! We're ready to build the solution, right click on the ''DeviceCoolAppInstaller ''project and select '''Build'''.

You can find the '''DeviceCoolAppInstaller.cab '''file in the ''DeviceCoolAppInstaller\debug ''folder.

[[Image:CAB (18).png]]

We are ready to ship our application and distributing it. If you want to test it (highly recommendable), you can copy it to the emulator (or share de folder to make it visible from the emulator as a Storage Card) or to the device and install it. You can also uninstall it thru the Remove Programs option.