Skip to content

Update GitM

Knowing when there's a new version

GitM tells you — you don't have to check manually:

  • In SolidWorks: when a newer release is published, a slim strip appears at the top of the GitM task pane — "A new add-in version is available — vX.Y.Z" — with a one-click Download. Dismiss it and it stays hidden until the next version.
  • In GitMCloud: the ? (Help) menu shows "Latest vX.Y.Z" next to Download desktop add-in, and the sign-in getting-started card shows the latest version.

There is no silent auto-update; the nudge just points you at the download. Both link to the stable installer: gitmcloud.gojain.com/download.

For most people the simplest update is to download the latest GitM-Setup-<version>.exe and run it with SolidWorks closed. The installer's fixed product GUID means a newer installer upgrades any earlier install in place — your settings and repositories are untouched, and it re-registers everything cleanly. This is always safe and is the right path when a release adds a new dependency DLL or touches registration.

Fast path for code-only updates (DLL copy)

For code-only updates (bug fixes, new features, UI changes) you do not need to re-run the installer. You only need the three updated DLL files.

Prerequisites

  • SolidWorks closed (so it isn't holding the DLLs).
  • Administrator rights to write to C:\Program Files\GitM\.
  1. Close SolidWorks.
  2. Receive the three DLL files from whoever maintains GitM:
  3. GitM.Core.dll
  4. GitM.UI.dll
  5. GitM.SolidWorks.dll
  6. Copy them into C:\Program Files\GitM\, overwriting the existing files.
  7. Start SolidWorks. The task pane loads the new version immediately.

Verify the update

Hover the ? button in the task pane and click it. The Version menu item shows the new build number (e.g. V1.1.6). If it still shows the old number, SolidWorks was still running during the copy — close it, copy again, reopen.

When you need to re-run the full installer

A DLL-only update is sufficient for the vast majority of releases. Re-run the full installer only if the release notes say one of the following changed:

Reason Why
A new dependency DLL was added The new file won't exist in C:\Program Files\GitM\ yet.
SolidWorks interop DLLs updated Rare; only if targeting a new SolidWorks version.
COM registration needs to change Never happens in a normal update — the CLSID is fixed.

If in doubt, running the installer is always safe — it overwrites cleanly and re-registers everything without affecting your settings or repositories.

For IT admins distributing updates

Zip the three DLL files and send with a one-line instruction. No UAC prompt or wizard needed — just a file copy into C:\Program Files\GitM\. Scriptable via robocopy or any file-deployment tool:

robocopy \\share\GitMUpdate "C:\Program Files\GitM" GitM.Core.dll GitM.UI.dll GitM.SolidWorks.dll

See Deploy GitM across machines for the full installer-based deployment path.

Your settings and repositories are never touched

Neither the DLL update nor a full reinstall touches %APPDATA%\GitM\ (your settings and logs) or your local repository folders. Data is safe either way.