INFO

This API documentation is for FAKE version 5.0 or later. The old API documentation can be found here for migration or here for fake 4

This is part of the Fake.DotNet.Mage module.

Mage

Contains helper functions which allow FAKE to call the Manifest Generation and Editing Tool, in short 'MAGE'. The intentional use is the creation of a clickonce application.

Certificates

The MAGE tool wants to sign the manifest using a certificate. It should be clear, that this file is not under source control. On the other hand - you want to be able to run the compile batch on each developer machine. How can we achieve that? In the parameter structure, we use a CertFile property and a TmpCertFile property. Whenever the CertFile was not found, the manifest is signed with a temporary certificate. And the latter one can be shared in the source control.

Nested types and modules

TypeDescription
MageParams

Needed information to call MAGE

Processor

These are the supported processor types of the MAGE tool

TrustLevel

The level of trust to grant the application on client computers.

Functions and values

Function or valueDescription
createApp
Signature: MageParams -> unit

Encapsulates the MAGE call to create a new application's manifest

deployApp
Signature: MageParams -> unit

Encapsulates the MAGE call to deploy an application

run(mp)
Signature: mp:MageParams -> unit

Executes a full run of MAGE commands: first, it creates a new manifest file. Then it signs the manifest, deploys the application and finally signs the deployment.

signDeploy
Signature: MageParams -> unit

Encapsulates the MAGE call to sign the deployment of an application

signManifest
Signature: MageParams -> unit

Encapsulates the MAGE call to sign an application's manifest

updateApp
Signature: MageParams -> unit

Encapsulates the MAGE call to update an existing application's manifest

updateDeploy
Signature: MageParams -> unit

Encapsulates the MAGE call to update the deployment of an application