Output folder not kept as defined

[uwem]

[attachment=0]outputfolder.JPG[/attachment]
We intend to compile our chms for testing into that directory where our application is started after chm compiling.
see our attachement. After build the chm is located not in the defined path. MadCap creates automatically subfolder \output\HTML Help where it is located. This is not very userfriendly. Or is it a bug? If not is there a way to keep the output folder as defined?

Uwe M.

[RamonS]

This is by design. The output folder is Flare's territory and should not be used this way. What you want to use is the Publish function that allows for copying the output to the desired location. You can combine build and publish in one step.

[uwem]

Thanks, now we are sure. That's what we assumed. But really, if we type in the path as shown in the attachement and there is no obvious hint for this behavior an untrained user is confused because she /he does not find the chms where she/he looks for.
OK, we ll use publish options.

[RamonS]

I agree to some extent, but where should the hint be? The form is already very busy and cluttering it even more with hints and bubble help will make it maybe easier to use for the beginner, but annoying after that. The build vs publish differences are documented in the help and tutorials. The main problem with the extra folders is that the path gets longer. With Windows being tied to DOS era restrictions in regards to path/file name length (255 characters) this can cause problems.

[evanarsdall]

Compiling and publishing have long been separate processes in help development tools. Separating the two is an industry standard and isn't unique to Flare.

If you share your build output directory with users, you're giving them a lot of unnecessary files. The publishing process assembles only the files needed to properly display the essential content files and whatever those files need to function properly when accessed by users.