Source Control Issues after Updating to 2018 r2?

This forum is for all Flare issues related to using Source Control.

Source Control Issues after Updating to 2018 r2?

Postby Chicago_HPT on Tue Nov 06, 2018 9:58 am

I'm using Flare 2018 and my project is bound to Team Foundation Server (TFS). After a rocky start back in April, the source control features have been working nicely since. After updating to Flare 2018 r2, however, I started encountering odd behavior related to source control.

  • Up to now, when I modify files that have not yet been checked out, the large "check out" dialog lists all the the project files, with a checkmark next to the files I need to check out. All I have to do is press Enter to check out the files and proceed. Now, however, the dialog displays the project folder (just the folder), unchecked. I can check it but then Flare checks out every file in the project.
  • I've been experiencing synchronization and check-in errors.
  • Just recently, on the eve of our product's first release, checking in the files deleted nearly everything. Much back and forth and restore efforts and file copies later, I had the project back. I unbound it, cleaned up the the project folder on the source control side, then copied the project back to source control and rebound the project. It seemed to work for a brief time but, within an hour, I started getting the weird check-out dialog again.
  • This time, I didn't touch the binding but contined to work with all the files simply checked out. I built and published the project but two files had mysteriously vanished!
  • I also encountered a strange link issue. Two links in a much-used snippet were broken in one particular topic. In that topic, I'd converted the snippet to text and somehow the links went from "Place in project" to "External File." The link was broken but the actual linked files were in their rightful locations. The links in the [unconverted] snippet remain just fine.

Is anyone else experiencing anything like this? I've got tickets into MadCap support but I'm wondering if anyone else is experiencing issues with 2018 r2.

Cheers,
-jeff
Chicago_HPT
Propeller Head
 
Posts: 30
Joined: Sun Feb 03, 2013 6:01 pm

Re: Source Control Issues after Updating to 2018 r2?

Postby Dave Lee on Wed Nov 07, 2018 1:21 am

I use TFS and noticed issues with the Pending Changes list straight after installing 2018r2 - for example, I'm seeing files files listed as "Pending add", which were already added and checked in (some 3 years ago!).
It's a bit annoying as Pending Changes was previously broken for TFS for over a year (from Flare v12 to 2017r3), and now it appears broken again.

As for the "strange link issue", I'd suggest you close the project, then go to Windows Explorer and delete the project's Analyzer folder.
Dave Lee
Master Propellus Maximus
 
Posts: 5368
Joined: Mon Mar 05, 2007 8:33 am
Location: UK

Re: Source Control Issues after Updating to 2018 r2?

Postby Chicago_HPT on Wed Nov 07, 2018 2:26 pm

Thanks Dave. I fixed the link issue, though I admit it didn't occur to me to delete the Analyzer folder to do so.

I'm sorry to hear you're experiencing issues with TFS, too, but I'm glad it's not just me.

-jeff
Chicago_HPT
Propeller Head
 
Posts: 30
Joined: Sun Feb 03, 2013 6:01 pm

Re: Source Control Issues after Updating to 2018 r2?

Postby krsinger on Fri Nov 09, 2018 10:15 am

I'm also experiencing a problem with Source Control check in. Some of my topics with a Pending Add, Locked By Other User status receive the following error message when I try to either Add them or Check them in: "TF14088: '$/Flare/Content/Topics/../....' must be checked in because it is a rename or an undelete." I've tried closing the project and Flare, then opening them both again. I don't know how to get my topics checked in now! Does anyone know what I can do to check them in?

I'd appreciate any thoughts.
Thanks.
krsinger
Jr. Propeller Head
 
Posts: 7
Joined: Thu Feb 18, 2016 8:06 am

Re: Source Control Issues after Updating to 2018 r2?

Postby Dave Lee on Mon Nov 12, 2018 12:27 am

MadCap support suggested removing my local workspace mapping (in Visual Studio), deleting the projects from my local drive, then re-importing all the projects from source control again.

I haven't tried this, so can't confirm it would work.
I've done this before in previous Flare versions that had issues with TFS, and it didn't solve anything.
Dave Lee
Master Propellus Maximus
 
Posts: 5368
Joined: Mon Mar 05, 2007 8:33 am
Location: UK


Return to Source Control

Who is online

Users browsing this forum: No registered users and 4 guests