[Windows RT Development and Hacking] djboo:
About this Suite:

Arms Apps:

AIP Installer:

Installer for the AIP format. Since V2, the store needs this installed to install downloaded files. Currently must be manually associated with AIP files

Place the exe file and associated DLL in a folder somewhere sensible. I have not tested in ProgramFiles yet but the app elevates UAC so should be ok.

Double click on any AIP file (I include one as an example) and windows willl show this:

select 'more options' which will show this:

check the check box at the top and then click 'Look for another app on this pc'

A browse dialog will open - find and select AIPInstaller and you are done. You only need to do this the first time. I intend to add an auto install to this, so in future you can just double click the installer and it'll set itself up, but till then...

From now on, you can double click an AIP file and the installer will pop up. Usually just hitting 'install' will be all you need to do (there are some advanced functions like disabling the install batch if it exists, and changing the install path which isnt really recommended)

RTD Store V2:

Work in progress version of a new RTD Store. Much simpler and should be more stable. Install and settings currently not implemented. More details coming soon.

PC Apps:

RepoBuild:

run like

RepoBuild.exe d:\dropbox\public\repo

to prep a folder for being a repo. needs to be run on any changes. You may need to FTP files to your server.

RTD Packager:

Create AIP files from a folder or from an MSI file.

This utility is designed for creating AIP files. Its worth paying note that the AIP format is designed for repos more than it is the installer - so there are a lot of details here which the repo can use to make you app more visible.

V1.1 now has full open and save support.

V1.2 has MSI support

Save will save a template XML, which can be loaded later with the Open button. Open will also open an existing AIP file and fill in the details.

Create Package no longer saves in the same place as the files being packaged - it opens a save dialog.

The browse button will now work and populate the run EXE field and the folder field.

some details:

AppName is the display name - and the install folder - so avoid \'s and such. If you change this in an update, it will get installed to a new folder.

Updates are detected based on the App GUID. Change this, it will appear as a new app - use the same GUID on more than one app and you will have conflicts. The generate button for GUID *DOES* work - you should only use it on the first release of your app - and for the time being, keep it safe for any updates.

Run EXE is the exe that will be launched by the store when the user asks to run it - and if a shortcut name exists, will be placed in the start menu.

If you select an MSI from the browse menu, this overrides runEXE (and disables some irrelevant functions)

Install/uninstall batch files are option batch files for installing/uninstalling registry settings and the like. There is currently no uninstaller, but the store app should have this built in - the uninstall batch is NOT for deleting files - the store will handle that.

App version number is a REAL number. ie. 1.03 is ok. 1.0.3 is not.

App category is for placing your app in a 'folder' - it is free form, with | splitting. Anyone can create a new category this way and its not up to the repo manager to manage this. Obviously it will work better if we have sensible categories such as 'Apps|Browsing' or 'Emulators|GameBoy' - while its totally possible to do 'djboo|prerelease|funthing' - i hope we dont do that.

Source codes:

Complete source code for the RTD Repo Connector (used by the store), the store itself and for the RepoBuilder.

Donwload Now