Buildmaster Legacy Features .bmx, .inedox extension will no longer be supported

[antony.booth_1029]

Indeo documentation is still showing that creating a custom extension uses an '.inedox' suffix, yet the Detect Legacy Features section in the administration page states the extension is no longer supported and Buildmaster can not be upgraded to 6.2.13 until all legacy issues have been resolved, so what do I do differently with custom extensions to make them compatible with 6.2.13

[atripp]

Hello, great question.

.indeox deployment is no longer supported, so I updated the documentation as follows

Direct Deployment {#zip-file}

An extension can be directly deployed to an Inedo product's extension root as a simple universal package.

To do for an extension named MyExample, first create a manifest file called upack.json with the following contents:

{
  "name": "MyExample",
  "version": "1.0.1"
}

Then, create a zip file called MyExample.zip with the compiled output in a package folder, and the upack.json at the root, like this:

  /package/
     /MyExample.dll
     /SomeLibrary.dll
  
  /upack.json

Rename the the zip file to MyExample.upack, and copy the .upack file into the Product extensions directory. By default, this will usually be in C:\ProgramData\«product-name»\Extensions, but you can verify the exact location by going to the Admin->All Settings page and looking for the ExtensionsPath value.

Finally, restart the product services (and application pool if hosting in IIS).