Click or drag to resize
AlchemyVisual Studio Configuration

Certain aspects of the Visual Studio project for an Alchemy Plugin is configurable.

This topic contains the following sections:

Configuring the Upload to Webstore Dialog
Important note Important

The feature was introduced in 0.6.0.

When an Alchemy Plugin Project builds in Visual Studio, the user is presented with a dialog that allows the developer to immediately upload the plugin to the Webstore if they wish. Although this is handy as a quick way to get your plugin updates to the Webstore, it can be annoying when in active development of your plugin. For this reason, the control for how and when the dialog appears is totally configurable.

There are two ways to configure the Upload Dialog Form.

  1. Use the AlchemyUploadDialog property in the project's .csproj file. The value of this property can be a "0" or "false" to make the dialog never appear, a "1" or "true" to make the dialog always appear, or a pipe separated list of configuration targets. For example, a value of DEBUG|RELEASE will have the dialog appear in both DEBUG and RELEASE build modes, while a value of RELEASE will have the dialog only appear when building for RELEASE.

  2. Define a DefineConstant with a name of AlchemyUploadDialog_<VALUE>, where <VALUE> should be the value of the option on how you want the dialog to appear. For example, defining a constant of AlchemyUploadDialog_RELEASE will make the dialog only appear after building for RELEASE mode.

    Important note Important

    The AlchemyUploadDialog_ Define Constant overrides any property value set in the project's .csproj file.

Configuring the Output Build Files

When an Alchemy Plugin Project builds, a special .a4t plugin package file is created in the output directory. To make it easier to find this package, all non-direct project files are automatically cleared from the output directory (only the .a4t, .dll, .pdb, and .xml files of the actual project will remain). Depending on your needs, this feature is also configurable.

  1. Use the AlchemyRemoveBuildFiles property of the project's .csproj file. The value of this property can be NonProjectAssembly (the default which removes any file not directly output by the project), None (which will not clear any file at all), and All (which will delete everything except for the .a4t file, which was the default behavior prior to verison 0.6).

  2. Define a DefineConstant with a name of AlchemyRemoveBuildFiles_<VALUE>, where <VALUE> should be the value of the option on how you want the build files removed. For example, a defined constant of AlchemyRemoveBuildFiles_All will remove all files except for the .a4t package file on build.

    Important note Important

    The AlchemyRemoveBuildFiles_ Define Constant overrides any property value set in the project's .csproj file.