TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:Re: How do you use VMs? From:Robert Lauriston <robert -at- lauriston -dot- com> To:"techwr-l -at- lists -dot- techwr-l -dot- com" <techwr-l -at- lists -dot- techwr-l -dot- com> Date:Wed, 3 Aug 2016 12:32:35 -0700
If your source is in source control, that's where it is.
It makes no difference whether you're running FrameMaker or whatever
locally or in a VM. You would install, configure, and use it in
exactly the same way.
Your source control system won't know the difference. It's the same
client running at a different IP address.
On Wed, Aug 3, 2016 at 12:01 PM, Janoff, Steven
<Steven -dot- Janoff -at- hologic -dot- com> wrote:
> That's awesome, Victoria. Thank you so much for sharing.
> Follow-up question: Do you have revision control on the VM?
> I'm wondering if it makes sense to use for example TFS for FrameMaker projects.
> That might be independent of a VM but in this case it could be hosted on the VM.
Visit TechWhirl for the latest on content technology, content strategy and content development | http://techwhirl.com