I am using Team System to store my Help Studio 3, files/project. I want to be able to store versions of the output produced (both chm and html)  in the source control.  I can't see an option to to this through HS3.  Can this be done? If not .. this is a feature request :) 

To do this you would have to add them manually using your source control client.  

Hi, all. I've encountered the same need and found some solution.

What I did - added website to my solution and configured HS build profile to generate output to the website's folder. Before rebuilding HS project I need to check out the website, then generate help, then refresh folder structure for the website in solution explorer (if files were added to the folder it's handled by VS and it automatically adds them to source control). Then just check the folder in. Now I can even deploy my help separately or add the website's output to setup project. That's nice.

It works for me but it still has limitations and inconvenience (for example everyone who builds help must reconfigure build profile, VS doesn't seem to handle deleting files from website's folder - only adding etc.). So I would join burkni with requesting some additional integration with source control for HS projects output.

I have logged this as a feature request here - definitely a good idea.

Sounds good. The technical writers in our company don't have access to Visual Studio and as we are using Team Foundation Server we don't have any easy way of manually committing files without outside Studio (like e.g  tortoise for subversion).  I guess many are in that situation.

Out of interest, do you normally tend to store the outputs in the project path in Source Control, or in a different part of the Source Control tree?

We used to store documentation with the dev projects ... but we have been using HelpStudio to disconnect the technical writers from the main development process, and will now be storing documentation output for all projects in the same designated documentation tree

Just an update to let you know that this feature was implemented in the recent HelpStudio 3.5 update - there is now a property in the Build Profile that allows you to identify a Source Control location for the generated help file.