tag:blogger.com,1999:blog-9537945.post2869429501697899261..comments2009-04-27T06:42:47.563-05:00Christopher Painterhttp://www.blogger.com/profile/12167478740431444267chrpai@yahoo.comBlogger3125tag:blogger.com,1999:blog-9537945.post-13460231338009105882009-03-23T04:21:00.000-05:002009-03-23T04:21:00.000-05:00Hi Chris, how could you generate the folder TFSPROJECT\WindowsProduct\Setup1\ProgramFilesFolder after build?<BR/><BR/>I created similar project but I got no such folder after successful build?Pradanahttp://www.blogger.com/profile/01690453240079295072noreply@blogger.comtag:blogger.com,1999:blog-9537945.post-18319692004952846812007-10-03T16:10:00.000-05:002007-10-03T16:10:00.000-05:00Sure, just define multiple ConfigurationToBuild elements. There may be situations where you want to build the windows application twice ( debug and release ) and situations where you don't ( release cdrom and release webdownload ).<BR/><BR/>It's all about how you organize and configure your solution.<BR/><BR/>As an aside, I work on large asset based products in a product line development environment. My .NET is split out across many solutions and my installs are in their own solutions. This allows me to branch/merge and build atomically while composing products from differnt groups of asset packages.Christopher Painterhttp://www.blogger.com/profile/12167478740431444267noreply@blogger.comtag:blogger.com,1999:blog-9537945.post-63597926512604456512007-10-03T16:05:00.000-05:002007-10-03T16:05:00.000-05:00I have a question, how can you make TSF to build multiple configurations of the InstallShield project, but not of the Windows application? E.g. you need to build the CDROM install and a downloadable install configuration of the Setup, but only the one Release config of the Windows app? Is that possible?<BR/><BR/>Sandrasandi.madden@sbcglobal.netnoreply@blogger.com