I was exited too when discovering Treehouse. I intended to use it to export assembly structure from existing complex assemblies.
Anything more than rather simple assemblies makes it crash or produce a fatal error message.
So - nice promises but unfortunately useless Treehouse.
It would also be useful, if you could see external references.
So I hope SW will continue on this product.
And of cause I agree with Johns points.
Not sure either what all the hype was - but your comment made my day, just learned a new one "It's as much use as a chocolate teapot" lol
We were notified of treehouse at our reseller's 2015 preview event. Never used it though.
I learned about it first from the "What's New 2015" document that was out before the VAR Preview event in my area.
Then I went to the preview event and was even more excited, but had not yet tried it.
I was also excited as I am the Engineering Manager in my company that is in-charge of SW and everything related to it in my company.
I thought this would be Wonderful because our documentation structure stinks (actually that's not true - we don't have a real structure!).
I am trying to get our system organized and it is a fight (too many opinions that converge - none of the others having any formal or structured documentation background - except me - but it is a small company so they all have some say in the structure - sorry, I got on a tangent).
Then, when I installed and tried 2015 I tried to setup a simple structure for an existing product and after a few hours of frustration I gave up.
Never opened it again.
I have not seen any indication in the preview information for 2016 that there have been any changes made to TreeHouse. Maybe they fixed some things but doesn't look like it. Hope I am wrong because, if it worked well, it could be a real documentation enhancement.
My point of view is that Treehouse has the potential to help. I am a designer and I can conceptualize the build of a complex assembly so I could set that up in TH and then let my designers go to work. I can literally name the entire assembly tree, parts and drawings included. If I have custom properties I can enter then before I even start modeling and I can show where I want drawings made. Now my team can get to work on 'building' and documenting that assembly.