> This feature has been added to uppercut at rev 316 or hash dc13e16
> depending on where you are looking. I will have a release up soon.
> There is a setting you will need to add to your config file to take
> advantage, do a comparison of your UppercuT.config versus the new one.
> This allows you to compartmentalize all of your projects into their own
> subfolders neatly based on how you set up your out directory from visual
> studio. For uppercut to still work, you need to make sure the ones you care
> about still build to the same top level folder and then are built to
> subfolders under that same directory. Like say you had a common bin folder
> that was at the same level as all of your projects. You would tell the
> project1 ..\bin\*project.name*\*SubFolder1* and project2 ..\bin\*
> project.name*\*SubFolder2* and so on and so forth. Then tell uppercut
> what the build output folder is, if you are not using build_output - there
> is a setting in the uppercut.config for this.
> And now the caveat. You cannot use this in conjuction with multitargeting.
> UppercuT must be able to specify an output path to take advantage of
> multitargeting.
> Questions? Feel free to ask, someone else probably has the same question.
> :D
> ____
> Rob
> "Be passionate in all you do"
> http://devlicio.us/blogs/rob_reynolds
> http://ferventcoder.com
> http://twitter.com/ferventcoder
> On Tue, Jul 6, 2010 at 11:42 AM, Rob Reynolds <ferventco...@gmail.com>wrote:
>> FYI - being put in as we speak.
>> ____
>> Rob
>> "Be passionate in all you do"
>> http://devlicio.us/blogs/rob_reynolds
>> http://ferventcoder.com
>> http://twitter.com/ferventcoder
>> ---------- Forwarded message ----------
>> From: Dru Sellers <d...@drusellers.com>
>> Date: Tue, Jul 6, 2010 at 9:05 AM
>> Subject: uppercut feature
>> To: Rob Reynolds <ferventco...@gmail.com>
>> allow people to either override the output path, or use the one that is
>> configured. but that the default is to override.
>> -d
