Steps to repro:
1. User A clones a Git project on a shared machine.
2. User B opens the cloned project.
Expected results:
Source control binding should be retained. User B's SSH key should be referenced when the project is opened.
Actual results:
Source control binding is lost.
Workaround:
Run MadCap Flare program as an Admin. (I cleaned the project first by deleting the folders Analyzer, Output, and Project/Users.)
Hopefully I don't have to run Flare as admin every time I access the project on the shared machine! I'm awaiting a reply from Tech Support.
UPDATE: My reply to tech support is below.
Failed to connect to source control when I closed Flare then ran it normally.
This behavior seems like a bug. I shouldn’t have to run Flare as Admin every time I open it on the shared machine, especially since my user is an admin user. Please tell me that Dev is working on a fix.
Git source control binding lost on shared machine
-
- Propellus Maximus
- Posts: 574
- Joined: Tue Oct 03, 2006 7:56 am
- Location: Seattle, WA
- Contact: