Flare 11 build process

This forum is for all Flare issues not related to any of the other categories.
sdcinvan
Propellus Maximus
Posts: 1260
Joined: Wed Aug 21, 2013 11:46 am
Location: Vancouver, Canada

Re: Flare 11 build process

Post by sdcinvan »

KCinColorado wrote:My HTML5 target builds went from about 1-2 minutes (with Flare 10) to 5-6 minutes (with Flare 11). Same project, no major changes, just topic edits here and there.

MadCap Support zipped my project and built it in 1/2 the time. These are the suggestions they gave me for reducing build times. I'm still working through them but thought they might be useful to someone else:

1) Clean the project. (Close Flare. In Windows Explorer, go to your Flare project and delete the Analyzer, Output, and User folders. (If you want to retain any of our built outputs or info in the User folder, move these outside your project rather than delete them.)

2) To determine if the issue is related to source control, zip the project and remove binding from zipped file then try building that.

3) Try running Flare as Administrator (Shift+Right Click, Run as Admin).

4) Delete the CatapultMdiEditor folder. (In Explorer, go to C:\Users\[Your Username]\Appdata\Roaming\Madcapsoftware\Flare 2. The folder should be within the Flare directory.) Note that this deletes your layouts so if you may want to save them elsewhere.

And lastly, if none of the above work:

5) Repair the .NET Framework on your machine. (Windows Control Panel, Programs and Features, search for Microsoft .NET Framework Client Profile, right-click the item > Uninstall/Change > Repair. Repairing the .NET Framework "Client Profile" will also repair "Extended". If the .NET Framework "Multi Targeting pack" is installed, perform a repair of this as well.) You will need to restart your machine after this.

I am only up to step 4 because the first three had no effect on my build time. Hopefully some of these hints from MadCap will help someone else though.
I received a similar list from MadCap and like you, none of the suggestions actually do anything to speed up the build time (or in my case, build time and random build crashes during Global Project Linking). I suggested that MadCap append their list with the following potential fixes:
  • Change any embedded vector images with bitmap images (where possible). Images such as: .pdf, .svg, .eps should be converted to .png images. The reason is that Flare's rendering tool (or whatever is required to embed vector images into a final PDF or convert vector to bitmap for HTML5 output) is extremely slow.
  • Global Project Linking is very slow (at least for me) and projects that do not rely on GPL will build in 1/2 the time. This might explain why when you zip up a project for MadCap testing, they report back with very different build times; a zipped project is no longer associated with GPL.
  • Ensure that your project is located on a local disk (no components over a network)
  • Ensure that you have .NET Framework 4.5.2 or better (the latest is 4.6.1) https://www.microsoft.com/net
    Also, remove any old versions of the .NET framework.
Good luck
Shawn in Vancouver, Canada
Main tools used: Flare 11.x, InDesign, Google Docs, Lectora, Captivate.
Report bugs: https://www.madcapsoftware.com/feedback/bugs.aspx ▪ Feature requests: https://www.madcapsoftware.com/feedback ... quest.aspx[/i]
Post Reply