This is the official Visual Studio Code IDE for MethodScript. Generally, this code should not be used directly, the extension should be downloaded directly from the Marketplace. First, download Visual Studio Code, then find the MethodScriptVSC extension.
On first run, you will be prompted to link to your jar. This will need to be re-linked if you wish to compile against a different jar, or if the file is moved. If no profile is selected, the plugin should prompt you, but to manually select the profile, use ctrl+shift+p and run "Choose Global MethodScript Profile". You may be prompted to update the jar if you are on a very old version, as this extension only works with the latest versions.
In some cases, you may wish to use a different profile just for this workspace. This can happen, for instance, if you're programming a remote server. In that case, you can choose the workspace profile instead, using the "Choose Workspace MethodScript Profile" command. This will override the global profile, but just for this workspace. The global profile is always used when opening single ms files, however.
The IDE allows you to more easily code in MethodScript. More than just syntax highlighting, the IDE will highlight errors for you as you code, so you don't need to compile the code just to find out something is wrong. Get information about functions, events, and objects, all without leaving the IDE. The functions and highlighting are based on your local copy of MethodScript, which will also include help for extensions and whatever version you're currently running, even if the information on methodscript.com is for another version.
You must be able to run MethodScript from the commandline to get this to work. Java must be installed, and you must have already downloaded the MethodScript/CommandHelper jar file.
See CHANGELOG.md for release notes.
To install the extension in your main Visual Studio Code installation, you must first create a VSIX package. Make sure you install and run from within the sandbox first, then
To publish the version on the marketplace, first ensure that the vsce command is up to date,
so it doesn't fail midway through:
This will publish the version, and create a new commit and release tag. Push the changes