Tree Surgeon 2.0 - The future on the T4 Express
Posted
by Malcolm Anderson
on Geeks with Blogs
See other posts from Geeks with Blogs
or by Malcolm Anderson
Published on Sun, 08 Jul 2012 18:20:57 GMT
Indexed on
2012/07/10
15:17 UTC
Read the original article
Hit count: 293
Filed under:
If you've never been a fan of TreeSurgeon (http://treesurgeon.codeplex.com/) then skip this post.
However, if have been there have been some interesting developments over the last couple of years.
The biggest one is T4
Recently Bill Simser wrote a detailed post about the potential future of tree surgeon,
called "Tree Surgeon - Alive and Kicking or Dead and Buried"
He raised the question:
I've spent the last couple of years doing agile engineering coaching and architecture and from my experience, I can tell you, there are a lot of shops out there that would benefit from having Tree Surgeon as a viable product. Many would benefit simply from having the software engineering information that is embedded in the tree surgeon site be floating around their conversation.
Little things like,
Well, it used to be right out of the box. Today, you have to play with the project to make it work for you, but even with the issues (it hasn't been updated since 2008) it still gives you a framework, with logical separations that you can build from.
If you have used Tree Surgeon in the past, take a few minutes and drop a comment about what difference it made in your development style, and what you are doing differently today because of it.
However, if have been there have been some interesting developments over the last couple of years.
The biggest one is T4
Recently Bill Simser wrote a detailed post about the potential future of tree surgeon,
called "Tree Surgeon - Alive and Kicking or Dead and Buried"
He raised the question:
Times have changed. Since that last release in 2008 so much has changed for .NET developers. The question is, today is the project still viable? Do we still need a tool to generate a project tree given that we have things like scaffolding systems, NuGet, and T4 templates. Or should we just give the project its rightful and respectful send off as its had a good life and has outlived its usefulness.For myself, the answer is, keep it.
I've spent the last couple of years doing agile engineering coaching and architecture and from my experience, I can tell you, there are a lot of shops out there that would benefit from having Tree Surgeon as a viable product. Many would benefit simply from having the software engineering information that is embedded in the tree surgeon site be floating around their conversation.
Little things like,
- keep all of your software needed to run the build, with the build in the version control system.
- Have your developers and the build system using the same build.
- Have a one-touch build
- Separate your code from your interface
- Put unit tests in first, not last
Well, it used to be right out of the box. Today, you have to play with the project to make it work for you, but even with the issues (it hasn't been updated since 2008) it still gives you a framework, with logical separations that you can build from.
If you have used Tree Surgeon in the past, take a few minutes and drop a comment about what difference it made in your development style, and what you are doing differently today because of it.
© Geeks with Blogs or respective owner
