Flare randomly changes primary target

[skwpt]

I have two online targets. Target A was my original primary, when I had no other online outputs. Now I also have Target B. After I created B, I right-clicked it and selected Make Primary from the submenu.

(Note: This sometimes takes multiple tries, even after a refresh--for example, today I could not switch the primary assignment back to B until after I restarted Flare.)

Working from the Project ribbon, I'd guess that that 3 out of 5 times if I click the Build Primary button (without dropping down into the list and selecting B), I'll watch the Builds window build the wrong target. Flare builds A instead of B.

So I mosey over to the Project Organizer and discover that primary target (B) has reverted back to A.

I have not been able to identify what is causing the internal switch. It seems random. How do you get an assigned primary target to stick?

[RamonS]

Is that project under source control?

[skwpt]

It is under source control, but in a nonstandard way. My local IT guy originally bound the project to Git, but then we realized that Flare doesn't support SSH. So I do all my checkins using SourceTree, but the project is still bound to Git through the Flare interface. If I remember correctly, when we unbound the project, the .git file would get deleted.

Pardon my ignorance. I attended the Madcap Source Control webinar yesterday, but its focus was on managing source through the Flare UI, which I wish I could use.

I don't mind the extra mouse click. I am primarily curious about what is causing the behavior so I can avoid unintentionally messing things up.

[RamonS]

You may want to check if all the files are checked out when you make the change. It may not keep the setting because on file is still checked in. It's at least an idea, wouldn't explain why it works after trying it a few times.

[skwpt]

Thanks, I will try that today.

[NorthEast]

It sounds like you have files added to source control that shouldn't be there.

Do NOT include Project\Users folder in source control, that's where settings are stored.

Source control should not include a number of folders:

Analyzer
FileSync
Output
Project\Users