Hey all! I am attempting to streamline the way we link our methods using Method Manager 2. Currently, we have different instances of MM2 on each of our lab computers that refer to methods on a shared drive. However, we do not have any version control management software, so every time we need to make a new version, we create another method file. This means that every instance of MM2 needs to be re-linked to the new file, which is tedious and can lead to inconsistency across different machines.
Eventually, I want to get something like GitHub that has versioning management built-in. Since that will be a significant undertaking, I’d like to do something simpler for now. The goal is to set it up in a way so that I only need to change one thing in order to get all MM2 instances to link to the new version of the method.
For example, one idea I had was to use a Windows shortcut in the shared drive that would point to the current version, and then use that shortcut as the MM2 link. The idea would be that when a new version is released, I just need to change the file that the shortcut is pointing to. Unfortunately, this didn’t work since MM2 automatically links to the file location whenever I selected the shortcut, but the principal is something I’d like to pursue.
Has anyone done something like this before? If so, I would love some suggestions!
Secondarily, I’d love to know what the attachments in the MM2 links do. I was unable to find any information on them.
