dotSoftwaredotDevelopmentdotCustomersdotAbout us
PushOk logoblank
bullet Home
bullet My software
bullet Support
bullet My payments
bullet My info
bullet Subscriptions
bullet Voting
bullet Contact us
fast linksFast Links
news&eventsnews and events

2012-12-21 
Major update of SVNCOM version 1.7.2 are finaly released

2012-12-21 
Major update of SVN SCC plug-in - versions 1.7.2 are finaly released

Lightweight embedded Node.js database with MongoDB API.

Ticket

Search go
PushOk Logo blank
leftTicketright

Issues using the SVN plug-in with MadCap Flare 6

( SVNSCC , Flare 6.x, 1.7.2, Windows 7 Professional, x64  )
Type: Public Status:Opened Created: 24 May 13 05:00 Updated: 24 May 13 05:00
--> Alonna (user)  at 24 May 13 05:00 writes

Since installing the trial version of the SVN plug-in, version 1.7.2, to
connect Subversion/TortoiseSVN and MadCap Flare version 6, I have run into
two major issues:

1. On more than one occasion, the local working copy and the Subversion
copy have gotten out of sync across multiple files when I added a new topic
through Flare, and the only way I could resolve the issue was to delete the
local copy and do a fresh check-out.

2. Most recently, when trying to bind a Flare project to the Subversion
controlled copy, I was repeatedly returned to the dialog where I designate
the source-controlled module to which Flare needs to point. When I shut
Flare down with Task Manager, I discovered that several project folders and
files had been duplicated, causing the project to become corrupted. I had
to copy a branched version in order to continue with my work.



You are 9786516 visitor since 20 Jan 2003.
1360 visitors today and 14 online right now.
blank left to top right blank

© Copyright by PushOk Software, 2003-2024, webmaster@pushok.com