You can use Microclimate Developer Tools for Visual Studio Code to develop your Microclimate projects from within VS Code. Use the tools to access Microclimate features in the comfort of your IDE.
Getting started (Documentation)
- Install VS Code version 1.27 or later and local Microclimate version 18.12 or later.
- Install Microclimate Developer Tools for VS Code from the VS Code Marketplace or by searching for "Microclimate" in the VS Code Extensions view.
If you want to host or build the extension yourself, see Contributing.
How to use (Documentation)
- Navigate to the Explorer view group and open the Microclimate view.
- Right-click the background of the Microclimate view to access the New connection commands.
- After creating a connection, right-click a connection or project to access the other commands.
- Open the Command Palette and type "Microclimate" to see the actions available.
Features (Documentation)
- View all projects in Microclimate, including application and build statuses.
- Debug Microprofile, Spring, and Node.js Microclimate projects.
- View application and build logs in the VS Code Output view.
- View project information similar to the information on the Microclimate Overview page.
- Integrate Microclimate validation errors into the VS Code Problems view.
- Open a shell session into a Microclimate application container.
- Toggle project auto build and manually initiate project builds.
- Scope your VS Code workspace to a Microclimate project or to your
microclimate-workspace. - Disable, enable, and delete projects.
We welcome issues and contributions. For more information, see CONTRIBUTING.md.
Development builds are available here. Follow the Install from a VSIX instructions to install a .vsix.
To host the extension yourself so you can develop or debug it, clone this repository and run the Extension launch in dev/.vscode/launch.json. See Developing Extensions for more information.
You can also build the extension .vsix yourself by running vsce package from dev/. Refer to the before_install and script sections of .travis.yml to see the exact steps the build runs.